If the server is not responding to ping even from the IP address or FQDN then make sure that the server 's firewall is configured to allow Responding to incoming ICMP requests
Main Topics
Browse All TopicsHi Experts,
I have two windows 2003 servers, server A & B. They are both configured with DNS. The problem that I have is that I can ping the FQDN of server B from server A, but can't ping the FQDN of server B from A. But the really strange thing is, if you take a look at the attached image of server B which I click on 'Resolve' it does so successfully. BTW keylooop-4d20e4.keylooop.l
Any help or suggestions will be greatly appreciated.
Cheers
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
>> I can ping IP
No firewall issue (at least related to ICMP).
>> Can't ping name
>> [...] successful reply when do a ping -a 192.168.1.10 which returns hostname
Which hostname? The FQDN or the WINS (NetBIOS) name only?
>> can't do nslookup on name
Try again with nslookup -d2 (or in nslookup cli mode, set d2).
If you can see the DNS suffices are tried correctly, and it is the correct DNS server, then there is no DNS record.
If the suffixes are wrong, you will have to check that in your TCP properties.
Hi guys,
Below are the outputs from various commands.
I don't have windows firewall installed. As a matter of fact when I click on 'windows firewall' I get the following message ('windows firewall cannot be run because another program or service is running that might use the network address translation component (Ipnat.sys))' I'm not sure what that means.
Byty,
As regards nslookup, I can only get results from the server itself, not for the server I'm trying to ping.
Guys, I hope I've give enough info to assist me in getting this working.
Oh, I should mention, I have managed once to ping the FQDN of the server but it then suddenly stopped when I pinged it back from the other server - does that help?
C:\Documents and Settings\Administrator>ipco
Windows IP Configuration
Host Name . . . . . . . . . . . . : keyloop-017982a
Primary Dns Suffix . . . . . . . : keyloop.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : keyloop.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7781 Gigabit Server Adapter #2
Physical Address. . . . . . . . . : 00-0B-CD-4E-40-CA
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.252
Default Gateway . . . . . . . . . : 192.168.1.6
DNS Servers . . . . . . . . . . . : 192.168.1.5
192.168.1.10
C:\Documents and Settings\Administrator>ping
Pinging KEYLOOOP-4D20E4 [192.168.1.10] with 32 bytes of data:
Reply from 192.168.1.10: bytes=32 time<1ms TTL=127
Reply from 192.168.1.10: bytes=32 time<1ms TTL=127
Reply from 192.168.1.10: bytes=32 time<1ms TTL=127
Reply from 192.168.1.10: bytes=32 time<1ms TTL=127
Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\Administrator>ping
Ping request could not find host KEYLOOOP-4D20E4. Please check the name and try
again.
C:\Documents and Settings\Administrator>ping
Ping request could not find host keylooop-4d20e4.keylooop.l
e name and try again.
C:\Documents and Settings\Administrator>
Thanks again guys
ipconfig/all displays keyloop.com (2 o in loop with .com) and you're trying communicate with <hostname>.keylooop.local (3 o in looop with .local)
The same thing with the other server's name. the local host is spelled with 2 o in keyloop and you're trying to communicate with servername spelled with 3 o in keylooop.
If this is correct with keyloop.com existing one server and keylooop.local exists on the other server, you nead to configure conditional forwarding to forward the other domain's DNS suffix to the correct server.
DNS server properties -> Forwarders -> New, and add the correct DNS server for the other domain.
You can also create a stub or secondary zone on the local DNS server with the remote server as primary server for the other domain.
You're having two different DNS domains keyloop.com and keylooop.local.
The DNS server isn't aware of the namespace of the DNS zone located on the other server and doesn't know where to forward the unresolved queries. When not using conditional forwarders, the DNS server will try to forward the query to external DNS server (forwarders configured to use ISP's server or using roothint list) for external resolving.
The second domain isn't registered on internet and queries will fail to resolve when not using conditional forwarders or local stub/secondary zone for the remote DNS zone.
Business Accounts
Answer for Membership
by: BytyPosted on 2009-09-27 at 03:06:15ID: 25433374
1) check local host file
2) clear the DNS cache
3) flush the dns cache form the server ipconfig /flushdns
4) check the Network card configuration - the DNS server configuration
5) see if you do not have more records in the DNS zone
6) use nslookup comand linie to see if IP /name is resolved ( enter the IP and afhterwards the name ) see if it is resolved corectly
7) ping only the name not the FQDN.. maybe you see something..