View Single Post
Old 25-09-2007, 11:31   #5
popper
Inactive
 
Join Date: Jan 2006
Posts: 3,270
popper has a bronze arraypopper has a bronze arraypopper has a bronze array
popper has a bronze arraypopper has a bronze arraypopper has a bronze arraypopper has a bronze arraypopper has a bronze arraypopper has a bronze array
Re: Strange Router Problem

Quote:
Originally Posted by 42Neil View Post
I've been having a few problems recently with my net connection disconnecting under heavy load, requiring a reset of the cable modem.

After trying a few things to fix this, I decided to try a new router, to see if that would fix the problem. So I bought a new router (Netgear WRG614) and tried that, but the disconnecting problem was still there.

So I decided to take that router back and go back to my old one, but now for some reason my old router doesn't work any more!

The old router is a Linksys WRT54G, and I am trying to connect using a wired connection, but it just won't work any more. All of the settings are the same as before, but I cannot connect to the web through it any more.

I can access the router via it's IP address (192.168.1.1) and all settings look fine, and I can also access the cable modem's IP address (192.168.100.1). I can even ping web addresses from the router's admin page, but I just can't connect to the web.

Is it possible that Virgin Media are now blocking my old routers MAC address for some reason?

Anyone have any bright ideas as to what the problem may be? It's driving me mad!


hmm thats a very odd one!.

the 'disconnecting under heavy load, requiring a reset of the cable modem' one is easy enough to explain, (older, and not so old) many (wireless)routers CPU's cant cope with the load and so fall over, and forget the WAN address/route type fault, and as already said, reducing the overall load per second helps stop it falling over.

the fact you can ping from inside it and get a response means the UDP DNS etc is working and so the IP must also be valid, or at least valid within the VM internal network.

did you check to see if it was now still getting a true WAN IP that is viewable/pingable externally to VM network, something in the 80.* 81.* 82.* and now they seem to also use 62.* range, perhaps more?.
popper is offline   Reply With Quote