I have Azureus/Vuze as a P2P client and it can test, more accurately than most, whether or not ports are properly opened. Normally, this isn't a problem, but after 1.33NA, UPnP will go down and the router has to be restarted. I may downgrade to 1.31NA like I did from 1.32NA, but what do you guys think? Anyone else having the same issue? I have the UPnP service, etc. marked as automatic in Windows 7 HP x64.
I have the similar situation as yours.
1.33NA + WinXP SP3 + uTorrent 2.0 17920(official stable release, not the beta)
Under 1.32 build 9, the uTorrent 2.0 UPNP could run for 1x days smoothly without any DIR-655 reboot or PC reboot.
After I updated to 1.33NA, UPNP cannot be used AFTER the uTorrent 2.0 continuously ran for 3-4 days.
I did a soft reboot on DIR-655 1.33NA, nothing happens.
I want to point out that the DIR-655's 1.33NA UPNP stops working after CERTAIN days or CERTAIN accumulated throughput.Don't ask me stupid question about confirming the 2 Windows related services or the DIR-655 UPNP web option are whether on or off.
However, I discover an odd thing that the web UPNP check box in DIR-655 is unchecked after a soft reboot. No one has entered the web page because i am the only owner of it, so I doubt whether DIR-655 shuts its UPNP down automatically when something is triggered.Honestly, I have switched some critical options after I updated to 1.33NA. This maybe the cause but it should not be. Otherwise, it is a serious bug.
Here is the important options comparison between current 1.33NA setting and the previous 1.32 build 9 setting
| 1.32 build9 | 1.33NA |
QoS page | off | on + traffic shaping on + manual 100000 + manual cable + 3 boxes on in the middle |
SPI | on | on |
Anti-spoof | on | on |
Endpoint filter | highest restricted | highest restricted |
Securespot | on | off |
Anti-spoof | on | on |
DNS relay | on | on |
NTP | D-link server | D-link server |
Syslog | off | off |
MAC access Filter | off | off |
HTTPS | on | off |
RemoteManagement | on | off |
Multicast | on | on |
Wireless | off | off |
Of course, I can switch them back into 1.32build 9 status.
So, wait me for another 10 days and the truth will be out.