Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[PhantomMike]

I replaced my trusty DIR-655 with a new DIR-865L today.  Automatic setup went smoothly, and after that was complete I created/enabled a mydlink account, updated my firmware to 1.03 and set up my various DHCP reservations.  After that I verified that after restarting the various PCs they were getting the IPs I had allocated for them and then I entered the port forwarding rules into the router.  I added port forwarding rules for my homeserver, minecraft server, and steam server. These are the same DHCP reservation IPs and Port Forwarding rules I used successfully on the DIR-655. 

Unfortunately, I have not been able to access my computers from the internet.  I verified that I was able to access the web site on my homeserver and the minecraft server via another local computer using the lan IP:port - so the basic functionality works.  I also verified that the WAN IP address in the router WAN Status page is valid so I'm not suffering from the multiple routers issue.  I went to the routers firewall settings and switched both to "endpoint independent" for the NAT filtering.  I played a bit with DMZ and that didn't seem to help either.  I have rebooted the router.  My Comcast modem is an ARRIS TM822.

Any other thoughts for additional troubleshooting?

Thanks for any suggestions.

Mike

[PhantomMike]

Update:
It turns out that port forwarding is working, when accessed from computers outside my local LAN.  I was testing port forwarding by trying to connect to my WAN:port or DNSName:port from other computers on my LAN, and that was failing.  However folks from outside my LAN seem to be able to connect to my servers over the internet.
On the dir-655 I used to be able to validate port forwarding was working by accessing via WAN:port or DNSName:port from my LAN, but that doesn't seem to work with dir-865. 

I'm currently researching that problem but if anyone knows why that is the case or what the workaround is I would appreciate it.

Thanks.

    --Mike

[FurryNutz]

Have you tried using Virtual Server instead of PF?

[PhantomMike]

Thanks.  I did some more research and have come upon a few posts that are relevant to this "loopback" scenario.  Some claim that loopback is no longer supported on some/recent d-link routers, even that it used to work on early "A" versions of the dir-655 but not on the "B" versions.  I haven't seen much referring to the dir-865l.  Others claim that loopback works on some dlink routers if you use virtual server instead of port forwarding, another claimed it worked for virtual server only if you map the public port to a different private port.  I have tried using virtual server for my minecraft server, both with the same public/private port and one that maps - and neither worked in the loopback scenario.

[FurryNutz]

Ya, been posts regarding LoopBack. Not sure which ones do and which ones don't. Possible that older DIR series models do and newer models do not.

Also be ware of this:
http://forums.dlink.com/index.php?topic=50682.0

[carlb60]

DLink Coax Cable Modem (model too small to read) connected to Cox. Using Cat 5e cable that came with DIR 865L.

I finally got Remote Desktop going after fighting it all day yesterday and spending $33 with DLink expanded service.  The solution (not provided by DLink expanded service) was as follows: Reset the modem to factory defaults after upgrading firmware to 1.03.

Set Port Forwarding (not Virtual Server) for port 3389 and forward to a fixed ip computer on the LAN.  Make sure the target server (computer) allows Remote Desktop - Windows 7, System and Security, Allow Remote Access, everyone or whoever you want.

Stick with default LAN ipv4 addresses 192.168.0.1 - 254.  Make sure Remote desktop works on the target computer by connecting via the LAN using LAN address.  Make sure you know what your external IP address is (status page on the router).

You cannot connect using the external address from the LAN - you gotta try from outside.  I used Remote Desktop to my work computer via VPN then back to external IP.  Still no joy.  Checked McAfee firewall log and found that port 3389 was being blocked even tho Remote Desktop was enabled in Firewall Apps.  Went to "Ports and System Services" on McAfee firewall and enabled 3389 (Remote Desktop).  Problem solved

[FurryNutz]

Seems like this was a configuration issue.
FYI>http://forums.dlink.com/index.php?topic=51256.0

Glad you got it working.

Enjoy.

DLink Coax Cable Modem (model too small to read) connected to Cox. Using Cat 5e cable that came with DIR 865L.

I finally got Remote Desktop going after fighting it all day yesterday and spending $33 with DLink expanded service.  The solution (not provided by DLink expanded service) was as follows: Reset the modem to factory defaults after upgrading firmware to 1.03.

Set Port Forwarding (not Virtual Server) for port 3389 and forward to a fixed ip computer on the LAN.  Make sure the target server (computer) allows Remote Desktop - Windows 7, System and Security, Allow Remote Access, everyone or whoever you want.

Stick with default LAN ipv4 addresses 192.168.0.1 - 254.  Make sure Remote desktop works on the target computer by connecting via the LAN using LAN address.  Make sure you know what your external IP address is (status page on the router).

You cannot connect using the external address from the LAN - you gotta try from outside.  I used Remote Desktop to my work computer via VPN then back to external IP.  Still no joy.  Checked McAfee firewall log and found that port 3389 was being blocked even tho Remote Desktop was enabled in Firewall Apps.  Went to "Ports and System Services" on McAfee firewall and enabled 3389 (Remote Desktop).  Problem solved

[Svuppe]

Thanks.  I did some more research and have come upon a few posts that are relevant to this "loopback" scenario.

I am having the same problem as you. But I have found that the loopback does work with UDP connections. TCP does not.

[FurryNutz]

The Canadian site reports that the v1.04 fixes some NAT Lookback issue. Might try it to see if it resolves anything.
http://forums.dlink.com/index.php?topic=52708.0

I am having the same problem as you. But I have found that the loopback does work with UDP connections. TCP does not.

[Svuppe]

Success.
The Canadian 1.04 does indeed solve the loopback problem.

[FurryNutz]

Awesome, glad it's working for you. Enjoy.

Success.
The Canadian 1.04 does indeed solve the loopback problem.