Quote:
|
Originally Posted by trebor
that complicates things a little  when you can't even tell where on the network the problem is. no wonder NTL have so much trouble keeping things working 
so you will either have to have a look here http://homepage.ntlworld.com/robin.d...ips/index.html
or pm/email that trace route to somebody working in tech support and hope they can find out what piece of kit that ip belongs to.
but it is still a problem with the first hop a packet come to.
good luck you're going to need it. |
An IP address is an IP address, keeping track of a public one is just as easy as keeping track of a private one. Private IPs are used internally for:
* office desktops, which only access the net via proxies and don't need full internet access
* back end servers which don't need to access the internet and are easier to secure privately
* cable modems and set top boxes that only ever need to talk to the local dhcp server or ntl monitoring equipment.
* UBR gateway IPs for those cable modems which obviously have to be in the same range
Public IPs are a finite resource, so using private IPs for equipment that never needs to talk to the full internet is sensible, RIPE wouldn't be happy if we asked for 2,000,000+ public IPs to publicly address all the STBs and CMs. We do have databases with all this stuff on, you know!