Cannot IP addresses

[Guest_imported]

I have a 209.39.123.0 IP scheme. I also have 22 WAN connections. I cannot add an IP to any machine on the local network, except 209.39.123....... Everytime I try to set ANY IP address on the local network it comes up with a network error, 'IP exists on the local network'. But I don't have that scheme set anywhere! Help

 

[hnd]

Make sure you are using a class c Subnetmask 255.255.255.0
hnd
hasso55@yahoo.com

 

[Guest_imported]

I am using a 24 bit mask

 

[Guest_imported]

I have isolated the problem to just a few routers. Althought they all worked fine before. I don't know why they would start acting up now?

 

[MWM]

...is this a routing or WAN IP error message or a LAN error message? If you simply unplug the WAN access and then try to apply the address, do you generate the same error?

This would at least indicate whether the IP conflict is a network addressing conflict or a host address conflict as place to begin.

Probably, as you say, it is really neither one, but at least this might narrow the field.

Yours,
Mike

 

[Guest_imported]

I did unplug the routers and I WAS able to apply the IP addresses. Although, I cannnot figure why this is just now starting to happen. I have turned off all of the Proxy ARP settings.

 

[MWM]

... So, if I understand the situation correctly, there is no error message when the inside network only is online. Perhaps the network portion of the IP address (not the host bits, just the network address, which is that portion of the entire IP address used by the router to make routing decisions, has the conflict.

What has changed in the router(s)? Are you the only admin person for them?

Next test: try to ping a new candidate address, which had before raised the error. It probably is not out there, really.

Best,
Mike

 

[Guest_imported]

You would be partly correct in saying that the network works fine without the outside routers. Although, I have found that a few of the routers seem to work fine and I have compaired all of the routers without any differences. Nothing has changed on these routers. I have added several other routers in the last few months. I disconnected the routers one by one and found that 12 of the routers cause this problem. I have even gone as far as reflashing the config file onto these routers from routers that already work, only changing the spid numbers and IP addresses.

 

[Guest_imported]

Anybody have any ideas. This is still stumping me

 

[MWM]

...well, money can buy some kinds of happiness, and if you throw some towards Cisco, I'll bet they can be helpful.

They have various support programs, for the excellence of which they are rightly proud. While it may seem like an admission of incompetance to ask for help (or to ask your boss for the funds) it really is not. This stuff is very complicated and people become expert is small facets of the IT world.

Then they charge others for their hard-won expertise.

When I bit the bullet and called Cisco it was well worth the cost in time and frustration, plus the confidence it gives, knowing that these intractable problems are usually solvable, and the answer, when you get it, is often surprisingly simple. Maybe that's encouraging, maybe not (!).

Yours,
Mike

 

[Guest_imported]

Not to proud to ask Cisco for help, as a matter of fact, I called them about this issue about 3 weeks ago. I gave them the problem and they sent me a packet analizer. I ran it and sent it back. They are stumped as well. Thought maybe someone has had this problem and stumbled onto the problem.

 

[sanyog]

Did you ever tried following, if not try once may be you can get hints.

Connect all the routers to your LAN and remove the links of the modems which are connected to the routers identified to give trouble. If this situation also let you assign the specified IP range, there is definitely some LAN connected to your s through WAN links.