blueyonder cable modem IP address

John_Gray

I am slightly puzzled that I now get no response from 192.168.100.1, the address of the blueyonder cable modem. Previously if you plugged that address into a browser you got 'useful information' about the state of the cable modem. Any attempt to PING it now times out, TRACERT just gives asterisks where it should give the timings, and so on.

I've tried powering the cable modem off for varying lengths of time, disabling the software firewall on one PC (I can't easily disable the hardware firewall router because that's providing DHCP for my PCs).

Everything else works! Browsing, you name it -- all OK!

Has anyone any clues as to what might have happened? I had thought that BY might have changed the IP address via a new configuration file, but that seems fairly unlikely. Could they have disabled browser access by 'users' to their cables modems?

I remain puzzled, but open to suggestions from anyone who could shed light on this non-life-threatening experience!

John

electron_3

John_Gray wrote:

Could they have disabled browser access by 'users' to their cables modems

Yes as they have handed their IP address services to a new company
what this means is that IP changes should happen quicker rather than about
a week for a new DHCP IP it now takes about 24hrs on average.

John_Gray

I see your point, but I'm talking about the internal IP address, as seen from the local user side, not the 10.xx.yy.zz IP address which it would have from the outside...

John

electron_3

John_Gray wrote:

I see your point, but I'm talking about the internal IP address, as seen from the local user side, not the 10.xx.yy.zz IP address which it would have from the outside...

John

Wierd works for me

This help http://homepage.ntlworld.com/robin.d.h.walker/cmtips/ipaddr.html

CIS

What browser are you using ?, Ive seen problems reported on other sites whether firefox users could not access the modem status page.

Chriswil

Try 192.168.1.1 - quite a usual address from modems...

John_Gray

No, sadly it doesn't work with either Firefox and IE, and it used to work on 192.168.100.1 quite happily for a couple of years. Because of the router default, my local subnet is 192.168.11.x (no point changing it!).

I'm looking into Electron's link, which suggests it might be associated with using DHCP on the router rather than fixed IP addresses, but I won't have time now to play until the weekend.

Thanks for answers!

John