I am a veteran Windows user and .NET programmer who has been thrown into the Linux world so please bear with me. We are migrating our network and have run into an unusual problem. The guy who is the real guru here is a fan of Oracle VM's. I am still not sure what the heck those are or why they are different. Our DBA has set up all four of our databases as Oracle VM's. I'll call them DB1, DB2, etc.

Here is the problem. On DB1 and DB2 we keep getting connection reset by peer errors every 60 seconds. When we try to ping DB1 from DB2 we get Host Unreachable errors.

Now for the weird part, From DB1 I can ping any other server on the network including DB3 and DB4. From DB2 i can ping any other server on the network as well. It's just these two that won't talk to each other.

I have checked everything I can find on the internet. Any suggestions would be greatly appreciated. Thanks in advance.

Hi,

Welcome to LQ!

You could check the 'kernel route table' for each of the machines with the 'route -n' from the cli. How is the LAN setup?

Thanks for the quick response. Here are the results of the route -n command:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
xxx.xxx.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

*Note: I replaced the address with the X's. I think that was our static IP of the DSL.

I am just a dumb .NET programmer who got put in the position of Tech Lead on a Linux system, so bear with me. When you ask how the LAN is set up, I'm not sure what you mean. I'll do my best to answer. We have six servers set up with Linux as the main OS. There are several VM's on each server, mostly Linux but a couple of Windows 2003 server VM's. All is hooked to a static IP DSL connection. Everything provides service to the office users, about 15 laptops/towers. I hope that's what you were asking for. If not, just let me know.

Hi,

What about the other servers on your LAN? Compare the tables. Make sure everything has a pathway.

Our Linux Guru finally carved out enough time to fix this problem. We were redefining our IP Addresses and I believe we had defined the same address twice. When we corrected that the problem cleared up.