Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 218
  • Last Modified:

Client computers started not being able to connect to Server Shares via server name "HELP!"

I have a client that last Thursday a handful of their computers in the office started giving them errors that they could not connect to the network shares. Upon diagnosing the problem, I noticed that I could map the drives via the IP Address of the server which immediately got me thinking it was a DNS issue. I looked at the server and the Forwarders were pointing to the DNS of the ISP so I removed those entries and unchecked to allow forwarders. I also noticed that the router IP (DHCP server) was entered in the static DNS on the server. I removed that and just left the IP Address of the server in there since it is the DNS server. Upon looking at the Event Viewer of the server, there are numerous Event ID messages. Some are Under SYSTEM LOG: 5774, Under DNS SERVER: 7063, Under File Replication Service: 13552, 13555. I took this client over from a friend that got out of the business and they have been working fine up until last week. One other thing I see in the Event Viewer is under SECURITY LOG there are FAILED AUDITS every once in a while. I have never seen this before. The majority of the systems on the network are Windows 2000. However, there are a few Windows XP Pro and a couple of Windows NT.  Just FYI, I can ping all of the IP addresses but cannot ping computer names anymore. Can someone please help me with this as I am stumped and the client assumes they are down. Thanks!
0
newagetechnology
Asked:
newagetechnology
  • 3
  • 2
1 Solution
 
Amit BhatnagarCommented:
Hi, When you say clients are not able to connect to Shares using name..Are you talking about FQDN or Netbios? e.g.  \\xxxx.domain.com or \\xxxx

Cause it is very different. With FQDN, you would require to concentrate on DNS as you are already doing but with Netbios name, you need to concentrate on WINS and if it is also missing then it finally relies on Broadcast. Now, you mentioned that you fixed the Server by removing the DNS entries for ISP and Router. What about the Clients, Where are they pointing to for DNS? Are you using WINS in your Network?
0
 
newagetechnologyAuthor Commented:
I didn't get a response fast enough for this so I had to call Microsoft and have them connect and fix it. It ended up being that the DHCP client was disbaled on the server. Once it was reenabled and started along with the DNS client/server, and netlogon, I began mapping drives using the server name rather than the IP address. No they are not using WINS. All workstations are pointing to the server as a static DNS IP address. And for some reason all of the clients have NETBEUI installed on them.
0
 
Amit BhatnagarCommented:
Ok. Did Microsoft charge you for this simple fix? $245 is a lot of money..:(...Anyways, Good that it is working now. NETBEUI is not required on your clients unless you have some custom application installed which requires it.
0
Lessons on Wi-Fi & Recommendations on KRACK

Simplicity and security can be a difficult  balance for any business to tackle. Join us on December 6th for a look at your company's biggest security gap. We will also address the most recent attack, "KRACK" and provide recommendations on how to secure your Wi-Fi network today!

 
newagetechnologyAuthor Commented:
Yes, they charged me 259.00 which I passed onto the client. It took them over 3 hours to figure out and fix
0
 
Amit BhatnagarCommented:
'No' objections from my side..:)
0
 
Vee_ModCommented:
Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

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