Can't access network stations by its names anymore, only IP.


On our LAN of about 30 workstations, we lost the ability to access the server (Shared Folders) with simply typing in \\SERVERNAME in the Explorer. I can still access the server by its IP address, but all of the network settings (backups on workstations, printers, scanners) are configured to access it by its server name. The only thing that was changed is our switch for small part of the network (upgraded to Netgear Gigabit switch). The switch connects 10 workstations to the main Gigabit switch. I don't see how it can be Switch's fault - it seems to operate well.

Not sure, but Windows2003 might of downloaded some updates recently and restarted the server on its own.

Observation: Some workstations are still able to access the server by it's name: \\servername , these are desktops and some laptops that weren't removed from the office, the problem seems to only occur with laptops that are taken home and disconnected from network.

Here's our set-up:
We have 1 Windows 2003R2 server that has SharedFolders on it, workgroup, and also has Kerio WinRoute Firewall installed - the KWF software acts as a Firewall/DHCP/VPN server.

Thank You.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TG TranIT guyCommented:
Check DNS and/or WINS settings

Kaptain1Author Commented:
well, for DNS i'm using OpenDNS servers >, but i assume that's for outside the LAN. How do i check the DNS/WINS for inside the LAN? Please clarify.

Thank You.
TG TranIT guyCommented:
Do you have internal DNS and/or WINS servers?

Open Command line (start - run - cmd) and type "ipconfig/all"

The problem is when a PC in your LAN tries to resolve computer name to IP address, if you have OpenDNS configured on that PC, it will go to OpenDNS to ask for the IP.  Of course OpenDNS will not have the IP for PC located in your LAN.  Therefore, name resolution would fail
What were the top attacks of Q1 2018?

The Threat Lab team analyzes data from WatchGuard’s Firebox Feed, internal and partner threat intelligence, and a research honeynet, to provide insightful analysis about the top threats on the Internet. Check out our Q1 2018 report for smart, practical security advice today!

I would like to help. But, so far the advice provided has been real good. So, for now I will set on the sideline and monitor this question, if you don't mind.
Kaptain1Author Commented:
I haven't set-up a DNS server for our LAN, however, i assume it was functioning by default since i was able to use server names on LAN (//servername).

Since we're using Kerio WinRoute Firewall software as a Gateway for our LAN, i'll try researching more on their forum on how to troubleshoot or reset its LAN DNS capability.

... unless you guys can give me a hint :). Usually LAN DNS has just been working w/o any problems for me until now, so i don't know what steps can be taken to troubleshoot this problem.

Thank You.
TG TranIT guyCommented:
"LAN DNS has just been working w/o any problems" - What LAN DNS are you referring to?  OpenDNS?
In my opinion, you have not encountered name resolution until you now because you relied on NetBIOS (read this KB

One way to test this is to use "ping -a <ip address>"
Just type in an ip address of a valid node on your network, ping will return NetBIOS name
Use "nbtstat -c" - to see the cached NetBIOS names
Use "ipconfig/displaydns"  to see resolved DNS resolutions
Do you see a patten?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
You will have to set up a DNS server on your LAN.

Let me tell you why.

You have probably been using your router for DNS. That's fine and dandy if you have EVERYONE's credentials on each computer. Routers used as DNS servers are OK if you don't have a domain. This is because a 2003 server DNS holds what is called SRV records. SRV records point to the direction of an authentication server, (your domain controller). Your domain controller is the one thing that provides authentication to access shares on the domain computers. A router will not provide SRV records as a DOMAIN DNS server would.

Managing DNS server on your DCs is not only recommended, it is pretty much required.

Kaptain1Author Commented:
I don't use a domain,
I was able to solve the problem by setting up a WINS server pointing to my router, it works now. thanks all!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

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.