• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1487
  • Last Modified:

Can access a machine by IP only not by DNS name

I have one machine that can access a network share by the IP only but not by the DNS name.  So for example if I type in \\ everything works great.  But if I type in \\COMPUTERNAME it will give me an error and won't find the share.  Now this sounds like a DNS problem so I typed in ping COMPUTERNAME in the command prompt and it works fine.  

I need to be able to access the computer by DNS name because I have a program that will only work if it can access it that way. PLEASE HELP!

There used to be some extra configurations in the HOST file that mapped COMPUTERNAME to the wrong IP address but I have since changed that and restarted the computer multiple times.  Even if I map the COMPUTERNAME to the correct IP address it still won't work.  

Also, there is a program that is installed on this computer called IELock that I can't uninstall.  I am not sure if it is causing any problems or not, it could by spyware.  

Lastly, this is the only computer that is giving me problems.  I probably have 30 other computers that can access this share fine.  
1 Solution
Try the following

Click Start, then RUN

type CMD, and then click OK

Type IPCONFIG /FLUSHDNS, then press enter
Type nbtstat -R, then press enter
Please clarify:
1. Does you network use domain or workgroup?
2. Can you see that computer in the entire network under domain or workgroup?
Hi sevenpeaks,
yes you are correct first place to check is DNS,
However it sounds like it is netbios / WINS problem.
First I would see if you can access it via the FQDN (is it in a domain?)
then check to make sure WINS and netbios are correct in the TCP/IP settings

Good luck and let me know what you find
sevenpeaksAuthor Commented:
Wow, thanks for all the comments are such short notice. I did an ipconfig/flushdns and it seemed to have fixed the problem.  Becuase I can now acccess the share just fine.  
Thanks for all of your help.  

By the way the nbtstat command game me an error about not having a the correct drivers or something of that sort, but atleast the ipconfig/flushdns solved the problem.
The nbtstat command would have gave you an error if you do not have NetBIOS over TCPIP network driver installed.  I am glad you have it working.
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.

Join & Write a Comment

Featured Post

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now