Had two of the same IP's, how do I clear the damage?

  • Thread starter Thread starter ToddAndMargo
  • Start date Start date
T

ToddAndMargo

Hi All,

I set up an OpenVPN tunnel between two sites. I goofed
and had the same IP address (192.168.255.100) on each end.
I have corrected the problem.

Problem: every machine on the network works fine with the
new IP addresses (192.168.255.100-local, & 101-remote),
except the original machine (192.168.255.50) I was doing
the testing on. It can not see the 192.168.255.101 at
the remote location. (Everyone else can, but not .50)

Is it possible that its routing tables are messed up?
How do I do a mass clear and start over? How do I
clear the damage?

Many thanks,
-T
 
hi there Todd & Margo,

Im not too up on routing tables, BUT... when setting a route, in the command
line, there is an option to make the route change perminant (-p), otherwise
after a reboot - the additions to the table are lost, therefore - reboot the
machine, unless you made perminant changes to the machines routing table, all
should be reset.
 
hi there Todd & Margo,

Im not too up on routing tables, BUT... when setting a route, in the command
line, there is an option to make the route change perminant (-p), otherwise
after a reboot - the additions to the table are lost, therefore - reboot the
machine, unless you made perminant changes to the machines routing table, all
should be reset.
Click to expand...

I was hoping a reboot would work, but didn't. I suppose I could
manually delete every route and reboot. Any thoughts?

-T
 
not sure m8 - if i was in the same situ, i would probably force change the
fixed ip to something else, then back again, i guess then the system would
re-write the routes? - just a stab in the dark though...
 
'route print' at a command prompt should give you the routing info. Compare
the faulty machine's routing table with a working one.

The standard entries you see in here are created by the LAN card's TCP/IP
entries. If they are incorrect it's most likely because the LAN card's
default gateway, etc. needs correcting. Check these first.

You can experiment with the 'route add' command provided that you don't add
the persistence flag, and a reboot will then clear your changes.

I imagine you already know that you can use the ping, tracert, netstat and
nslookup commands to help diagnose the problem.
 
Anteaus said:
'route print' at a command prompt should give you the routing info. Compare
the faulty machine's routing table with a working one.

The standard entries you see in here are created by the LAN card's TCP/IP
entries. If they are incorrect it's most likely because the LAN card's
default gateway, etc. needs correcting. Check these first.

You can experiment with the 'route add' command provided that you don't add
the persistence flag, and a reboot will then clear your changes.

I imagine you already know that you can use the ping, tracert, netstat and
nslookup commands to help diagnose the problem.
Click to expand...
Thank you!
 
Back
Top