Destination host unreachable

I think I'm going crazy.  I could use a fresh set of eyes to help me figure out what is wrong.

I spun up a new virtual Windows Server 2008 R2 standard machine yesterday.  Connected it to the domain, installed windows updates, pushed out anti-virus, etc.  

When I attempted to push the backup agent to the new server it began to fail  The backup server could not connect to the new server.  Ping testes reveal the following:

Pinging newserver.domain.com [10.1.20.131] with 32 bytes of data:
Reply from 10.1.20.142: Destination host unreachable.
Reply from 10.1.20.142: Destination host unreachable.
Reply from 10.1.20.142: Destination host unreachable.
Reply from 10.1.20.142: Destination host unreachable.


If I go to the new server and ping back to the backup server I get the following:

Pinging backupserver.domain.com [10.1.20.142] with 32 bytes of data:
Reply from 10.1.20.142: bytes=32 time=1ms TTL=128
Reply from 10.1.20.142: bytes=32 time<1ms TTL=128
Reply from 10.1.20.142: bytes=32 time<1ms TTL=128
Reply from 10.1.20.142: bytes=32 time<1ms TTL=128


Then, if I go back to the backup server I can now ping:
Pinging newserver.domain.com [10.1.20.131] with 32 bytes of data:
Reply from 10.1.20.131: bytes=32 time<1ms TTL=128
Reply from 10.1.20.131: bytes=32 time<1ms TTL=128
Reply from 10.1.20.131: bytes=32 time<1ms TTL=128
Reply from 10.1.20.131: bytes=32 time<1ms TTL=128



Now, if I wait ~10 - 15 minutes, the backup server will once again fail to connect to the new server and show "destination host unreachable" again.


Both servers are on the same subnet, using the same gateway, with only ipv4 enabled.  Windows Firewall is disabled.  The newserver is serving file shares, which continue to be accessible.  The backup server has no problem accessing any other servers on the same subnet.

Any ideas of what I can look at to figure out why the backup server will lose connection to the new server without having the new server first ping the backup server?

Thanks for any suggestions.
brett_apfcAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

HalldorGCommented:
First guess ip address conflict.

From some other machine try ping your hosts ip address.
Then check the arp entry and check if it matches your hosts physical address

arp -a

Then try disconnect your host from the network and try ping it again.
Check if the arp for the entry has changed
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
brett_apfcAuthor Commented:
ARP is displaying the correct MAC address of the host in question:

 10.1.20.131           16-f4-de-8a-f1-27     dynamic


Connection-specific DNS Suffix:
Description: Citrix PV Network Adapter #0
Physical Address: ¿16-F4-DE-8A-F1-27
DHCP Enabled: No
IPv4 Address: 10.1.20.131
IPv4 Subnet Mask: 255.255.255.0
IPv4 Default Gateway: 10.1.20.1
IPv4 DNS Servers: 10.1.20.115, 10.1.20.120
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: Yes




Additional info / update:  I have migrated the virtual server in question to a different host server.  Since that migration, the connectivity issue has not reoccurred.  I'm still monitoring it to verify if the issue may be something with the original host server -- but I cannot duplicate with any other servers running on that particular host.   (good thing I'm already bald!)
0
HalldorGCommented:
And vlan not missing on switch between the hosts?
0
brett_apfcAuthor Commented:
Since migrating the server from one host to another the issue has not be reproduced.

Interestingly enough, the two host servers are members of a pool, which means all settings and network are identical.  Not sure exactly what happened, or why, but things are currently working.

I appreciate the suggestions and help from HalldorG.
0
brett_apfcAuthor Commented:
problem could not be reproduced.  Thanks for the suggestions -- help is always appreciated.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.