D-Link Forums
The Graveyard - Products No Longer Supported => DIR-655 => Routers / COVR => Europe DIR-655 => Topic started by: legenden on May 18, 2010, 05:39:06 AM
-
After installing 1.32EU on my DIR-655, UPNP stopped working on Windows 7.
I have ran the test at:
http://www.microsoft.com/windows/using/tools/igd/results.mspx
On two separate Windows 7 machines, and they both reported Not Supported for UPnP, in the More Information link, it said 0 IGD device(s) found.
I had also enabled UPnP logging in uTorrent to troubleshoot the error, and this sequence kept repeating:
[2010-05-17 15:57:47] DEBUG: UPnP: Got a reply/notify event
[2010-05-17 15:57:47] UPnP: Found location from upnp notify: http://192.168.0.1/root.sxml
[2010-05-17 15:57:47] UPnP: Discovered host: http://192.168.0.1/root.sxml
[2010-05-17 15:57:47] UPnP: The device "" is not a UPnP router (http://192.168.0.1:80/root.sxml)
[2010-05-17 15:57:47] UPnP: Device error "http://192.168.0.1/root.sxml": (-2)
[2010-05-17 15:57:49] UPnP: Could not map UPnP Port on this pass, retrying.
However, weirdly, the Microsoft.com UPnP test appeared to work correctly on a Windows XP machine, but not on Windpws 7.
After reverting the firmware to version 1.30EU, UPnP started working again, the test reported UPnP supported, and the uTorrent logs started showing:
[2010-05-18 15:27:03] DEBUG: UPnP: Got a reply/notify event
[2010-05-18 15:27:03] UPnP(XP): TCP port 47826 -> 192.168.0.199:47826 mapped successfully.
[2010-05-18 15:27:03] UPnP(XP): UDP port 47826 -> 192.168.0.199:47826 mapped successfully.
[2010-05-18 15:27:03] DEBUG: UPnP: Got a reply/notify event
[2010-05-18 15:27:04] DEBUG: UPnP: Got a reply/notify event
[2010-05-18 15:27:04] UPnP: Found location from upnp notify: http://192.168.0.1/root.sxml
[2010-05-18 15:27:04] UPnP: Discovered host: http://192.168.0.1/root.sxml
[2010-05-18 15:27:04] UPnP: Discovered new device: "WFADevice" http://192.168.0.1:4444/wipconn
[2010-05-18 15:27:04] UPnP: Getting external IP
[2010-05-18 15:27:04] UPnP: Got external IP: xxx.xxx.xxx.xxx
Hopefully a new firmware will be available to fix this. For now, I'm going to remain on 1.30EU.
-
Yes, my findings exactly. On 1.30b8, it works. And W7 is the only one with this problem, as it works on Vista. My post is the last one on this thread: http://forums.dlink.com/index.php?topic=12019.0