Tech Off Thread

14 posts

Forum Read Only

This forum has been made read only by the site admins. No new threads or comments can be added.

Windows Server 2008 R2 - Shares intermittantly inaccessible

Back to Forum: Tech Off
  • User profile image
    W3bbo

    I've noticed this ever since I upgraded my LAN's domain controller to Windows Server 2008 R2.

    The server has an SMB share called "Share" which is the root of an internal hard-drive (FWIW, E:\).

    I subscribe to one of the child-folders of Share as an Offline Folder on my desktop on the same LAN. Every so-often, about once every half-hour, I get a notification that the server is now unavailable and that I'm now Working Offline. When I try to access the share directly via Explorer only one or two folders are listed in addition to my Offline folder, and when I try to access a folder I know exists I get the Not Found error.

    A few minutes later it comes back online and I can access the share fine.

    Sometimes it only affects the NetBIOS name, so \\server\share fails, but \\server.domain.local\share works fine. But more-often than not I'm finding they both seem to fail at the same time.

    I've noticed this on both my XPx64 desktop and my Windows 7 laptop.

  • User profile image
    AndyC

    Are the LAN clients using the domain controller for all their DNS requests?

  • User profile image
    W3bbo

    , AndyC wrote

    Are the LAN clients using the domain controller for all their DNS requests?

     

    All the computers are configured using DHCP. The scope options set 172.16.1.2 and 172.16.1.1 as DNS Servers (in that order). 172.16.1.2 is the Domain Controller, 172.16.1.1 is the ISP-issued Netgear router with a built-in DNS server, it's listed for use as fallback so clients can still access the Internet when the domain controller is down. Do you reckon that might be the problem?

    FWIW I also have WINS set up on the network. The DHCP scope also defines 172.16.1.2 as the WINS/NBNS server.

    Nothing relevant is in any of the Event Logs.

    EDIT: This is interesting. In WINS, under Active Registrations, "SERVER" is down only for "File Server" and its IP address is 169.254.249.105, even though when I run ipconfig /all on the server all IP addresses are listed and valid (i.e. not in 169.254).

  • User profile image
    ScottWelker

    Hey W3.. This is likely a worthless shot in the dark but..

    I experienced a similar 2008 Server "Share Flakieness" until I resolved a Windows Update issue that prevented me from applying any updates. Once past that, with all updates, applied the issue went away.

    Best of luck! Please keep us posted.

     

  • User profile image
    W3bbo

    @ScottWelker:

    I've done some googling and found some error messages associated with the problem. I'm posting them here so anyone-else googling for the same problem will find this thread.

    For example, the Offline Files window shows "Unavailable for reconnect".

    I searched for that term and found a few threads where people discuss it, but I don't have the time right now to read them. I'll post again when I know.

  • User profile image
    W3bbo

    I ran Sysinternal's "ShareEnum" program from my XPx64 computer to investigate, interesting:

    The top half of the image shows what it showed when my computer reported the server offline. The bottom half shows what it says when it magically reconnected a few moments later:

    As you can see, the other servers (Waiter, Vaioz, and Blackbox) work perfectly fine, but \\SERVER (which is also the domain controller) has problems.

    Generic Forum Image

  • User profile image
    AndyC

    I'd be highly suspicious of the DNS config and try getting rid of the non-DC entry. Problems like this in AD environments almost always end up being DNS resolution.

  • User profile image
    W3bbo

    , AndyC wrote

    I'd be highly suspicious of the DNS config and try getting rid of the non-DC entry. Problems like this in AD environments almost always end up being DNS resolution.

    I can't see anything immediately wrong in my DNS zone:

    Generic Forum Image

  • User profile image
    W3bbo

    This is interesting. In WINS, under Active Registrations, "SERVER" is down only for "File Server" and its IP address is 169.254.249.105, even though when I run ipconfig /all on the server all IP addresses are listed and valid (i.e. not in 169.254).

    Last night I disabled the WINS service on SERVER. I haven't yet encountered a disconnection yet.

    So I guess that was the cause. I always used to install the WINS server component because I thought it would stop Windows Explorer from freezing when you open My Network Places, but it seems to work fine without it.

    Is there any need for the WINS server anymore?

  • User profile image
    W3bbo

    @W3bbo:I spoke too soon. Just now I received another "Unavailable for reconnect" message.

    Rats.

  • User profile image
    AndyC

    , W3bbo wrote

    *snip*

    I can't see anything immediately wrong in my DNS zone

    Yeah, but that's what your DC thinks DNS looks like. It won't be what your router thinks and it'll be queries going off that way that cause the failure.

    , W3bbo wrote

    *snip*

    Is there any need for the WINS server anymore?

    99.9% of the time, no. In the rare circumstances you might need it, you'll already know.

     

  • User profile image
    W3bbo

    Yeah, but that's what your DC thinks DNS looks like. It won't be what your router thinks and it'll be queries going off that way that cause the failure.


    WINS has been disabled for a while now, and I agree that something's up with DNS, but I can't imagine what.

    Here's what DCDiag on my desktop says:

    D:\Users\David>dcdiag /s:server
    
    Domain Controller Diagnosis
    
    Performing initial setup:
       Done gathering initial info.
    
    Doing initial required tests
    
       Testing server: Default-First-Site-Name\SERVER
          Starting test: Connectivity
             ......................... SERVER passed test Connectivity
    
    Doing primary tests
    
       Testing server: Default-First-Site-Name\SERVER
          Starting test: Replications
             ......................... SERVER passed test Replications
          Starting test: NCSecDesc
             ......................... SERVER passed test NCSecDesc
          Starting test: NetLogons
             [SERVER] An net use or LsaPolicy operation failed with error 53, The network path was not found..
             ......................... SERVER failed test NetLogons
          Starting test: Advertising
             Fatal Error:DsGetDcName (SERVER) call failed, error 1722
             The Locator could not find the server.
             ......................... SERVER failed test Advertising
          Starting test: KnowsOfRoleHolders
             ......................... SERVER passed test KnowsOfRoleHolders
          Starting test: RidManager
             ......................... SERVER passed test RidManager
          Starting test: MachineAccount
             Could not open pipe with [SERVER]:failed with 53: The network path was not found.
             Could not get NetBIOSDomainName
             Failed can not test for HOST SPN
             Failed can not test for HOST SPN
             * Missing SPN :(null)
             * Missing SPN :(null)
             ......................... SERVER failed test MachineAccount
          Starting test: Services
             Could not open Remote ipc to [SERVER]:failed with 53: The network path was not found.
             ......................... SERVER failed test Services
          Starting test: ObjectsReplicated
             ......................... SERVER passed test ObjectsReplicated
          Starting test: frssysvol
             [SERVER] An net use or LsaPolicy operation failed with error 53, The network path was not found..
             ......................... SERVER failed test frssysvol
          Starting test: frsevent
             ......................... SERVER failed test frsevent
          Starting test: kccevent
             Failed to enumerate event log records, error The network path was not found.
             ......................... SERVER failed test kccevent
          Starting test: systemlog
             Failed to enumerate event log records, error The network path was not found.
             ......................... SERVER failed test systemlog
          Starting test: VerifyReferences
             ......................... SERVER passed test VerifyReferences
    
       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
    
       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
    
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
    
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
    
       Running partition tests on : domain
          Starting test: CrossRefValidation
             ......................... domain passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... domain passed test CheckSDRefDom
    
       Running enterprise tests on : domain.local
          Starting test: Intersite
             ......................... domain.local passed test Intersite
          Starting test: FsmoCheck
             Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1722
             A Global Catalog Server could not be located - All GC's are down.
             Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1722
             A Primary Domain Controller could not be located.
             The server holding the PDC role is down.
             Warning: DcGetDcName(TIME_SERVER) call failed, error 1722
             A Time Server could not be located.
             The server holding the PDC role is down.
             Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1722
             A Good Time Server could not be located.
             Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1722
             A KDC could not be located - All the KDCs are down.
             ......................... domain.local failed test FsmoCheck
    
    D:\Users\David>


    But when I run it on the server at the exact same time:

    C:\Users\Administrator.domain>dcdiag /s:server
    
    Directory Server Diagnosis
    
    Performing initial setup:
       * Identified AD Forest.
       Done gathering initial info.
    
    Doing initial required tests
    
       Testing server: Default-First-Site-Name\SERVER
          Starting test: Connectivity
             ......................... SERVER passed test Connectivity
    
    Doing primary tests
    
       Testing server: Default-First-Site-Name\SERVER
          Starting test: Advertising
             ......................... SERVER passed test Advertising
          Starting test: FrsEvent
             ......................... SERVER passed test FrsEvent
          Starting test: DFSREvent
             ......................... SERVER passed test DFSREvent
          Starting test: SysVolCheck
             ......................... SERVER passed test SysVolCheck
          Starting test: KccEvent
             ......................... SERVER passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... SERVER passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... SERVER passed test MachineAccount
          Starting test: NCSecDesc
             ......................... SERVER passed test NCSecDesc
          Starting test: NetLogons
             ......................... SERVER passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... SERVER passed test ObjectsReplicated
          Starting test: Replications
             ......................... SERVER passed test Replications
          Starting test: RidManager
             ......................... SERVER passed test RidManager
          Starting test: Services
             ......................... SERVER passed test Services
          Starting test: SystemLog
             ......................... SERVER passed test SystemLog
          Starting test: VerifyReferences
             ......................... SERVER passed test VerifyReferences
    
    
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
    
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
    
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
    
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
    
       Running partition tests on : domain
          Starting test: CheckSDRefDom
             ......................... domain passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... domain passed test CrossRefValidation
    
       Running enterprise tests on : domain.local
          Starting test: LocatorCheck
             ......................... domain.local passed test LocatorCheck
          Starting test: Intersite
             ......................... domain.local passed test Intersite
    
    C:\Users\Administrator.domain>


    Do you suppose this is due to my dual-DNS config on the clients?

  • User profile image
    W3bbo

    I removed the two DNS servers from the DHCP server options and renewed the IP address on my desktop so it only uses 172.16.1.2 as its DNS server.

    ...3 minutes later, I got the Balloon of Evil again, and I can't connect to Services management on the server either:

    ---------------------------
    Services
    ---------------------------
    Unable to open service control manager database on SERVER.



    Error 1707: The network address is invalid.


    ---------------------------
    OK  
    ---------------------------

     

    Argh.

  • User profile image
    W3bbo

    Earlier this week I noticed that my desktop computer still had "WINS Server: 172.16.1.2" in ipconfig even though it wasn't specified by the DHCP server.

    I completely cleared the IP config and renewed, and I'm glad that WINS doesn't turn up at all now. Since then I haven't had any problems with my network.

    ...until yesterday. Argh!

    (Oh, and this happens regardless of whether or not my modem is connected to the network or not).

    I did some more googling and found one possible cure is to run this command on the server:

    net config server /autodisconnect:-1

    Before I set that the timeout was set to 15 minutes, which is roughly how often I was getting the messages. Let's see how long this works for.

     

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.