Print

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

[lagonauta]

When I noticed that the ports died, I also noticed that the router was very hot on the base (it was standing horizontally).
Now it is vertically positioned and seems to be running cooler, it also seems to be more stable. This weekend we are planning another LAN party, will post here if it goes without any problem. Did the other people that had problems with this router say if it was standing vertically or horizontally?

Maybe this router has some overheating issues? I keep the room where it is located at 25C (77F), for some it may be too hot but I am used to hot climates making it very comfortable to me.
I just hope that it works well in my country where it is fairly common for the temperature get to 35C (95F).

[FurryNutz]

I had mine runing in both H and V positions. I didn't notice anything while using H however I didn't have a a lot of traffic going on like you do. I'm the only gaming in my house and during the day, roommate works from home so mostly general internet and some VPN stuff going on. So I might not have noticed it. I know we are tracking a temperature issue over on the 857 forum. The newer routers do run a bit hotter however if there are some differences between H and V positions, might need to let D-Link know. Can you look at the user manual and see if there is operating temperatures listed?

I would turn off options like WPS, WISH and options that you don't really need. Helps the router run lean and smoother sometimes. Use Specific Wifi modes like before if you don't need A or B modes.

Wire connect those devices that can be wired connected. IT's preferred specially for gaming.

Keep us posted on how it goes.

[FurryNutz]

Also, the ISP modem, there isn't any WiFi enabled on it is there? Just checking.

[lagonauta]

The operating temperature goes from 0C (32F) to 55C (131F) according to the manual.
WPS is always off (too insecure and I never used it anyway), there is no WISH (I am starting to think that DIR-835 is lower-end than DIR-825).
Using NG on 2.4GHz and N on 5GHz. Medium transmit power on 2.4GHz and Low on 5GHz.
Using PPPoE to connect to the internet.

IPv6 is enabled with one HE tunnel, IPv4 and IPv6 firewall are up.
UPnP is active, media server and storage is off (USB is not being used). HTTPS is on. Guest network is off.
QoS is on (QoS configuration page is the same as the one for DIR-615, maybe the DIR-835 from Canada is different?)

Sadly I cannot connect any computer to it by wires as the router is in my bedroom and there is no way to put cables trough the walls.

The ISP modem is on Bridge mode and WiFi is disabled.

Will keep testing.

[FurryNutz]

If you could do me a favor and capture the QoS page and post it here if possible when you have time. I'll adjust the stickies to reflect this.

Does the QoS section look anything like this?
Gaming and QoS for XBL


How is the WiFi on the newer 835? Still acting up or working better? How many devices are connecting wireless while gaming? Could be running into a threshold limitation maybe.

One suggestion if you are interested, run 1 long LAN wired from the bedroom where your router is and run it out to where most of your wired devices are located. Get you a external Gb network switch. They make them from 4 ports all the way up to 48 ports. I have a 24 and a couple of 8 port units. Put the switch near your wired devices then connect them to the switch. Will run smoother if you can use this platform. I use a 50 ft cable that runs from my office to the living room where my 8 port is.

Keep us posted.

[lagonauta]

Here:
http://img832.imageshack.us/img832/8214/dir835qos.png

The wireless connection seems to be working better, with four N devices on 2.4GHz (and sometimes one X360 Slim (N) or one 3DS (G)). On 5GHz there is only one device.
Do not know if this is because of the unit, or because of the new firmware.

I played online only with the 3DS and it seemed to work fine. This weekend I should be able to test it for real, maybe lots of small packets on the network from LAN gaming saturate the router wireless processor.
(6 computers and 4 phones on 2.4GHz + 2 computers on 5GHz)

If it still gives me problems I might do what you suggested, just need to measure how long the cable should be. Ugly, but certainly effective.

[FurryNutz]

Here:
http://img832.imageshack.us/img832/8214/dir835qos.png
Thanks for the image. This wasn't what I saw, maybe they are different or they changed it. Crazy. One thing, I recommend disabling Dynamic Defrag. Thats for slow ISP connections. Isn't needed.
So you can review this:
Gaming and QoS for XBL

The wireless connection seems to be working better, with four N devices on 2.4GHz (and sometimes one X360 Slim (N) or one 3DS (G)). On 5GHz there is only one device.
Do not know if this is because of the unit, or because of the new firmware.
Keep us posted on how it goes.

I played online only with the 3DS and it seemed to work fine. This weekend I should be able to test it for real, maybe lots of small packets on the network from LAN gaming saturate the router wireless processor.
(6 computers and 4 phones on 2.4GHz + 2 computers on 5GHz)
One other suggestion, if you want to use more devices on 5Ghz, get you a DAP-1533 and connect them to it and bridge that 1533 to the 5Ghz on the 835. This might also help alleviate the load on 2.4Ghz radio.

If it still gives me problems I might do what you suggested, just need to measure how long the cable should be. Ugly, but certainly effective.

I agree, I have cables running back and forth from the office to the living room. I use those little brass round hooks and run the cable up and aroudn door jams and frames, putting the hooks up towards the top corners of the door frames then down as close to the floor as possible. This does help clean the wire runs up a bit.

If your concerned about router cooling, I bought one of these:
Onn Laptop Cooling Pad

[lagonauta]

Just noticed that the logs are flooded with name server messages, even when there is almost no activity on the router. Is that normal? I just had a major slowdown for some seconds and it seems to be related to them but that is a hunch, the router's config page was slow to navigate and websites were slow to load.
1 client on 2.4GHz and 1 on 5GHz.
Router has been running for 2 days and 3 hours with not very much traffic.
The slowdown stopped by itself. The logs are registering "System activity" and "Debug Information".

Code: [Select]

Nov 16 18:09:53 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:09:53 info   using nameserver 2001:470:20::2#53
Nov 16 18:09:53 info   using nameserver 216.254.136.227#53
Nov 16 18:09:53 info   using nameserver 216.254.141.13#53
Nov 16 18:09:53 info   reading /etc/resolv.conf
Nov 16 18:09:38 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:09:38 info   using nameserver 2001:470:20::2#53
Nov 16 18:09:38 info   using nameserver 216.254.136.227#53
Nov 16 18:09:38 info   using nameserver 216.254.141.13#53
Nov 16 18:09:38 info   reading /etc/resolv.conf
Nov 16 18:09:34 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:09:34 info   using nameserver 2001:470:20::2#53
Nov 16 18:09:34 info   using nameserver 216.254.136.227#53
Nov 16 18:09:34 info   using nameserver 216.254.141.13#53
Nov 16 18:09:34 info   reading /etc/resolv.conf
Nov 16 18:09:32 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:09:32 info   using nameserver 2001:470:20::2#53
Nov 16 18:09:32 info   using nameserver 216.254.136.227#53
Nov 16 18:09:32 info   using nameserver 216.254.141.13#53
Nov 16 18:09:32 info   reading /etc/resolv.conf
Nov 16 18:09:30 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:09:30 info   using nameserver 2001:470:20::2#53
Nov 16 18:09:30 info   using nameserver 216.254.136.227#53
Nov 16 18:09:30 info   using nameserver 216.254.141.13#53
Nov 16 18:09:30 info   reading /etc/resolv.conf
Nov 16 18:09:27 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:09:27 info   using nameserver 2001:470:20::2#53
Nov 16 18:09:27 info   using nameserver 216.254.136.227#53
Nov 16 18:09:27 info   using nameserver 216.254.141.13#53
Nov 16 18:09:27 info   reading /etc/resolv.conf
Nov 16 18:09:11 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:09:11 info   using nameserver 2001:470:20::2#53
Nov 16 18:09:11 info   using nameserver 216.254.136.227#53
Nov 16 18:09:11 info   using nameserver 216.254.141.13#53
Nov 16 18:09:11 info   reading /etc/resolv.conf
Nov 16 18:08:57 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:08:57 info   using nameserver 2001:470:20::2#53
Nov 16 18:08:57 info   using nameserver 216.254.136.227#53
Nov 16 18:08:57 info   using nameserver 216.254.141.13#53
Nov 16 18:08:57 info   reading /etc/resolv.conf
Nov 16 18:08:40 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:08:40 info   using nameserver 2001:470:20::2#53
Nov 16 18:08:40 info   using nameserver 216.254.136.227#53
Nov 16 18:08:40 info   using nameserver 216.254.141.13#53
Nov 16 18:08:40 info   reading /etc/resolv.conf
Nov 16 18:08:40 debug   dhcp6_reset_timer: reset a timer on sit1, state=INFOREQ, timeo=1551, retrans=110436
Nov 16 18:08:40 debug   client6_send: send information request to ff02::1:2
Nov 16 18:08:40 debug   copy_option: set opt_20 (len 0)
Nov 16 18:08:40 debug   copy_option: set option request (len 2)
Nov 16 18:08:40 debug   copy_option: set elapsed time (len 2)
Nov 16 18:08:40 debug   copy_option: set client ID (len 10)
Nov 16 18:08:34 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:08:34 info   using nameserver 2001:470:20::2#53
Nov 16 18:08:34 info   using nameserver 216.254.136.227#53
Nov 16 18:08:34 info   using nameserver 216.254.141.13#53
Nov 16 18:08:34 info   reading /etc/resolv.conf
Nov 16 18:08:27 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:08:27 info   using nameserver 2001:470:20::2#53
Nov 16 18:08:27 info   using nameserver 216.254.136.227#53
Nov 16 18:08:27 info   using nameserver 216.254.141.13#53
Nov 16 18:08:27 info   reading /etc/resolv.conf
Nov 16 18:08:20 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:08:20 info   using nameserver 2001:470:20::2#53
Nov 16 18:08:20 info   using nameserver 216.254.136.227#53
Nov 16 18:08:20 info   using nameserver 216.254.141.13#53
Nov 16 18:08:20 info   reading /etc/resolv.conf
Nov 16 18:07:57 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:07:57 info   using nameserver 2001:470:20::2#53
Nov 16 18:07:57 info   using nameserver 216.254.136.227#53
7:57 info   using nameserver 216.254.141.13#53
Nov 16 18:0Nov 16 18:07:57 info   reading /etc/resolv.conf
Nov 16 18:07:33 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:07:33 info   using nameserver 2001:470:20::2#53
Nov 16 18:07:33 info   using nameserver 216.254.136.227#53
Nov 16 18:07:33 info   using nameserver 216.254.141.13#53
Nov 16 18:07:33 info   reading /etc/resolv.conf
Nov 16 18:07:33 info   UDHCPD Inform: add_lease 192.168.0.222
Nov 16 18:07:31 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:07:31 info   using nameserver 2001:470:20::2#53
Nov 16 18:07:31 info   using nameserver 216.254.136.227#53
Nov 16 18:07:31 info   using nameserver 216.254.141.13#53
Nov 16 18:07:31 info   reading /etc/resolv.conf
Nov 16 18:07:27 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:07:27 info   using nameserver 2001:470:20::2#53
Nov 16 18:07:27 info   using nameserver 216.254.136.227#53
Nov 16 18:07:27 info   using nameserver 216.254.141.13#53
Nov 16 18:07:27 info   reading /etc/resolv.conf
Nov 16 18:06:57 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:06:57 info   using nameserver 2001:470:20::2#53
Nov 16 18:06:57 info   using nameserver 216.254.136.227#53
Nov 16 18:06:57 info   using nameserver 216.254.141.13#53
Nov 16 18:06:57 info   reading /etc/resolv.conf
Nov 16 18:06:44 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:06:44 info   using nameserver 2001:470:20::2#53
Nov 16 18:06:44 info   using nameserver 216.254.136.227#53
Nov 16 18:06:44 info   using nameserver 216.254.141.13#53
Nov 16 18:06:44 info   reading /etc/resolv.conf
Nov 16 18:06:44 debug   dhcp6_reset_timer: reset a timer on sit1, state=INFOREQ, timeo=1550, retrans=116052
Nov 16 18:06:44 debug   client6_send: send information request to ff02::1:2
Nov 16 18:06:44 debug   copy_option: set opt_20 (len 0)
Nov 16 18:06:44 debug   copy_option: set option request (len 2)
Nov 16 18:06:44 debug   copy_option: set elapsed time (len 2)
Nov 16 18:06:44 debug   copy_option: set client ID (len 10)
Nov 16 18:06:27 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:06:27 info   using nameserver 2001:470:20::2#53
Nov 16 18:06:27 info   using nameserver 216.254.136.227#53
Nov 16 18:06:27 info   using nameserver 216.254.141.13#53
Nov 16 18:06:27 info   reading /etc/resolv.conf
Nov 16 18:06:05 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:06:05 info   using nameserver 2001:470:20::2#53
Nov 16 18:06:05 info   using nameserver 216.254.136.227#53
Nov 16 18:06:05 info   using nameserver 216.254.141.13#53
Nov 16 18:06:05 info   reading /etc/resolv.conf
Nov 16 18:05:29 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:05:29 info   using nameserver 2001:470:20::2#53
Nov 16 18:05:29 info   using nameserver 216.254.136.227#53
Nov 16 18:05:29 info   using nameserver 216.254.141.13#53
Nov 16 18:05:29 info   reading /etc/resolv.conf
Nov 16 18:05:29 debug   UDHCPD sending ACK to 192.168.0.222
Nov 16 18:05:29 info   ath1: STA c4:85:08:a7:6c:dc WPA: pairwise key handshake completed (RSN)
Nov 16 18:05:29 info   ath1: STA c4:85:08:a7:6c:dc RADIUS: starting accounting session 506DACEF-0000000B
Nov 16 18:05:29 debug   ath1: STA c4:85:08:a7:6c:dc IEEE 802.1X: authorizing port
Nov 16 18:05:29 debug   ath1: STA c4:85:08:a7:6c:dc WPA: received EAPOL-Key frame (4/4 Pairwise)
Nov 16 18:05:29 debug   ath1: STA c4:85:08:a7:6c:dc WPA: sending 3/4 msg of 4-Way Handshake
Nov 16 18:05:29 debug   ath1: STA c4:85:08:a7:6c:dc WPA: received EAPOL-Key frame (2/4 Pairwise)
Nov 16 18:05:29 debug   ath1: STA c4:85:08:a7:6c:dc WPA: sending 1/4 msg of 4-Way Handshake
Nov 16 18:05:29 debug   ath1: STA c4:85:08:a7:6c:dc IEEE 802.1X: unauthorizing port
Nov 16 18:05:29 debug   ath1: STA c4:85:08:a7:6c:dc WPA: start authentication
Nov 16 18:05:29 debug   ath1: STA c4:85:08:a7:6c:dc WPA: event 1 notification
Nov 16 18:05:29 info   ath1: STA c4:85:08:a7:6c:dc IEEE 802.11: associated
Nov 16 18:05:27 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:05:27 info   using nameserver 2001:470:20::2#53
Nov 16 18:05:27 info   using nameserver 216.254.136.227#53
Nov 16 18:05:27 info   using nameserver 216.254.141.13#53
Nov 16 18:05:27 info   reading /etc/resolv.conf
Nov 16 18:05:26 debug   ath1: STA c4:85:08:a7:6c:dc IEEE 802.1X: unauthorizing port
Nov 16 18:05:26 debug   ath1: STA c4:85:08:a7:6c:dc WPA: event 2 notification
Nov 16 18:05:26 info   ath1: STA c4:85:08:a7:6c:dc IEEE 802.11: disassociated
Nov 16 18:05:24 info   ath1: STA c4:85:08:a7:6c:dc WPA: pairwise key handshake completed (RSN)
Nov 16 18:05:24 info   ath1: STA c4:85:08:a7:6c:dc RADIUS: starting accounting session 506DACEF-0000000A
Nov 16 18:05:24 debug   ath1: STA c4:85:08:a7:6c:dc IEEE 802.1X: authorizing port
Nov 16 18:05:24 debug   ath1: STA c4:85:08:a7:6c:dc WPA: received EAPOL-Key frame (4/4 Pairwise)
Nov 16 18:05:24 debug   ath1: STA c4:85:08:a7:6c:dc WPA: sending 3/4 msg of 4-Way Handshake
Nov 16 18:05:24 debug   ath1: STA c4:85:08:a7:6c:dc WPA: received EAPOL-Key frame (2/4 Pairwise)
Nov 16 18:05:24 debug   ath1: STA c4:85:08:a7:6c:dc WPA: sending 1/4 msg of 4-Way Handshake
Nov 16 18:05:24 debug   ath1: STA c4:85:08:a7:6c:dc WPA: EAPOL-Key timeout
Nov 16 18:05:24 debug   ath1: STA c4:85:08:a7:6c:dc WPA: sending 1/4 msg of 4-Way Handshake
Nov 16 18:05:24 debug   ath1: STA c4:85:08:a7:6c:dc IEEE 802.1X: unauthorizing port
Nov 16 18:05:24 debug   ath1: STA c4:85:08:a7:6c:dc WPA: start authentication
Nov 16 18:05:24 debug   ath1: STA c4:85:08:a7:6c:dc WPA: event 1 notification
Nov 16 18:05:24 info   ath1: STA c4:85:08:a7:6c:dc IEEE 802.11: associated
Nov 16 18:05:06 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:05:06 info   using nameserver 2001:470:20::2#53
Nov 16 18:05:06 info   using nameserver 216.254.136.227#53
Nov 16 18:05:06 info   using nameserver 216.254.141.13#53
Nov 16 18:05:06 info   reading /etc/resolv.conf
Nov 16 18:04:57 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:04:57 info   using nameserver 2001:470:20::2#53
Nov 16 18:04:57 info   using nameserver 216.254.136.227#53
Nov 16 18:04:57 info   using nameserver 216.254.141.13#53
Nov 16 18:04:57 info   reading /etc/resolv.conf
Nov 16 18:04:41 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:04:41 info   using nameserver 2001:470:20::2#53
Nov 16 18:04:41 info   using nameserver 216.254.136.227#53
Nov 16 18:04:41 info   using nameserver 216.254.141.13#53
Nov 16 18:04:41 info   reading /etc/resolv.conf
Nov 16 18:04:41 debug   dhcp6_reset_timer: reset a timer on sit1, state=INFOREQ, timeo=1549, retrans=122628
Nov 16 18:04:41 debug   client6_send: send information request to ff02::1:2
Nov 16 18:04:41 debug   copy_option: set opt_20 (len 0)
Nov 16 18:04:41 debug   copy_option: set option request (len 2)
Nov 16 18:04:41 debug   copy_option: set elapsed time (len 2)
Nov 16 18:04:41 debug   copy_option: set client ID (len 10)
Nov 16 18:04:07 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:04:07 info   using nameserver 2001:470:20::2#53
Nov 16 18:04:07 info   using nameserver 216.254.136.227#53
Nov 16 18:04:07 info   using nameserver 216.254.141.13#53
Nov 16 18:04:07 info   reading /etc/resolv.conf
Nov 16 18:03:36 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:03:36 info   using nameserver 2001:470:20::2#53
Nov 16 18:03:36 info   using nameserver 216.254.136.227#53
Nov 16 18:03:36 info   using nameserver 216.254.141.13#53
Nov 16 18:03:36 info   reading /etc/resolv.conf
Nov 16 18:03:27 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:03:27 info   using nameserver 2001:470:20::2#53
Nov 16 18:03:27 info   using nameserver 216.254.136.227#53
Nov 16 18:03:27 info   using nameserver 216.254.141.13#53
Nov 16 18:03:27 info   reading /etc/resolv.conf
Nov 16 18:03:11 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:03:11 info   using nameserver 2001:470:20::2#53
Nov 16 18:03:11 info   using nameserver 216.254.136.227#53
Nov 16 18:03:11 info   using nameserver 216.254.141.13#53
Nov 16 18:03:11 info   reading /etc/resolv.conf
Nov 16 18:03:02 info   using nameserver 2001:4860:4860::8888#53
Nov 16 18:03:02 info   using nameserver 2001:470:20::2#53
Nov 16 18:03:02 info   using nameserver 216.254.136.227#53
Content-type: text/html

[FurryNutz]

Seem like the router or ISP modem is trying to do something.

Is DNS relay and Advanced DNS Service enabled?
ISP Modem still bridged?


Try this, use either your ISP DNS or Google DNS, input the primary and 2ndary DNS into the Setup/Internet/Manual/DNS. Apply then DISABLE DNS Relay. Save and reboot. You might have to restart the PC so it gets it's DNS cache cleared.

Check the logs again, still see the message? You shouldn't be seeing this flood of messages.

[lagonauta]

Router's wireless just stopped responding when 6 clients connected on 2.4GHz, there is some kind of serious firmware driver bug here. It was still working on 5GHz and probably wired.

I put one rotuer from the competition and it is working fine now, but I really like D-Link routers and I would love if this bug were fixed.

DNS Relay was active, and advanced DNS disabled.
ISP modem still bridged.

Tomorrow will try this fix as I can't to it right now.

[FurryNutz]

'I put one rotuer from the competition and it is working fine now, but I really like D-Link routers and I would love if this bug were fixed.' - What is this in regards too? Using a different router?

Possible there is a problem with FW and handling of 5 or more 2.4Ghz clients. One thing you might try, Turn OFF the 5Ghz radio and see if 2.4Ghz exhibits the same. If so, I would recommend you phone contact D-Link support, level 2 or higher. D-Link needs to be made aware of this problem. I might also check this router out at a different location, friend, neighbor or family members place and see if the problem follows just to make sure your external environment isn't interfering.

I think in mean time, if you can get as many devices on wired connections or use the 5Ghz radio for now, this should keep you going until D-Link comes up with a solution for the 2.4Ghz problem. Be sure when you call them that you have all the information, test details and such to give them so they can determine the best course of action. Let them know if you've tried different routers, radio modes and configurations and such. Any InSSIDer information and if other WiFi is near by. The more information they have the better they can figure out what needs to be done. Can refer them here so they can see what we've tried here as well.


Keep us posted please.

[lagonauta]

With the different router it worked perfectly, in the end I counted 10 clients on 2.4GHz and 4 on 5GHz. This router is at the same price range as the DIR-835.

Next weekend we are planning to have another LAN party, and I will try disabling 5GHz.
How can I contact D-Link support? Is it written somewhere on the box?

I couldn't test disabling the DNS Relay yet, but will do when I have the time. Would it reach the NAT table connection limit? I am just imagining 10 devices making lots of DNS queries at the same time while one is torrenting.

[FurryNutz]

http://www.dlink.com/us/en/contact-d-link

Please phone them and talk to level 2 or higher for this one. Tell them that you've done all the troubleshooting, mentioned trying a different router seems to resolve your problem using same clients.

May I ask what other router worked for you? Just curious.

I'll pass this along to my contacts as well here. I believe that this router should be able to handle more than 4 or 5 devices on wifi at a time. 


Please let us know how it goes.

[lagonauta]

I did not know if I was allowed to post its name here. It is one WD MyNet N750.
Feel free to edit my post if I should have sent to you by PM.

I will test 2.4GHz only this weekend, and then I will call them. What are their working hours? I am at GMT -5.
Should I call D-Link Canada or US? The one from US seems to be more organized as it has more than one phone number.

[FurryNutz]

No thats ok. just need to know. Not trying to hamper any competition. Where here to help you determine whats going on and best course of action. it does help to know that a different similar router is working so this give DLink a bit more information and hopefully will review it and fix it soon. Ya we all like DLink, so we do want to help them improve and let them know if any problems we find. Troubleshooting using other routers is desired and once all that has been exhausted, then it should help D-Link to find a solution.

I would call the U.S. I don't think it should make any different unless they are going to do an RMA or something like that. I don't think an RMA is needed here, rather something in FW needs to be done. I don't think this problem can be fixed by and RMA since you have tried it one 2 same model routers that exhibit the same thing. Are there any other D-Link model routers available there? It would be interesting to see if you could test say a DIR-857, or 827. I suppose i can try this on my 857 this week. I need to see if I can bring up that many wireless devices. I only usually have about 3-4 at a time online. I'll see what I can dig up and test to help this out here.

Thanks for your patient, efforts and time in this. I hope D-Link will be able to resolve this.

Keep us posted.