Experience with 1.0.16.98 for V1?

[Simon0]

Originally Posted by TitaniumDust

I too have connection problems with 1.0.16.98 (and 1.0.14.98 also). Its just like the version previous to 1.0.7.98, which was pulled from the website - 1.0.4.98 was it? It too had massive connection problems. Sometimes random web connections will simply time out, but you might turn right around and it will suddenly work. I encountered the problem with 2 different browsers, and also with 2 anti-malware programs with auto-update functionality. It also happened trying to connect to Steam, so its definitely the router. Going back to 1.0.7.98 gives no problems whatsoever... been running it since it came out and it has been the best firmware to date, easily. Note that I tried erasing the settings on the router status page, and set up everything manually with 1.0.16.98, but still had the connection problems.

Are those wired or wireless connections. For wireless, AVOID mixing -g & -n devices, setting up a cheap AP for those -g devices may help.

Steam can open MASSIVE # of connections & some router firmware may be set too SENSITIVE and perceive it as an attack by dropping those connections and exhausting the "MEASLY" 4096 connections present. You may consider a separate free x86 router or 3rd party firmware or a router which has more firewall controls, settable # of connections, etc... smallnetbuilder has some good info on this.

I've used m0n0wall & pfSense w/ wndr3700v1 as an AP w/ great success!

[Danmarc]

I upgraded to 1.0.16.98 and I started the "schedule" feature in "Advanced Wireless Settings, between midnight and 5 am. The router turned off the signal at midnight but didn't restarted at 5 am. I had to enter the settings and restart the wireless manually.

[TitaniumDust]

Originally Posted by Simon0

Are those wired or wireless connections. For wireless, AVOID mixing -g & -n devices, setting up a cheap AP for those -g devices may help.

Steam can open MASSIVE # of connections & some router firmware may be set too SENSITIVE and perceive it as an attack by dropping those connections and exhausting the "MEASLY" 4096 connections present. You may consider a separate free x86 router or 3rd party firmware or a router which has more firewall controls, settable # of connections, etc... smallnetbuilder has some good info on this.

I've used m0n0wall & pfSense w/ wndr3700v1 as an AP w/ great success!

Those are wireless connections. I only have n devices in the house (no g or b for that matter). I'm running both the 2.4 and 5 GHz channels simultaneously. The same setup with fw 1.0.7.98 has never given any type of connection problems whatsoever, under exactly the same circumstances, using exactly the same software, on exactly the same PCs. This is why I wanted to report my findings in this thread. Simply using fw 1.0.7.98 does the trick for me, but its a bit unsettling to see these types of problems arise (again) in a new firmware. In case it helps Netgear or anyone else, my router is "WNDR3700-100NAS" (v1 router) and it has another non-serial number "100-1394-01R15". I've read about antennae dying on other R15 units but I've never had any such problem.

[Simon0]

Originally Posted by TitaniumDust

Those are wireless connections. I only have n devices in the house (no g or b for that matter). I'm running both the 2.4 and 5 GHz channels simultaneously. The same setup with fw 1.0.7.98 has never given any type of connection problems whatsoever, under exactly the same circumstances, using exactly the same software, on exactly the same PCs. This is why I wanted to report my findings in this thread. Simply using fw 1.0.7.98 does the trick for me, but its a bit unsettling to see these types of problems arise (again) in a new firmware. In case it helps Netgear or anyone else, my router is "WNDR3700-100NAS" (v1 router) and it has another non-serial number "100-1394-01R15". I've read about antennae dying on other R15 units but I've never had any such problem.

I had an "R15" and it was unstable. Wired port issues. Another one had 5GHz instability. It's nothing specific it seems, just bad. I've got a R17 right now and is working good. Firmware will not fix serious hardware issues..

[gringopig]

Originally Posted by SkykingUSA

Sir, could you please tell me what model and size hard drive you are using on your USB port? I have one connected to mine, and I suspect that is the cause of all my lockups and freezes every week or so. I'm at the point where I will try this new firmware to see if the crashes stop, then I'll try the OpenWRT firmware, and if none of that works, I'll just remove the USB hard drive and go back to my old slow NAS until I get a better one. Sigh. Frustrating.

I've got one of these: http://www.wdc.com/en/products/products.aspx?id=480

320GB model.

I have it attached 24/7 and changed the workgroup to match my own and have only the internal network connection enabled. No specific network folder was created but the share appears nonetheless as 'Readyshare' in my network.

I have it formatted as ext3.

Quite pleased with it!

[gringopig]

I did disable the traffic meter using the telnet batch file I downloaded from a user here also...

[SkykingUSA]

Originally Posted by gringopig

I've got one of these: http://www.wdc.com/en/products/products.aspx?id=480

320GB model.

I have it attached 24/7 and changed the workgroup to match my own and have only the internal network connection enabled. No specific network folder was created but the share appears nonetheless as 'Readyshare' in my network.

I have it formatted as ext3.

Quite pleased with it!

Thanks for that info. I have a similar setup to you regarding the USB drive, but mine is a 1 TB drive which apparently is not on the unofficial supported drives list. That is why I think it's causing my problems. Thanks again for the quick reply.

[KiccoLSD]

In order to use AP mode is advisable to use WAN port? (With .14 it was necessary to avoid bugs)
Upgraded yesterday only to access to webgui it needed 3 reset. Using AP mode i founded WNDR3700 after 12Hrs with Webgui freezed and WiFi not working (SSID listed but cannot connect). Power cycle and now is working... I fear that this is a buggy fw release!

[lagerblad]

In the release notes says:
Support "AP mode" and "Auto IP" in AP mode.
Has anyone found any documentation for this feature?

[KiccoLSD]

Using WAN port AP Mode doesnt' work