Print

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

[whiteangel]

I can't turn on my home computer remotely. WOL was configured and working correctly a few months back. I could turn on my home computer remotely from work with my laptop and also with my Android phone, but now WOL packets are not turning on my home computer. Remote Desktop is also not connecting to the home computer remotely. I can only connect with Team viewer remotely. It has a wake feature, that I could use to wake up my home computer, but that is not working.

I posted a few months back when I had problems configuring my router for remote access at that time, I successfully enabled port forwarding and WOL was also working. Link to previous post.

http://forums.dlink.com/index.php?topic=56897.msg221997#msg221997

Nothing has changed since then, I haven't made any changes to the router or the computer configuration. Can't figure out why it stopped working.

Router Firmware is 2.05
Dlink DDNS is connected

[FurryNutz]

Any status on this? 

[whiteangel]

Status is same as before.

There are two issues I don't know if both are related.

Issue 1
I can't use WOL to turn on the computer remotely. I did a check for open ports on the home computer, port 3389 is open. WOL was working fine several weeks back, no configuration changes have been made to the router or the home computer. The only recent change in hardware was an HP printer which I connected to the home computer and installed drivers for it. Prior to this, WOL was working fine from my laptop and also my android phone, now both devices cannot wake up the remote computer.


Issue 2
Remote desktop cannot connect to the remote computer. I can connect with Team viewer but only when the remote computer is already on. I can't wake it up from sleep.

[FurryNutz]

Internet Service Provider and Modem Configurations

• 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: Link>Double NAT and How NAT Works. 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.
  Example of a D-Link router configured for PPPoE with ISP Modem bridged: PPPoE Configuration on Router
• Check ISP MTU requirements, Cable is usually 1500, DSL is around 1492 down to 1472. Call the ISP and ask. Link>Checking MTU Values
• For DSL/PPPoE connections on the router, ensure that "Always ON" option is enabled.

[whiteangel]

Furrynutz...
Some months back you helped me bridge the modem, configure WOL and set up port forwarding. Like I stated before, this does not seem to be a configuration issue. WOL was working fine after you helped me set it up, but for some reason it is not working now. Please refer to the link below.

http://forums.dlink.com/index.php?topic=56897.msg221997#msg221997

[FurryNutz]

Ensure nothing has changed on the ISP modem configuration and the router. I presume if it had been working that the router was configured corrected and that something else has changed, either on the modem side or the PC side...

[whiteangel]

uPNP was enabled. I think I enabled it accidentally, because I remember disabling it to get WOL working. I have disabled uPNP and now its working.

What effect does disabling uPNP have? Can you please elaborate on the benefits of having uPNP.

[FurryNutz]

Think of it as the router automatically connecting ports to there applications with out any configuration needed by you. Now since you are using port forwarding for a specific application. uPnP isn't needed and maybe interfering with WoL configurations which it seemed to be.

Glad you got it working.

Enjoy.