Client not doing ping by name to server
one desktop system is doing ping to server by ip address but not doing by server name then how to sort out this bug from desktop sytem?
Software/Hardware used:
Software/Hardware used:
ASKED:
February 7, 2011 5:13 PM
UPDATED:
February 8, 2011 5:22 PM
Answer Wiki:
It means the desktop system is not resolving the hostname. It is done by DNS, Domain or Wins server (or samba server).
We need more information about your scenario. Tell us if you are talking about internet hostname, or a local network hotnames resolving issue.
Regards.
To see all answers submitted to the Answer Wiki: View Answer History.
Can you let me know resolution of both scenarios????
Thanks for ur prompt response.
open up command prompt, type the line below
ipconfig /all
make sure the dns servers are correct, if they are, type the line below in cmd
nslookup [servername]
It should show a connection to your dns server then to the server you requested the connection to. If it shows a the first hop to your dns server and doesn’t go any further you should type the following into command prompt.
ipconfig /flushdns
So you know and don’t just follow me blindly, the ipconfig /all will show you the NIC settings including DHCP, DNS, IPs. nslookup will give you name server information, external dns queries should bounce from the machine to your name server to an external name server such as 4.2.2.2 (open dns) and flushdns will clear the dns on the worksation which may help get rid of an old/bad entry. All of the steps should be done on the workstation you are having issues with.
@ KFaganJr is this can be sort out by the lmhost file if not by your given steps. coz someone given me hint about lmhost
I know that lmhost file is useful in WINS to resolve netbios name to ip address.
if anyone have idea about this then let me know
http://support.microsoft.com/kb/314108
lmhost will give you the ability to manually make an entry into the workstation to associate the IP address with the DNS record. The issue with this is that if something changes later on such as the IP of the server, or another server takes over that IP the workstation will have issues finding it again.
Have you rebooted? Don’t like asking those questions on here, but it is a desktop so I’m going to ask. If you haven’t, I’d recommend doing so before you start making manual changes you don’t know much about to the system. That could very well clear up a dns issue
@ KFaganJr
Thanks buddy your point is good on lmhost entry coz we indeed need to infuse ip address again if IP address of server will change.
Actually, this question was asked by one of the employer to me and when i didn’t give any reply to this question then they had given hint to me that you can do this by make any entry in lmhost file.
“lmhost will give you the ability to manually make an entry into the workstation to associate the IP address with the DNS record”
Actually, it associates ip addresses to host names, not to DNS records.
If a DNS record existed for the host name and the DNS server were accesible, then the lmhost file would not be used as it is the last resort when resolving host names.
OTOH, this question looks like a homework assignment. Depending on the environment the lmhost file could not need to be used, but no details at all were provided about the environment, so it looks like a mere theoretical question.
Carlosdl is right, I misspoke about the lmhosts file in a quick attempt to answer you while promoting troubleshooting the issue before making the change
@ Carlosdl
you are right as i mentioned as well in the previous post that this question was asked by interviewer.
thankx but dont mind that i didn’t understand this concept clearly specially about lmhost