WNDR3700: wifi drops and reconnects, strange logs

[Arnie-75]

Hello,
I don't know whats up with my wifi. Somehow, my WNDR3700v1 seems to drop the wifi connection and sometimes rejects my computer from reconnecting. Sometimes everything works fine for hours, then the wifi gets dropped and immediatly reconnected many times within minutes. Signal is strong so that is no problem.

I already switched channels, changes the wpa key, set 20 und 40 Mhz channels and even swapped my wifi card against a new one (both are Intel 6300).

Here is a log from my WNDR3700, I highlighted what I find strange.
Does someone have some knowledge and can tell me what might be happening here?


[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 20:04:16
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:58:05
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:56:22
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:55:41
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:54:52
[WLAN access rejected: incorrect security] from MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:54:42
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:48:52
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:46:08
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:43:06
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:42:25
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:39:40
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:36:39
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:35:06
[WLAN access rejected: incorrect security] from MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:34:56
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:34:26
[WLAN access rejected: incorrect security] from MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:34:16
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:33:35
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:33:05
[WLAN access rejected: incorrect security] from MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:32:54
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:30:32
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:30:03
[WLAN access rejected: incorrect security] from MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:29:52
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:29:30
[Internet connected] IP address: 77.23.0.150, Wednesday, September 21,2011 19:29:25
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:27:09
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:24:36
[WLAN access rejected: incorrect security] from MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:24:25
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:15:55
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:12:08
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:02:51
[WLAN access rejected: incorrect security] from MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 19:02:40
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 18:57:56
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 18:56:50
[DHCP IP: 192.168.0.4] to MAC address 00:xx:xx:f1:12:dc, Wednesday, September 21,2011 18:56:03
[DHCP IP: 192.168.0.2] to MAC address 00:xx:xx:yy:tt:rr, (my webcam) Wednesday, September 21,2011 18:53:53
[DHCP IP: 192.168.0.3] to MAC address 00:xx:xx:zz:ff:ss, (my mobile phone) Wednesday, September 21,2011 18:52:24
[Time synchronized with NTP server] Wednesday, September 21,2011 18:52:00
[Initialized, firmware version: V1.0.16.98] Wednesday, September 21,2011 18:51:58

I also posted this in the Netgear forums.

 

[thiggins]

If you are having this problem with only one client, I'd see if that client has problems maintaining connections with other routers if you can.

Did you change anything on the router or client side that you can relate to the start of the problem?

 

[Arnie-75]

I also wondered why my computer is the only device showing this error and that is why I already swapped the wifi card against an identical Intel 6300.

I don't remember changing anything else. The only thing I changed about one year ago was the router istself. I don't know when this problem became apparent because I did not find it very annoying. It looses connection but reconnects seconds later. Only recently this began to to annoy me.

I will try the Netgaer WNDR4000. Hopefully it fits to the wall mounts of my WNDR3700.

 

[thiggins]

Try deleting the WiFi profile and redoing it. Also check for an Intel driver update.

 

[Arnie-75]

Thanks, done both many times.

 

[Arnie-75]

Just got the new WNDR4000. I will report back if anything changes.

 

[Arnie-75]

I got the WNDr4000 and this device seems to keep the wifi connection.

Nevertheless the log shows many entrys where the same IP-address is given to my computer again wihtin minutes. Ist this normal or is it a sign of some error?

[DHCP IP: 192.168.0.2] to MAC address 00:xx:x7:F1:12:xC, Tuesday, Sep 27,2011 17:36:06
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:35:46
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:35:12
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:34:38
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:33:53
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:33:20
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:32:37
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:31:55
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:31:41
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:31:17
[DHCP IP: 192.168.0.2] to MAC address 00:xx:x7:F1:12:xC, Tuesday, Sep 27,2011 17:31:15
[DHCP IP: 192.168.0.2] to MAC address 00:xx:x7:F1:12:xC, Tuesday, Sep 27,2011 17:30:56
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:30:30
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:29:58
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:29:48
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:29:36
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:29:07
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:29:04
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:28:34
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:28:21
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:27:49
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:27:05
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:26:50
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:26:32
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:26:21
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:26:12
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:25:46
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:25:10
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:25:10
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:24:27
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:23:55
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:23:16
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:22:32
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:21:49
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:21:47
[Time synchronized with NTP server] Tuesday, Sep 27,2011 17:21:38
[Internet connected] IP address: 77.23.4.28, Tuesday, Sep 27,2011 17:21:38
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:21:14
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:21:08
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:20:34
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:20:24
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:20:02
[UPnP set event: Public_UPNP_C3] from source 192.168.0.2, Tuesday, Sep 27,2011 17:19:51
[DHCP IP: 192.168.0.2] to MAC address 00:24:x7:F1:12:xC, Tuesday, Sep 27,2011 17:19:44

 

[stevech]

reissuing the IP quickly - to me, suggests that the client PC is losing association / signal and searching again, then re-associating. In doing so, it will send a new DHCP request resulting in the IP reassignment (the router elected to reuse the same IP, though it may elect to use a new IP).

On the client, in a command window, run a ping, like
ping -t 192.168.1.1 (or whatever the router/gateway address is)

and see if pings are dropped in a recurring pattern. This, and the wifi manager in the tool bar may show that the re-associations are occurring.

There is a router setting for DHCP renewal time (lease time) - normally defaulting to many hours. It would affect all clients.

Another experiment: Change your client to use a static IP on the WiFi card. Choose an IP that's not in the DHCP range, and doesn't conflict. The gateway address will be that for your routers. The manually set DNS address can be 4.2.2.2.
Then run the ping -t and see if what happens. The static IP will avoid DHCP issues.

 

[Arnie-75]

Just did the ping -t an no dropouts.

 

[Arnie-75]

I will keep the WNDR4000. Works fine, even my wireless printer stays connected, while it didn't with the WNDr3700.

After mailing with Netgear they will replace my WNDR3700. I will probably sell it on ebay.

 

[Greg_Elite]

I will keep the WNDR4000. Works fine, even my wireless printer stays connected, while it didn't with the WNDr3700.

After mailing with Netgear they will replace my WNDR3700. I will probably sell it on ebay.

Get a Linksys E4200. Best router currently on the market.

 

[Arnie-75]

Very helpful answer.
Why should I sell my WNDR4000 and buy an E4200 if the former works fine??