Solved

Ping not resolving local server name properly

Posted on 2015-02-18
9
237 Views
Last Modified: 2015-03-03
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.
0
Comment
Question by:dhlytle
  • 4
  • 3
  • 2
9 Comments
 
LVL 12

Expert Comment

by:Jeff Darling
ID: 40617049
Try using NSLOOKUP.

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

nslookup Server-Name.Domain.com dc1.Domain.com
nslookup Server-Name.Domain.com dc2.Domain.com

Open in new window


This might reveal something.
0
 
LVL 12

Expert Comment

by:Jeff Darling
ID: 40617061
If you need the list of DCs, this VBScript might be helpful.

On Error Resume Next

Const ADS_SCOPE_SUBTREE = 2

Set objRootDSE = GetObject("LDAP://RootDSE")
strConfigurationNC = objRootDSE.Get("configurationNamingContext")

Set objConnection = CreateObject("ADODB.Connection")
Set objCommand =   CreateObject("ADODB.Command")
objConnection.Provider = "ADsDSOObject"
objConnection.Open "Active Directory Provider"
Set objCommand.ActiveConnection = objConnection

objCommand.Properties("Page Size") = 1000
objCommand.Properties("Searchscope") = ADS_SCOPE_SUBTREE 

objCommand.CommandText = _
    "SELECT ADsPath FROM 'LDAP://" & strConfigurationNC & "' WHERE objectClass='nTDSDSA'"  
Set objRecordSet = objCommand.Execute

objRecordSet.MoveFirst
Do Until objRecordSet.EOF
    Set objParent = GetObject(GetObject(objRecordset.Fields("ADsPath")).Parent)
    WScript.Echo objParent.CN
    objRecordSet.MoveNext
Loop

Open in new window

0
 
LVL 12

Expert Comment

by:Jeff Darling
ID: 40617064
also, ipconfig /all will show you some important info.

ipconfig /all |find "DNS Servers"

Open in new window

0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
LVL 79

Expert Comment

by:David Johnson, CD, MVP
ID: 40617157
in your firewall you need to allow icmp echo requests
0
 

Author Comment

by:dhlytle
ID: 40617290
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.
client-nslookup.txt
client-ipconfig.txt
0
 

Accepted Solution

by:
dhlytle earned 0 total points
ID: 40625000
The problem is solved.
By placing the full server name "server_name.domain.name.com" on the router, the problem was fixed.

Pinging server_name alone worked fine.
The client-sever application began working previously.

What got corrupted requiring this fix is still unknown.

Adding the full server name and IP in the hosts file also worked, but would require a fix on each work station.

C:\WINDOWS\system32\drivers\etc\hosts
0
 
LVL 79

Expert Comment

by:David Johnson, CD, MVP
ID: 40625022
here is only one domain controller
DNS server is the Verizon router


A router is not a domain name server. So in other words you don't have a server but 2 workstations, windows 7 and Windows 8 .. This also means that you are not in a domain but in a workgroup or a homegroup.
0
 

Author Comment

by:dhlytle
ID: 40627372
Re: Johnson

We are running a dedicated Windows Server 2008 box.

Until last year DHCP and DNS were controlled by the server.

When we installed a new Verizon router about a year ago, we decided, wisely or otherwise, to transfer these functions to the router.  Everything ran fine until a couple of weeks ago when the problems discussed above began.
0
 

Author Closing Comment

by:dhlytle
ID: 40641410
The responses received did not take me beyond what had been done when the question was submitted.
I received no further responses after submitting the ipconfig and nslookup files requested.

The solution to the problem came from other resources and was not related to suggestions made by the respondents.
It seems certain that something has gone wrong in the DNS process.

If the problem had been different, the suggestions make could have been helpful, but that was not the case.

It was a tough issue.

I appreciate the attempts to help, but "C" is the only alternative that fits.

I pass on the solution, hoping that it will help others.
0

Featured Post

Live: Real-Time Solutions, Start Here

Receive instant 1:1 support from technology experts, using our real-time conversation and whiteboard interface. Your first 5 minutes are always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Downtime reduced, data recovered by utilizing an Experts Exchange Business Account Challenge The United States Marine Corps employs more than 200,000 active-duty Marines with operations in four continents, all requiring complex networking system…
This is the first one of a series of articles I’ll be writing to address technical issues that are always referred to as network problems. The network boundaries have changed, therefore having an understanding of how each piece in the network  puzzl…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question