Ping by Name issue
When I ping some servers by name it times out but by IP address I receive replies.
If I ping the server such as: Ping Servername
it times out
If I ping such as: Ping Servername.Comapnyname.com
I receive replies also
If I ping such as: Ping IPaddress I also receive replies.
Do you have any idea why do I need to add the Company.com after the server name in order to receive replies??
If I ping the server such as: Ping Servername
it times out
If I ping such as: Ping Servername.Comapnyname.com
I receive replies also
If I ping such as: Ping IPaddress I also receive replies.
Do you have any idea why do I need to add the Company.com after the server name in order to receive replies??
Please take a look at http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cncf_imp_absq.mspx?mfr=true
-showing how names can be resolved
-showing how names can be resolved
Both Servername and Servername.companyname.com
Chris
Just put your comany.com info in the DNS suffix of your TCPIP.
I hope this helps !
I hope this helps !
ASKER
I am doing the Pings from the same machine, but why only some servers they reply for the ping when I use Ping Servername.Companyname and not the other servers???
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
the amazing thing is:
the servers that I can't ping by name without adding the suffix company.com, I can ping them by name from other workstations. So I can see where the problem comes from
the servers that I can't ping by name without adding the suffix company.com, I can ping them by name from other workstations. So I can see where the problem comes from
Try:
ping -a hostname
The -a switch forces ping to resolve the hostname to the proper IP address.
ping -a hostname
The -a switch forces ping to resolve the hostname to the proper IP address.
oops... I guess that's probably not really what you need. Proper usage of the -a switch is:
ping -a ipaddress
then it displays the hostname...sorry :(
Assuming you're just looking to test connectivity to a host using hostname, have you tried tracert? It may give you more info than you need, but it could be worth a try.
tracert hostname
ping -a ipaddress
then it displays the hostname...sorry :(
Assuming you're just looking to test connectivity to a host using hostname, have you tried tracert? It may give you more info than you need, but it could be worth a try.
tracert hostname
As I mentioned, the other machines may have the proper DNS suffix. Please compare all the TCPIP settings of a working and non-working machine.
Also compare
ipconfig /all from a DOS box on each
I hope this helps !
Also compare
ipconfig /all from a DOS box on each
I hope this helps !
ASKER
guardsman85:
ping -a ipaddress
this resoloves the IP to hosname
SysExpert:
If I understand you , do you want me to go to the machines that I can't ping by name and check TCP/IP settings????
By the way there was nothing change and this problem just came up after they installed a new DNS server in the network. This is the one thing that I am thinking that the problem came from.
ping -a ipaddress
this resoloves the IP to hosname
SysExpert:
If I understand you , do you want me to go to the machines that I can't ping by name and check TCP/IP settings????
By the way there was nothing change and this problem just came up after they installed a new DNS server in the network. This is the one thing that I am thinking that the problem came from.
ASKER
This might help you understand the source of the issue.
from some machines that I can't ping some servers by name , I created records in host file and solved the problem.
But I still want to understand what was missing in the DNS servers that prevent some machines to ping some servers by name but able to ping other servers by name.
from some machines that I can't ping some servers by name , I created records in host file and solved the problem.
But I still want to understand what was missing in the DNS servers that prevent some machines to ping some servers by name but able to ping other servers by name.
As you mentioned. it could well be the the new DNS server is not set up properly, or that the old one is still running and there are conflicts.
ASKER
if it was the new DNS server that is faulty, why would some machines be able to resolve the name and some not.???????
If some machines are accessing the old, and they are working, and some are accesing the new, and NOT working, or vice versa.
Have you run all the diagnostics from the Server resource kit for DNS, AD and the rest ?
Have you run all the diagnostics from the Server resource kit for DNS, AD and the rest ?
On above path open Hosts file in Notepad. Map IP address against the server name like
10.0.0.1 SERVER
or
10.0.0.1 server.training.com