D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-865L => Topic started by: cthog on January 18, 2013, 08:40:51 AM

Title: Still having port forwarding problems
Post by: cthog on January 18, 2013, 08:40:51 AM
Hi Guys,

I looked through PhantomMike's thread, but don't seem to have the same issue.

I can't get port forwarding to work, and I suspect it's because my DHCP table isn't populating properly.  I've got a SBG6580 (with the built-in router) set in bridge mode--with NAPT off, DHCP off, wireless off, etc.  I have no problem getting internet functionality on my 865L. 

The problem I'm having is that I've made a DHCP reservation for my Buffalo NAS, which works fine.  It's at the correct ip address.  However, when I enter that IP in port fowarding, it doesn't seem to work.  (Yes, I've hit the checkmark, lol.)  What I suspect is a problem is that the NAS isn't available in the drop-down computer menu, nor does it show up in LAN computers on the Status page.

So basically, on my internal network, I have no problem going to the NAS, but as far as the internet is concerned, it doesn't exist.  Anyone encounter/solve this problem?

Chris
Title: Re: Still having port forwarding problems
Post by: FurryNutz on January 18, 2013, 09:33:51 AM
Link>Welcome! (http://forums.dlink.com/index.php?topic=41537.0)
Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on routers web page under status.
What region are you located?

Have you tried using Virtual Server instead?
Title: Re: Still having port forwarding problems
Post by: cthog on January 18, 2013, 02:05:46 PM
Hi FurryNutz,

I upgraded to 1.03, and Virtual Server didn't do anything for me.  It's kind of frustrating, because this is the exact issue that made me return the Western Digital mynet 900 2 weeks ago!

Chris
Title: Re: Still having port forwarding problems
Post by: FurryNutz on January 18, 2013, 02:10:39 PM
Think this is a configuration issue. Let see if we can help ya out...

What region are you located?
Are you wired or wireless connected to the router?
Has a Factory Reset been performed?

What ISP Service do you have? Cable or DSL?
What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?

If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
Double NAT (http://www.practicallynetworked.com/networking/fixing_double_nat.htm)
To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged.
If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ.
Check ISP MTU requirements, Cable is usually 1500, DSL is around 1492 down to 1472. Call the ISP and ask.

Some things to try: - Log into the routers web page at 192.168.0.1. Use IE, Opera or FF to manage the router.
Turn off ALL QoS (http://vonage.nmhoy.net/qos.html) or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting.
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
Enable uPnP and Multi-cast Streaming under Advanced/Networking. Disable uPnP for testing Port Forwarding rules.

WAN Port Speed set to Auto or specific speed? Some newer ISP modems support 1000Mb so manually setting to Gb speeds can be supported by the router. Advanced/Advanced Networking/WAN Port Speed
Set current Time Zone, Date and Time. Use an NTP server feature. Tools/Time.
Title: Re: Still having port forwarding problems
Post by: FurryNutz on January 18, 2013, 02:13:54 PM
Also what is the make and model of the NAS?
Title: Re: Still having port forwarding problems
Post by: Hard Harry on January 18, 2013, 02:18:28 PM
The main issue I see is the device isn't showing as a connected device in that drop down. What model NAS do you have? Is it set to DHCP? Can you log into it's interface?
Title: Re: Still having port forwarding problems
Post by: cthog on January 18, 2013, 03:44:44 PM
Hey guys,

Yes, I made sure the modem is bridged, I'm not getting a 192.x.x.x WAN IP. 

The NAS is a Buffalo Linkstation LS-WVL.  I can log into its interface, and I made sure that DHCP was enabled.  I have the option to set a static IP on it as well, which had similar results (no problem finding it on network, but now joy on port forwarding.)

One more thing I neglected to mention, which may be pertinent--the NAS is behind a DS-2205 switch.  I figured D-Link devices would play nicely with each other.  It's unmanaged, so there's no interface to fiddle with.
Title: Re: Still having port forwarding problems
Post by: Hard Harry on January 18, 2013, 05:21:10 PM
Looking through the manual, a couple questions:

1. What is the power mode on? I suggest setting it to On during testing.

2. If you disable the DHCP reservation, what IP does it get? I wonder if maybe something on the LAN is set to give out IP's

3. When you set a static IP, make sure its outside the DHCP server range, but not within range of anything else on your network. Then port forward to that.

4. What are you using to test if the port forwarding works or not? Is it showing in the routing table?
Title: Re: Still having port forwarding problems
Post by: cthog on January 19, 2013, 05:52:59 AM
Harry,

Linkstation is always On (the Auto setting is just ridiculous, and kind of defeats the purpose of a NAS, in my opinion).

If I disable the reservation, and don't enable a static IP on the NAS, it gives it 192.168.0.131.

When I first set up the router, the DHCP range was 192.168.0.100 onward.  I reserved x.x.x.14.  Same results.  I actually thought I was on to something when I changed the range to 192.168.0.2 onwards... but I wasn't, lol.

Testing with a variety of programs.  Trying to use PuTTY to ssh into my NAS, for instance.  Obviously I can do it from within my network, but not from outside.  Rather frustrating, really!

**Update**

Another weird thing I've noticed is that, while I opened the port range 7070-7080, only ports 7070-7074 actually show as open when testing from a web-based port checker.  What the hell?
Title: Re: Still having port forwarding problems
Post by: Hard Harry on January 19, 2013, 06:44:23 AM
Found this thread (http://forum.buffalo.nas-central.org/viewtopic.php?f=41&t=2000&sid=756b1f6c2b78174b9976972e31659edd&start=15), where someone was having a similar problem and their issue was their switch.

1. Have you tried removing the switch? Going NAS direct to router?
2. Can you ping the NAS from a computer on your LAN?
3. When set with no DHCP reservation, and the NAS gets the 192.168.0.131, does it show in the Connected Devices list?
4. Try with a new Ethernet cord.
Title: Re: Still having port forwarding problems
Post by: cthog on January 19, 2013, 07:07:58 AM
Hi again Harry,

I have no problem pinging the computer.  Like I said, it works fine within my network, it's just accessing it from outside my network that's the problem.  I can ping from either the router itself, or another PC on the network.

I changed the cable just to check, but since it worked fine with the router on the SBG6580, and it's pingable, I don't know what the issue would be.

Sometimes the NAS will appear in the 'LAN Computers' list, whether as x.x.x.14 or x.x.x.131.  It makes no difference.  I'm kind of concerned about the fact that some of the ports I instructed the router to open are still closed.
Title: Re: Still having port forwarding problems
Post by: Hard Harry on January 19, 2013, 08:01:14 AM
Oh thats different. I thought the NAS not showing up in the connection list was the main problem, since how would one apply port forwarding rules if the router doesn't see the NAS connecting. If that isn't a issue, then I shal move on.

How are you telling if a port is open or not? What ports are you opening?
Title: Re: Still having port forwarding problems
Post by: cthog on January 19, 2013, 11:02:02 AM
Well, I'm trying to open port 22 so I can ssh in remotely.  Portscanner says it's open, but doesn't get forwarded.

I also wanted 7070-7080 open, for SABnzbd, sickbeard, etc.  Portscanner says 7070-7074 is open, but 7075-7080 isn't.  Weird, huh?  Even the open ports, however, do not get forwarded.

I like D-Link, and I'm willing to mess with this for a while, but if I don't get this fixed in the next week or so, I guess I'll have to return this router, too.  Really strange.
Title: Re: Still having port forwarding problems
Post by: FurryNutz on January 19, 2013, 11:40:17 AM
Is the ISP modem really bridged? To tell if the modem is bridged or not, look at the 865Ls web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged.
If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ.
Title: Re: Still having port forwarding problems
Post by: Hard Harry on January 19, 2013, 11:41:10 AM
Well alot of other things might be blocking the ports. First I would fact check the test your using by connecting direct to the 6580 and running the tests. If there not open there, then its either the test, your PC, or the 6580. One thing to note is if no traffic is running on those ports, the ports won't be forwarded..because theres nothing to forward. I know this first hand when I was trying to get SABnzbd to integrate into my web based newsgroup search engine.  I was testing it while the client was off. Woops
Title: Re: Still having port forwarding problems
Post by: cthog on January 19, 2013, 02:13:20 PM
Harry,

Okay, that explains why 7005 and onwards wasn't open.  Mystery solved there.

The plot thickens, however.  Well, actually it's kind of thinning out, as progress has been made.  I went through the bridging process on my SBG6580 again, and forwarded the WAN mac of the router in the modem settings.  Not sure if that's just voodoo, but I discovered that port forwarding works from an external connection now.

*However* (of course), when trying to test from home (and from my phone, using Mediadog (to check SAB, sickbeard, etc)), when I use my dynamic dns, I can't open the port.  I have confirmed that the dynamic dns is correctly reporting my cable IP, but more to the point, my phone will connect to the same dynamic host address when NOT on my wireless network.

I wasn't even aware that my wireless network would play a role in the dns resolution of the dynamic ip, but apparently it does.  So what works on a different network doesn't work on my own.  Weird, weird, weird.

Any thoughts on this, guys?
Title: Re: Still having port forwarding problems
Post by: Hard Harry on January 19, 2013, 03:14:05 PM
Ok, first, so to be clear, your end game is to use the Mediadog App on your phone from outside your network, using a domain set up with DDNS that points to a DHCP IP that is configured on your router. Then your port forwarding that IP to x.x.x.113 (NAS IP's) on port 7070-7074.

1. How does the Mediadog app, SABnzbd and the NAS tie together? Or are we talking about two different things?

2. It makes sense that the App wouldn't work on your own network because the app is pointed to a IP that your own router is configured for. I don't think the DIR-865L has loop back. Its the equivalent of calling your own phone number to reach another headset in your house.

But in general are things working now?
Title: Re: Still having port forwarding problems
Post by: cthog on January 20, 2013, 06:15:01 AM
Harry,

You've got the picture.  I used modified firmware for my LS-WVL to enable root access, then installed optware,   I can run SAB, sickbeard, couchpotato, headphones... even LazyLibrarian, and have it always on using about 15 watts.  (Lol, I sound like I work for Buffalo; I don't, but I'm pretty pleased with it, as you can tell.)

So yeah, I have my home IP configured with a DDNS, with the appropriate ports forwarded to the NAS.  Mediadog is configured to query the ports on the DDNS host.  With the built-in router on the SBG6580, it didn't seem to matter whether I used the DDNS or the local ip in my query, whether I was doing it from Mediadog or a network pc.

From what you're saying, it looks like this may simply be a feature (loopback?) that the 865L lacks, which is kind of surprising, since I always figured the SBG6580 had POS software.

In general, things are working--however, I'd love to fix this, because I'd have to select a different host every time I'm at home and want to use Mediadog, which, being an American, is simply way too much work for me.

Now, however, it looks like I'm simply at PhantomMike's issue.
Title: Re: Still having port forwarding problems
Post by: Hard Harry on January 24, 2013, 10:07:18 PM
Nope, I don't believe the DIR-865L has loopback.

Option 1, to change the host for the Coachpotato (to your LAN IP) when your on your LAN, and back when your off it.

Option 2, you can get a second IP and go modem > switch > DIR-865L (IP1) and LS-WVL (IP2). Then your configuring DDNS on the LS-WVL and not the DIR-856L, but that means it will no longer be behind a firewall. Then your just configuring your Coachpotato for IP2 which would be outside your DIR-865L LAN.

Option 3 is buy a different router. Here is a decent (but out dated) list of routers (http://opensimulator.org/wiki/NAT_Loopback_Routers) with loopback.
Title: Re: Still having port forwarding problems
Post by: cthog on January 25, 2013, 12:59:40 PM
Thanks Harry,

I'm thinking Option 4, is hope that DD-WRT is developed for this hardware, which other than the lack of this ridiculously easy to implement feature, is pretty impressive.

Cheers, mate.
Title: Re: Still having port forwarding problems
Post by: Hard Harry on January 25, 2013, 04:27:52 PM
Actually thats possible, just if it happens, its going to be a long time. 1+ years. The DIR-865L seems to use the BCM4706, which is the same chip as the RT-N66U and the WNDR4500, but unlike the RT-N666U it separates the processing of the wireless between the CPU and the Wireless CPU, which means its going to be a pain to code. Thats why there is no 3rd party support (that I know of) for the WNDR4500, because it does the same thing.

I mean if it was a PC, you could edit the host files. Maybe you do something similar with your phone? I assume you have it rooted?
Title: Re: Still having port forwarding problems
Post by: FurryNutz on February 05, 2013, 08:57:12 AM
Wondering if this might help with Loop Back?
http://forums.dlink.com/index.php?topic=16358.0 (http://forums.dlink.com/index.php?topic=16358.0)