Quote:
|
Originally Posted by hjf288
http://192.168.100.1 is unreachable - Pinging 192.168.100.1 is unreachable = The only way getting to it is if the default gateway is 192.168.100.1. Ambit 200 cable modem via ETHERNET
|
What operating system are you getting these results with? Is this in an ex-C&W region of the country, or an original NTL region? Using Windows XP and an Ambit 100 in an original NTL region does not have this problem, and of course there are thousands of NTL users who happily read diagnostics from their Ambit via 192.168.100.1 using their web browser while online. So if you cannot do this, something must be different. Either the Ambit 200, or the ex-C&W setup, or the operating system.
There is one interesting misfeature of at least some (maybe all) of the Ambits: if you send a request to 192.168.100.1 during normal online working, the reply packets are labelled as coming from the ISP-side private IP address, and the replies are routed via the CMTS head-end (UBR) and back again (tromboned), rather than directly from the SACM to the PC. This reply might be blocked by security settings in the CMTS in the ex-C&W region. This mis-match of response IP address might cause routers and firewalls to drop the replies.