On Wed, 29 Jul 2009 05:18:46 +0100, Kyote <>
wrote:
>
> ok
> both computers can see the router's ip of 192.168.1.1.
> both computers can open the routers UI using that IP(192.168.1.1).
> both computers can use the routers UI to ping the Cable modem.
> both computers can ping the cable modem's IP of 192.168.100.1 from a
> cmd prompt.
> The router's routing tables can see both computers.
> Neither computer can connect to the internet through the router.
> both computers when connected to the cable modem directly cannot ping
> the modem.
> both computers also cannot open the UI of the modem when connected
> directly.
> both computers cannot access the internet via the Ethernet port.
> both computers can access the internet via the USB.
>
> To me this seems strange. I mean why can they see the cable modem when
> connected to the router, but not when directly plugged in to the cable
> modem?
>
Because when the PCs connect to the router they send a DHCP request out to
get their settings, and the router's DHCP servers allocates them an
address on the 192.168.1.* sub-net which they use there IP address. Then
when they send anything to an address not on that sub-net the router
passes it through the firewall and out the internet port to the modem -
which either responds to it if it is addressed to 192.168.100.1 or passes
it on.
When you connect the PCs directly to the modem via ethernet then when they
send the DHCP request the modem ignores it and the PC doesn't get a IP
address, and falls back to its factory default settings - which aren't
suitable in this case.
> Seeing the modem through the router indicates to me the Ethernet port
> on the CModem is working fine. Same with the Ethernet ports on each
> computer and the router. All Ethernet ports are fine. Also all are
> connected properly. But then when they try to connect directly to the
> modem and access or ping the modem it fails utterly.
>
>
So everything is now reconnected as it was before the reorg.
So it looks like some setting was lost.
Connected via the modem connection tests:
Lights on the modem before enet, sync, ready on.
In a command prompt run
ping 74.220.195.50
The enet, send, and recv, lights should flash briefly and you should get
back a response time.
If you get an unreachable address then you have a routing problem on
either the router or all the PCs.
If you get a timeout and:
enet remains on - router not routing external traffic correctly.
enet flashes, send remains steady - modem not forwarding traffic.
enet and send flash, recv remains steady - modem not connected?
All flash - routing problem with reply?
You might want to try this with the USB connection to see how the lights
should be.
If you get a response time then try
ping bluehost.com
This should be about the same - but with more flashing.
If you get a can't resolve address reply - then the problem is in the DNS
settings - probably on the router, but check the PCs are set to get their
DNS automatically.
Go to both devices web interface and check logs, and status pages.
--
Using Opera's revolutionary e-mail client:
http://www.opera.com/mail/
Similar Threads
Linear Mode
