right, the fact you have gone from than STB to the stand alone cable modem (NTL250) is usually a good thing.
the fact is, if your supplyed info and that screenshot is right , your cable modem IS conected to the router and given it the WAN IP so again that seems right, the problem must most likely be the IP your PC is useing, is the router DHCP server working and giving out the right IP for the lan.
(edit:
hmm just noticed the WAN on the picture is blank that is your problem so try the * below)
your WAN has got a 80.**.**.** yes?, i seem to remember that IP range usually dedicated to STB's as all the stand alone cable modems iv seen get in the 82.*.*.* (wythenshawe, south manchester) range but its possible i suppose.
the IP of the router says 192.168.2.1 yes?
does the IP of the PC your using also have the 192.168.2.* range, i assume it does, or you couldnt connect to the router.
does the router have a page were you can enter an IP or web url and ping a site?, if so ping something like
www.ntlworld.com and you should get a response, that proves the router is working and getting a useable VM IP...., then in that case it seems it must be the lan part between the router and the computer, but its a puzzle as you can connect to the internal web server of the router already.
you say the new NTL250 directly connected to the PC gives a valid IP and works, what IP range does it have then?, still the 80.*.*.* ?.
if the router is not getting a ping even though its got what seems like a valid WAN IP ,
*while it shouldnt be needed , i usually like to temp clone the router MAC in the PC network card rather than the other way around, as then you will see if it works directly wired to the PC (with router removed)and then hopefully (dont forget to reset the PC card MAC back) when you reconnect the router to the NTL250 any NTL side setting will see the router MAC as it was just working with that MAC a minute ago (and that blank WAN address in picture should have a 82.* in there).
---------- Post added at 08:41 ---------- Previous post was at 08:04 ----------
Quote:
Originally Posted by Russell
Hi ayjayoh21, XBrav,
Aj's screenshot looks very familiar... unfortunately. :-(
I did manage to get a connection tonight, just once when I changed the cable between the router to the PC from a cat5E to a cat6. However I couldn't get to the Virgin homepage; I timed it out after waiting 5 minutes. I was unable to reproduce this when I recycled the cables.
However, from what you say earlier, I can at least rule out Vista as a probable cause.
|
what , you have more than one network card in your PC?, make sure the one connected to the router is set for DHCP client, (windows OS, general/internet protocol[tcp/ip] obtain an IP address automaticly)OR, you could set the card for a fixed IP and make sure the router also has that IP in its fixed setting page.
its the same if your wired or wirelessly connecting, eather DHCP client or fixed IP both ends.
is your router status page got a valid WAN or is it blank as above?, you need that WAN address filled in or the router isnt talking to the VM modem.