New
#11
the only one that might not be secure to share, would be your default gateway...
does your "valid ip's" your getting happen to start with 169. ?
the only one that might not be secure to share, would be your default gateway...
does your "valid ip's" your getting happen to start with 169. ?
you'll have this problem with so many devices on a home network router. netgear told me that a home router should handle up to 5 or 6 devices without issue.
I have a similar issue with a windows 7 laptop.
it seems to only want to use the same ip it had when you turned it off last and doesn't want to search or should I say "get a new one" when I turn it on. I have to do it manually.
netgear recommend I put it's ip as static and then set that ip address to that device only in the router's settings. but that actually made things worse. it would then instead take over the other ip addresses the other devices were using. netgear support said that shouldn't happen and they were out of ideas.
The MAC filtering was put in place in an attempt to try to fix this. I will disable it.
The router firmware is up to date. We bought a new one thinking our old router wasn't able to handle so many devices.
Here's the crashed ipconfg /all
Would it help to post an ipconfig /all when running?removed
Last edited by CaptPhil; 27 Oct 2011 at 16:14.
You bought a new router? and still have same problems? id call your ISP and let them know, your modem, might have gone bad....I wouldnt normally say that, but i had similar issue's this past weekend, but my house modem was about 8 years old. They came and replaced it the next day, and i can handle probly around 20 hosts fine now.
if the case for sure is that you cant connect more than so many user's I still think its a DHCP issue, can you post your network range setup, etc... i see its a class C obviously but im curious if something might be off a little
Check the DHCP scope on your router. make sure its not set for less devices than is on your network (i.e. it is giving out addresses at least 10 addresses from 192.168.0.2 - 192.168.0.11)
Did you try a static IP on the wireless? Can you connect with a cable with no problems?
When it crashes next check the IP addresses of your other devices to make sure there isnt a conflict.
Dave
DHCP scope is set from 2-242. I can connect wired no problem, but have to recreate the crash situation to see if wired will survive the scenario. Will do and report.
Testing today... when left hard-wired, it seemed to stay connected. It was a single shot test though.
I bought a new router today. a netgear N300 all of my issues went away.
you have a much better router than me but a lot more connected devices.
Test may have been flawed, so disregard that.
Anyway, I ran an ipconfig /all both connected and crashed, looking for any differences between. (other than lease obtained/expired)
The differences:
Working:
As far as I can tell, this bolded line is the only difference between the two. I have no idea what it means.Connection-specific DNS Suffix . :
DHCP Server . . . . . . . . . . . : 192.168.1.1
Last edited by CaptPhil; 31 Oct 2011 at 10:50.