Ping not resolving local server name properly

Windows 8 Server, HP Windows 7 workstation, TCP/IP connectivity

Starting a few days ago we were having some problems with a client-server application, and while running tests, we notices that when we tried to ping the server from any of several Work Stations, we got the following:------------------------------------------------------------------------------------------------------------
Pinging Server-Name.Domain.com [92.242.140.21] with 32 bytes of data:Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 92.242.140.21:Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-------------------------------------------------------------------------------------------------------------
Yes, the "server-name.domain.com" is not our real server identity, but the IP address is what (I'm guessing) some confused DNS process is finding with our actual description. We did not put an ip address in the ping command.

When we ping the server IP (192.168.1.10) we get totally normal results.

We have no problems reaching general shared data files on the server via typical MS Office applications.

Any suggestions for further analysis or a resolution?

Many Thanks.



Try using NSLOOKUP.

When you do NSLOOKUP, try with each of the DNS servers at your location.



Try using NSLOOKUP.

When you do NSLOOKUP, try with each of the DNS servers at your location.



If you need the list of DCs, this VBScript might be helpful.



also, ipconfig /all will show you some important info.



in your firewall you need to allow icmp echo requests



Thanks for your suggestions ...

This is a very small/simple network.
There is only one domain controller
DNS server is the Verizon router
the IP address shown in the router are:71.242.0.12
71.250.0.12
Which are verizon sites.
I have wondered if I choose other "reliable" sites, it that might help or tell me something.
But then we only have this single problem (that we know of at this time...)

See attached files.

Share this

Related Posts

There was an error in this gadget