Windows XP clients lose connection to shares on 2008 server

Discussion in 'Windows Networking' started by boe, Jan 2, 2009.

  1. boe

    boe Guest


    We have a single server environment running Exchange 2008. All the clients
    are running XP. They'll login and the login script batch file assigns all
    the drive mappings. They'll work for a week or so and then suddenly no
    one can access their shared drives. They have a few drives mapped to
    different volumes and none of them are accessible. They can still ping the
    server by name or by IP and they get a response. However, they can't even
    manually map a drive to the shares - even the hidden shares and they can't
    get to the sysvol from the clients. It isn't happening at a regular
    frequency - but about 1 to 3 weeks or so it will happen. I can remote
    desktop to the server - no issue when this is happening. There is nothing
    in the event viewer at the time the issue occcurs. If I reboot the server
    everything returns to normal.
    boe, Jan 2, 2009
    1. Advertisements

  2. What server do the clients point to for Primary and Secondary DNS?

    Danny Sanders, Jan 2, 2009
    1. Advertisements

  3. boe

    boe Guest

    The primary DNS is the file server. It has no secondary DNS entry.

    The file server is the AD, DNS, DHCP and WINS server. The workstations
    are still able to browse the web and ping the file server by name when the
    issue occurs. If I renew the IP address of a workstation at the time of
    the issue, they are able to refresh their DHCP address but still not able to
    get to the shares on the server.
    boe, Jan 2, 2009
  4. What does the DNS server point to for Primary and alternate DNS?

    Is there any error in the event viewer of the XP machine when this happens?

    Danny Sanders, Jan 5, 2009
  5. boe

    boe Guest

    The server points to itself. No secondary - I could put in the loopback
    address but it doesn't usually change anything on 2003 servers. The server
    can continue to browse the web and the PCs can at the time - the PCs can
    still ping the server by name at the time of the issue and they can renew
    their IP info at the time. The server has a static IP address.

    No error in the event view on the XP machines - other than eventually it
    can't find the group update ini - which coincides of course with it not
    being able to the sysvol or any other share.
    boe, Jan 7, 2009
  6. Well I'm not sure what is going on but it seems to be a problem with your
    server and not the clients. I would try restarting individual services on
    the server the next time it happens to see if you can at least narrow it
    down to a particular service.

    Danny Sanders, Jan 7, 2009
  7. boe

    boe Guest

    That seems like a good idea - I'm somewhat limited as I'm usually remoting
    in to that office. Strangely I can remote to the server with no issue.
    boe, Jan 7, 2009
  8. boe

    boe Guest

    Thanks - I'm running Symantec MR3 - and still having this issue.
    boe, Jan 23, 2009
  9. boe

    Tony P. Guest

    This is funny... just setup SBS 2008 for a client. Same EXACT issue. I have
    SEP 11.0.4... will be taking off the client and see if it's the problem.
    Tony P., Jan 28, 2009
  10. boe

    Tony P. Guest

    Found this on Symantec's Website:

    Terminal servers run multiple instances of ProtectionUtilSurrogate.exe
    Fix ID: 1185648
    Symptoms: After installing Symantec Endpoint Protection 11.0 to a Terminal
    Server, a copy of ProtectionUtilSurrogate.exe is ran for each user that logs
    Solution: Symantec Endpoint Protection 11.0 now allows for a client to
    disable the extra components from loading in separate sessions.

    Now when you remote desktop into the server it's a terminal session. I
    noticed in my application logs on the SBS 2008 that "protectionutilsurrogate"
    was flagged as a faulting application. When I arrived on-site to look at the
    server the sep client had a yellow exclaimation point and said it was
    malfunctioning or corrupted. These events seem to line up with times that
    I've connected remotely to the server. I've removed the client and will
    report on what happens now.
    Tony P., Jan 28, 2009
  11. boe

    boe Guest

    When the issue occurs for me, no one is using TS as I'm the only one with TS
    access to my 2008 server. I can however TS in while no one is able to
    access shares from their workstation.
    boe, Jan 29, 2009
  12. boe

    Tony P. Guest

    Which, when you do, is most likely loading another instance of that
    executable. I've removed the sep client from the server and have had no
    issues yet :) I also noticed that the sep client on the server was screwing
    up group policy deployment to PC's too. I was also getting "could not
    reconnect all network drives" upon login's and that has also disappeared
    since removing the sep client on the server. There's def. something hookie
    with the sep client on server 2008 regardless of which Maintenance release
    you have.
    Tony P., Jan 29, 2009
  13. boe

    Mike S Guest

    Hi, we had the same problem too on Storage Server 2008- running double Take and SEP- turned out to be a SEP problem- both SEP and Double take have replicated this they say (in their test environment) and in our case a patch is being released Oct 2010 to resolve this
    Mike S, Oct 28, 2010
  14. boe

    joj bell

    Dec 11, 2010
    Likes Received:
    If you've enabled the Client service for Netware and there's a Netware server detected on the network, the system will pause for you to login. If you don't want access to Netware servers, just uncheck that box in your local area connection properties.
    joj bell, Dec 13, 2010
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.