Make sure netbios over tcp/ip is enabled and the dns client service running
Main Topics
Browse All TopicsGood morning,
I encountered a 'fully qualified host name' type error when installing a service on some local machines in my office. After some digging, I discovered the following:
-When I ping from my workstation, to any of my servers or other workstations (not the problem ones), the ping shows:
"Pinging workstation.domain.int" [IP address here] with 32 bytes of data:"
-When I ping from my workstation, to a problem workstation, the ping shows:
"Pinging workstation" [IP address here] with 32 bytes of data:"
-When I ping from the problem workstation, to the problem workstation, the ping shows:
"Pinging workstation.domain.int" [IP address here] with 32 bytes of data:"
Note that the domain doesn't appear when pinging to the problem workstations.
The pings are fine, and the machines work fine, but the problem workstations don't show the <.domain.int> portion. This is causing my services to fail, as they can't resolve themselves to the fully qualified host name of the workstation in which they are installed.
What's the root cause to this, and how can I solve it? (500 points due to time constraint...please help soon!)
Thanks,
~mtd
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.
Hi Deb,
The 'register this connection's address' was disabled on the problem machine, so I enabled it, then did a release/renew on the IP, as well as flushing and re-registering the DNS cache. I also did the same on another working machine, and let it have its 30 minutes to ensure nothing showed up in the event viewer.
After that, I'm still a no-go with the domain on the ping. Any next steps?
Thanks,
~mtd
Turn off netbios on the problematic computer and test. If the computer does not ping properly then it is not fully joined to the network domain. It may need to have its account reset, or it's account deleted and the computer rejoined to the domain. In any case, ping -a should resolve the FQDN of any IP address as long as it can contact a DC.
Could you ping by name?
If not then check hostname is registered in dns on the server as has already been suggested. Also make sure dns on the server is set to accept dynamic updates (it should be but won't hurt). Also could you post the output of an ipconfig /all from both your server, a working pc and the problem one? Can you confirm you're using dhcp from the server rather than a router?
Deb :))
Business Accounts
Answer for Membership
by: Debsyl99Posted on 2005-06-14 at 09:38:28ID: 14213419
Hi
Some suggestions: In tcp/ip settings, advanced,dns on the problem workstation's nic check the following are enabled:
Append primary and connection specific suffixes, register this connections address in dns
Also check you can ping the hostname of the prob workstation rather than just ip, if you can't check it's registered in dns on the server.
Post back if this doesn't help,
Deb :))