|
#21
|
|||
|
|||
|
Quote:
Wearing me out going up and down stairs to reset my equipment mind you after doing that a few times, then suddenly the router started to refuse to pick up it's own IP Address from my ISP, that had me going for a while as well. Plug my laptop into the back of my Cable Modem, DHCP off of it, no problem get a public IP address from ISP. Take Wifes Laptop same thing no issues there. Kids Laptops they work as well... plug cable modem into routers WAN port it goes brain dead, WAN address shows 0.0.0.0 call ISP they see no issues with cable modem, and I can verify no issues as well because direct connect devices work. Oh Cable modem is also a Netgear CMD31T... finally figured if Cable modem giving address out to all my laptops, screw it, I'll just tell it to clone the MAC address - didn't have to do it before, but suddenly now it has to be done. With all the crap I've seen with .90 I rolled back to .88 myself, so lets see if this version of the firmware works and is stable. BTW: Anyone ever read the release notes for each firmware update, how's that for broken Eng-rish. I can only imagine where this firmware is being written.
|
|
#22
|
||||
|
||||
|
I sent my config file to a netgear engineer who replied back with a temp fix while he tries to duplicate problem. Back .90 now for a week now everything seems to be working fine.
Cloning, spoofing WAN mac does save a lot of footsteps when changing devices behind a cable modem. Another trick to try is to remove WAN cable for a few seconds when trying to get public IP from modem when release renew IP fails to work. One thing I have noticed or done with these 4000's is to reset to default and reload FW to cleared some problems. I upgraded my Data to 115 down and 20 up and other than ping time I see now difference between wired and wireless |
|
#23
|
|||
|
|||
|
What was the temp fix they had you perform?
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|