Link to home
Start Free TrialLog in
Avatar of PatrickDoman
PatrickDomanFlag for United States of America

asked on

Computers on LAN can't ping server via IP or Name

We have a server on our network which hosts a line of business application. It is primarily web based.
- The application operates over HTTPS

We recently moved the application to a new server, formatted and reloaded the server and ran all applicable updates.

When we reboot our computers, we often find that we can't ping the application server by name or IP.

That, is, until we ping our computer from the server. After we have pinged our own IP from the server, communication starts to work.

Seems a bit phishy.

Anyone seen this?
Avatar of SStory
SStory
Flag of United States of America image

Well a firewall could stop pings even all pings but those already established on the inbound side.

Does the app server have a configuration that requires specifying which machine addresses are allowed to access it or ping it?
Avatar of PatrickDoman

ASKER

Our firewall does nothing to prohibit internal communications system to system.
The server's windows firewall is disabled.

The NIC is a Intel R Pro 1000 PT Dual Port Server Adapter
The driver is 9.16.10.0 from 6/19/2013

Teaming is disabled
no VLAN's configured


In the power management area of the NIC, Wake on Directed Packet is the only option selected.

I turned that off. Not sure why we  have that selected.
ASKER CERTIFIED SOLUTION
Avatar of Craig Beck
Craig Beck
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If you have AD with DNS, open an elevated command prompt and run "ipconfig /registerdns"

Do this on the problematic server and on the client computer.

Wait 15 min and ping the server after rebooting your PC.
I agree that it could be some sort of ARP issue, but still sort of strange.
I assume tracert <serverip> doesn't reveal a router on which it dies or is it all on a simple LAN
I will suggest to check the ip on the new machine.  Go on the DNS server and look for duplicated entries for the server name and delete the old one.  Then, I will run ipconfig /flushdns, ipconfig /registerdns on all machines if necessary after the DNS server cleanup.
I have gone in and flushed and registered DNS on all systems, servers specifically.

Again, if I ping my computer from the server at 172.16.250.12 the pings from my computer will work. But if the system is not the system initializing the communication and I just try to ping, the connections timeout.

I have to run a constant ping when I do have it working so the connection won't time out.

Sever Nic is a Intel Server Dual Port Adapter (add-on) latest drivers installed.

Switches are Procurves. No Vlan's configured.
They are also running the latest firmware and have been reset and reconfigured from scratch to see if they were the culprit.

I turned off a setting on the NIC, I think it was power management based. I will get the setting. I haven't had issues connecting to the server in the last couple of days.

This may have fixed it.
Perhaps if you put WireShark on both sides you could tell where the packets are dying. It must get sent and be received obviously. It can die before leaving or before returning, or before getting there. (http://sourceforge.net/projects/wireshark/)