Windows Update breaks XP Client DFS paths?

Discussion in 'File Systems' started by Stephen, Jul 22, 2004.

  1. Stephen

    Stephen Guest

    We've recently noticed that when a user tries to open an executable file
    from a Windows 2003 network share, they get a warning message saying
    "Opening files may harm your computer..." just like you would get when
    opening an executable located on the internet.

    If they open \\dfsroot.edu\dfsnet\share\file.exe they get the warning.
    But, if they open the netbios version of the path
    \\dfsroot\dfsnet\share\file.exe then they don't get the error.

    Noted that if I add the dns dfs path to the local intranet security
    setting in Internet Explorer, the warning messages don't occur anymore. But,
    this is a kludgy workaround, that I don't want to do.

    We have a lot of scripts and files hardcoded to use the dns version of the
    DFS path. Don't want to change this. Have the Windows 2003 DFS/FRS hotfixes
    installed.

    This problem never happened before. Believe that the latest
    round of windows updates is causing this warning in conjunction with DFS.

    Has anyone seen this. Know of a workaround beyond changing everything to use
    the netbios dfs path?
     
    Stephen, Jul 22, 2004
    #1
    1. Advertisements

  2. We're investigating this...I'll be back to you as soon as I know more.
     
    Jill Zoeller [MSFT], Jul 22, 2004
    #2
    1. Advertisements

  3. Stephen

    Stephen Guest

    Thanks, Jill...


     
    Stephen, Jul 22, 2004
    #3
  4. This isn't specific to DFS shares. Anything that you access through
    explorer using FQDN would bring this message up because it puts it into the
    Internet security zone and not the "local intranet" zone.

    303650 Intranet site is identified as an Internet site when you use an FQDN
    or
    http://support.microsoft.com/?id=303650

    --
    Gary Mudgett, MCSE, MCSA
    Windows 2000/2003 Directory Services

    =====================================================
    When responding to posts, please "Reply to Group" via
    your newsreader so that others may learn and benefit
    from your issue.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Gary Mudgett [MSFT], Jul 23, 2004
    #4
  5. Stephen

    Stephen Guest

    So that's it? This behaviour is by design!!

    I can tell you that this did not occur until after the last round of windows
    updates. It still does not occur with Windows 2000 - even with the latest
    security updates.

    This behavior is very undesirable, and I think Microsoft will start seeing
    many DFS support call about this issue. The fact that its inconsisitent with
    Windows 2000 would lead one to believe that this behaviour was not
    intended - and is a bug.

    -Stephen
     
    Stephen, Jul 23, 2004
    #5
    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.