Unable to browse server by hostname

Good morning Experts,

I have one server running Windows Server 2008 R2 that is unable to connect to another server responsible for file and print sharing. The server running this is running server 2012. I am unable to browse via hostname to the server but can browse by FQDN as well as IP address. I have verified when pinging the server by hostname it is correctly resolving the IP address. I have tried disabling the windows firewall and 3rd party antivirus on the 2012 file server but am still seeing the same results. I have researched the issue but am having a hard time turning up any possible solutions. Any suggestions would be much appreciated!
PCNS_TechAsked:
Who is Participating?
 
PCNS_TechAuthor Commented:
I actually just got it. Since the workstation service is responsible for browsing I restarted it and voila I can now browse it. Thank you all for your suggestions!
0
 
Kent FichtnerInformation Technology Systems SupervisorCommented:
I would try flushing the DNS on the computer.  Have you also tried rebooting?  Do any other computers have this same issue?
0
 
PCNS_TechAuthor Commented:
I have flushed and registered DNS and the issue persisted. I have been hesitant to reboot as the server is running our TimeMatters database but am thinking I am going to have to give it a try. I have tried on another Server 2008 R2 box and 2012 box but none of them see these issues.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Steven CarnahanNetwork ManagerCommented:
I know it may sound odd but check the time on the server against the time on the network.
0
 
PCNS_TechAuthor Commented:
They are both properly syncing with the domain controller.
0
 
Santosh GuptaCommented:
Please try to as shown below.

LAN
0
 
Steven CarnahanNetwork ManagerCommented:
That was the next step I was going to recommend.  If you are not using WINS/NetBIOS (most people don't now) then appending the suffix this way should work.
0
 
PCNS_TechAuthor Commented:
I have never done that before. I am assuming this is on the server experiencing the issue so it will make it use the FQDN for the connection. I am hesitant to put that in without more information. Will that append to all DNS queries?
0
 
PCNS_TechAuthor Commented:
I added it just to see if it alleviated the issue but still no dice. Even after enabling it to append the DNS suffixes and adding the local domain I am still getting the windows cannot access servername.
0
 
Santosh GuptaCommented:
it is just to add suffix to your host name.

for example... if you will ping or access by hostname it will add suffix.

like, requested host name SERVER1 then it will add suffix and change to SERVER1.ABC.COM

MS reference: http://technet.microsoft.com/en-us/library/cc959611.aspx
0
 
Steven CarnahanNetwork ManagerCommented:
Try changing it to the first option:  Append primary connection... and the sub option: Append parent suffix... should also be checked. Then look at the WINS tab and under the Netbios section the Default option should be selected.
0
 
PCNS_TechAuthor Commented:
I have changed it back to the first option to append primary connection specific DNS suffixes and enabled the sub options. I have confirmed WINS has the default option selected. Same error message when attempting to browse the server.
0
 
Santosh GuptaCommented:
Try this...

Go to C:\Windows\System32\drivers\etc and edit the host file.

and make a new entry. (example)

198.168.1.3                hostname
0
 
PCNS_TechAuthor Commented:
Found the issue whilst continuing troubleshooting
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.