In the utorrent case they already have the IP addresses they need so DNS resolution is not required, ergo they just work. From what I have heard/read here it is almost definately a DNS resolution related issue. Have either of you tried to set up your NIC with fixed DNS address (4.2.2.2 or 4.2.2.3)

Not yet, but I will try when I get home. I'm only home every 2nd month unfortunately.

The new firmware v2.09 has resolved the DNS error issues. The firmware isn't available for download on the DLINK website yet, so if anyone else has similar issues with the DSL-2642B ADSL router I'd be happy to send you the file.

Good to hear. Since i last posted, mine started to work properly.

After the last time i reset the router, vie never had to again since. Weird.

I am also having problems with this DSL-2642B with its DNS issues.
I turn on my laptops wifi, all is well. Then I go to turn on my ipod touch's wifi and the DNS just dies for this modem.
Only reapplying the DNS settings fixes this.

Manually assigning each PC a DNS server works great, but I would prefer the actual modem to provide the DNS servers!

Every time I join the wifi network with my iPod touch, DNS just dies! Pings stay active.
Other devices I have here seem to work fine.

Would be great if you could send me the newer firmware too, as I have already tried Firmware Version: AU_2.06 and AU_2.07 with no good result!

Man I dislike Dlink!

EDIT: To all, this is the link Dlink sent me (after I called) for the 2.09 firmware, use at your own risk, as I believe it is only a Beta: ftp://dlink.com.sg/DAUS_download/DSL-2642B/AU_DSL-2642B_2.09_08032010_cfe_fs_kernel

That FW v2.09 has proved to be quite stable for me, except that my ultra-reliable rock steady Kaleidescape system mis-behaved once when I tried to install a new M-Class player on my network. Despite being set to DHCP the player couldn't get an IP from the DLINK router (my network DNS server), and so couldn't communicate with it's server on the network. Although it could call home to Kaleidescape HQ in Sunnyvale and tell them it wasn't happy. Resolved by router re-boot. All good since.

I have found that FW v2.09 won't let you change from the default network range to your own preferred rage as before.
Am I blind or is this possible? I can't seem to find the option to change from the default network range. 192.168.1.# to 10.1.1.# etc.