Discussion Locked

Private IP Address rejected-already used

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We've got a block of IP addresses from our ISP, all public. We have a dedicated ISDN internet connection. I'd like to start moving all our internal ip addresses to non-routable addresses in the range of 192.168.x.x. When I try to bind one of these ip addresses, it fails because it detected this address on the line already. I know for certain the address is not in use on our network. I can trace the address, and it goes thru the Ascend Pipeline 75 router up to our ISP. The pipeline router has firewall capabilities in use already. I cannot figure out 1) why the router is routing the ip address "check-to-see-if-already-in-use" request thru to the ISP, and 2) How do I block this request, or limit it to the internal network. I know the ISP routers are designed to block the non-routable ip addresses. This behavior is occurring Win98 computers, Win2k computers, and the Netware 4.11 servers. None of the computers will allow me to bind a private ip address, reporting that the addressin question is already in use at mac address xxxx.

7 replies

by some guy in seattle

If you are going to use private IP ranges and still access the internet there is going to have to be some kind of Network Address Translation (NAT). You may be able to do this on your router (I'm not familiar with Ascend) but, if not, I believe Win2000 has a native NAT service through which your private IPs can be translated into public IPs.

Hope that helps,

by bpalmer

I can do NAT thru the router. I can't enable this at this time because that would effectively cut off access to my mail server from the outside world by hiding it's ip address. What I need to know at this phase of testing is how I go about gettingthis non-public ip address assigned to an internal nic without having the os go outside the router to check for the pre-existance of the ip address on the larger internet. Thanks though!

by ebob

The problem remains that your existing systems are NOT on 192.168.a.b, and so forward packets to your router, which is also NOT on this network.

In that case, you will need to setup the 192.168.a.b network on the inside of your router, too. Thereare a couple of ways of doing this. The cleanest is to have a 2nd LAN interface, and configure it on the private network. Then add a hub/switch and start moving PCs over. In your case one at a time.

Another way to do this is to add a secondary address to your existing LAN interface. Some routers let you do this, some do not. If yours does, then you can simply start to change IP addresses on your PCs...

One other way to apporach this is to add a 2nd router, with 2 LAN interfaces. One on your existing network, and one on 192.168.a.b. Then on this 2nd interface, add a hub or switch, and start moving PCs over. You may need to tell your first router that 192.168.a.b is accessible through the LAN interface of the new router. This can be done with a static route, or perhaps with routing protocols. Details dependent on the specifics of your implementation.

In any of these cases, now your networks will "know" where to go for 192.168.a.b.

by bpalmer

I understand this. This is exactly what I'm trying to do. I want my internal lan to be the 192.168.x.x range. If every computer on my lan is in this range, including my server, the subnet mask will indicate that all adjacent computers are on samesegment. The problem comes in when I try to bind the 192.168 address as a secondary IP to the server NIC. I've tried it with installing a separate NIC and binding the private address. No dice, the ip address "checking" goes along the wire, eventually hits the isdn router, and travels up to the ISP router, where it responds that the address already exists. I need to know the mechanism TCP/IP uses to determine whether an IP address already exists on a wire, so I can block that signal at my router. Your opening statement would be true if I already had IP set up on the computer, and had a gateway address set up on the computer. As there is no gateway address listed at this point, I don't think the router will actively listen for random packets floating around with this "unknown" ip address, and decide to route the packet out to the other side of the router. Thanks for trying, I appreciate it.

by mckaytech

I have two thoughts on potential causes. First, and most likely, the Pipeline 75 supports both routing and bridging. It seems to me that if bridging were enabled, this kind of behavior might result.

The second and less likely thought is that this device also supports DHCP spoofing and I'm wondering if it would make any difference if you chose another non-public address range (e.g. 10.x.x.x).

paul

by bpalmer

I ran a telnet session to the router, and it does indeed have bridging enabled. I disabled the bridging, but the router would no longer dial the ISP thru the ISDN line. This doesn't exactly let me test whether this is the cause or not, but the fact that you nailed the bridging aspect of the router would indicate that this is probably the path towards the solution. Thanks for your help!

This discussion is closed to new replies.