Home / server / Questions / 75409
Accepted
Wayne Hartman
Asked: 2009-10-17 16:17:16 +0800 CST

UNC Network Shares Fail

  • 772

I have a Windows Server 2008 R2 installation that is acting as a DC. It has been operational without any problems since late August. All of a sudden, UNC share access experiences an issue where no-one (clients or the DC itself) can access the DC's shares. A reboot of the computer resolves the issue for a minimum time 24-hours, at which time UNC fails again. When this occurs, DNS appears to be fine, routing is fine, I can remote in the server by its FCDN, etc. There are no log entries that really indicate that there is a problem until clients and even the DC itself try to refresh Group Policy, which is accessed via a UNC share.

I realize that details are scant, so if you have any troubleshooting information I can go dig up and post, I would appreciate it.

networking

9 Answers

  1. "Windows Server 2008 network shares may become unresponsive with Symantec Endpoint Protection 11 or Symantec AntiVirus 10.2 client installed and Auto-Protect enabled."

    From here.

    • 2
  2. Best Answer

    Have been conducting my own additional research and found this article:

    Windows 2008 Server Network Connectivity Problem:

    Here was the symptom – Everything would work fine for at least 3 hours, sometimes close to 24 hours. Then everything would start to go screwy. Computers would start to drop off the network like flies. The sysvol share would become inaccessible to anyone on the network (including the server itself.) ... Rebooting the server would make the errors and problems go away for a while, but within a day, the problem would be back. ... This symptom is caused by a flaky network card driver.

    I noticed my drivers were the Microsoft installed versions. I also found that my NIC manufacturer had more specific (and recent) versions of the NIC drivers, so I have loaded those. It has been a few days; so far so good. I'm not calling this one solved, so we'll see what the next few days bring...

    • 1

  3. Any updates applied about the time it started having this trouble?

    • 0

  4. Check that following services are up and running on the server:

    1. netlogon
    2. server
    3. computer browser

    They should be dealing with sharing...

    EDIT:

    Try to check also all dependences to Network Discovery, like:
    * Function Discovery Resource Publication
    * SSDP Discovery
    * UPnP Device Host

    • 0

  5. Did you adjust the server clocks for Daylight Savings? You might be off by an hour.

    • 0

  6. Please define "no one can access". What is the exact error message/problem....permission denied, shares not visible, server not found, etc?

    In your example \\domain.local\sysvol being inaccessible, is DFS in use?

    Have you done the previously suggested test of \\127.0.0.1\Share from the server itself?

    • 0

  7. This might seem obscure since you can do pretty much everything except SMBFS on the server, but - have you tried moving the server to a different switch port? A confused switch ARP stack can create many weird problems. I've had similar problems before (especially when doing trunking), and my only solution was to hard-reset our switches.

    • 0

  8. The Server service allows shares to be accessible. So you indicated that the server service is up and running and that client and the DC itself cannot connact to the shares.

    Do you have a firewall configured? if the clients cannot connect to the shares you could try portqryv2 on the server itself to confirm that the ip ports are open, these ports are 137,138,139, and 445. Is NBT enabled?

    Is the DC internet facing?

    Also try turning up the logging to find out if there are any errors you're not specifically picking up. It could be that you have a virus which may be causeing a buffer overflow on the TCP stack.

    • 0

  9. What does the output of "net share" say when you run it from the cmd.exe?

    Are all the shares which should be there actually appearing?

    • 0