XP SP3 Breaks DFS?

Discussion in 'File Systems' started by John Hornbuckle, Jun 16, 2008.

  1. Some XP and Vista update appears to be causing problems with DFS, but I can't
    figure out exactly what's going on.

    Quick background... At each school, I have a server with a shared directory.
    I use DFS to make these accessible to everyone under an "F:" drive, and every
    user has F: mapped to \\mydomain\dfs. That way users at school1 find their
    stuff under f:\school1, users at school2 find it under f:\school2, and so on.

    Some time back--I don't recall exactly when--I stopped being able to access
    one of my school's stuff from my Vista machine via the F: drive. Whenever I
    go to f:\school1 I get this dialog box:

    "f:\school1 is not accessible. Element not found."

    I have no problem directly accessing the share (i.e., going to
    \\school1server\shareddirectory), but I can't get to it via DFS. Neither
    through the F: drive nor through \\mydomain\dfs\school1.

    On this Vista machine I'm running an XP virtual machine. Interestingly, from
    that virtual machine I've had no problems accessing f:\school1.

    Until now. Now from the XP virtual machine when I go to f:\school1, I get:

    "f:\school1 is not accessible. Configuration information could not be read
    from the domain controller, either because the machine is unavailable, or
    access has been denied."

    And now I'm starting to see computers at that school have the same problem
    accessing their stuff via DFS. In doing some testing on the XP machines, it
    appears that the problem begins once SP3 is installed. I'm not sure which
    Vista update causes the problem, though; I haven't been able to test at that
    level yet.

    From within the DFS utility, all looks good. School1's share shows up as
    being online in the DFS management utility. Only the DFS share at
    School1--which is, as far as I can tell, configured exactly the same as all
    of my other schools--is exhibiting this problem. And only after SP3 is
    installed on the workstations accessing it.

    I have no clue where to go from here. Any suggestions?
     
    John Hornbuckle, Jun 16, 2008
    #1
    1. Advertisements

  2. John Hornbuckle

    Tony Yenshaw Guest

    Sorry, I don't have a fix yet, but my company is having the same issue, but it's only with one particular share, at the moment. We are actively working on a fix and if we do we'll let you know. I'm going to reboot the domain controller where this share resides tonight. We have many DC's scattered all over the world, each holding a different DFS share for that office.

    Thanks,


    Tony
     
    Tony Yenshaw, Jun 19, 2008
    #2
    1. Advertisements

  3. John Hornbuckle

    Tony Yenshaw Guest

    John,

    Hello, we rebooted the domain controller that hosted the share that was giving us the DFS issue and then rebooted the XP -SP3 machines and they can now get to the share. We're not sure what the specific issue was. I hope this helps.


    Tony
     
    Tony Yenshaw, Jun 20, 2008
    #3
  4. Thanks for the tip, Tony. I just gave this a shot, and unfortunately it
    didn't fix it for me.
     
    John Hornbuckle, Jun 20, 2008
    #4
  5. John Hornbuckle

    esentrik Guest

    check the dns registration of the client machines
     
    esentrik, Jul 1, 2008
    #5
  6. I can't imagine why DNS registration would get messed up with SP3 being
    installed, and if so why the only symptom would be that one DFS share out of
    a half-dozen would be inaccessible.

    I've opened a case with MS, and they're working on it now.
     
    John Hornbuckle, Jul 2, 2008
    #6
  7. John Hornbuckle

    bulent Guest

    John,

    We are experiencing the same issue. Were you able to fix it?

    Thanks.
     
    bulent, Aug 11, 2008
    #7
  8. Yes. It turns out that there was an error in our DFS info in AD. Pre-SP3,
    this error was ignored. But SP3 introduced some new error-checking that
    caused the problem--which had always been there, or at least had been there
    for a long time--to show symptoms.

    We were able to fix the error by deleting and then re-creating the DFS link.

    A simple solution, but it took hours working with Microsoft to come up with
    it.
     
    John Hornbuckle, Aug 11, 2008
    #8
  9. John Hornbuckle

    bulent Guest

    Thank you very much...

     
    bulent, Aug 11, 2008
    #9
    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.