Re: [ActiveDir] OT: Network latency on VBScript-mapped drive letters.
Just curious. Are you sure its not something like AV scanning network
files on access? Generally once scanned they add them to a temp db of
"known good list" to prevent scanning when accessed later. If so, that
would explain slow performance when first accessing the files but
better responses when accessing after manually mapping drives.
Do you think its worth looking at network traces to see if any SMB
errors are occurring?
On 1/23/07, Laura E. Hunter <[EMAIL PROTECTED]> wrote:
So I have a VBScript that I use to map a network drive to a DFS share,
as follows:
strDriveLetter = "S:"
strBaseDrivePath = "\"
Set objNetwork = CreateObject("WScript.Network")
objNetwork.MapNetworkDrive strDriveLetter, strBaseDrivePath
set objNetwork = nothing
When I map the DFS root using a drive letter using this code in a
login script, I get isolated-but-consistent client reports of network
latency when opening or saving a file; Word/Excel/whatever will choke
up for a good 5 or 6 seconds at a time.
If I disconnect the script-mapped drive and access this resource from
the same machine using any other method:
* map the drive using the GUI,
* map the drive from the CLI using 'net use', or
* manually enter the UNC path from the Run line
...all latency goes away. It's not OS-specific as far as I can tell;
the machines currently reporting the latency are a handful of XPSP2
and 2KSP4 machines that don't have much else unique in common.
I've determined that it's not specifically DFS-related, as I've tested
mapping directly to the physical servername instead of the DFS
sharename and produced identical results.
Neither is it relevant that the script is being run as part of a login
script/GPO, as running the script manually from an affected desktop
also produces the same behaviour.
So it's either a VBScript thing, or it's something client-specific
that I haven't isolated on the half-dozen desktops that are
experiencing the issue.
Google has thus far yielded no joy, has anyone run into this before?
--
---
Laura E. Hunter
Microsoft MVP - Windows Server Networking
Author: _Active Directory Cookbook, Second Edition_ (http://tinyurl.com/z7svl)
List info : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ma/default.aspx
List info : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ma/default.aspx
RE: [ActiveDir] OT: Network latency on VBScript-mapped drive letters.
I saw something similar using kixtart-mapped drive letters a few months
ago. The only thing affected seemed to be Office products and IE. The
knowledge base described it as unable to browse the network, but I
certainly saw it as ranging from severe latency to complete inability to
browse the network or file shares.
Cut and paste from an email I sent at the time:
"MS06-015 along with certain HP products can cause some conflicts.
Side-effects include program freezes, an inability to follow a link you
type into Internet Explorer, inability to open or save files in Office
applications, inability to click the + sign while browsing My Documents
or My Pictures."
Also see http://support.microsoft.com/?kbid=918165
Of course this may or may not be the problem, but it is the only thing I
have ever seen like what you are describing.
Hope it helps
Kevin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Laura E. Hunter
Sent: Tuesday, January 23, 2007 12:52 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] OT: Network latency on VBScript-mapped drive
letters.
So I have a VBScript that I use to map a network drive to a DFS share,
as follows:
strDriveLetter = "S:"
strBaseDrivePath = "\"
Set objNetwork = CreateObject("WScript.Network")
objNetwork.MapNetworkDrive strDriveLetter, strBaseDrivePath
set objNetwork = nothing
When I map the DFS root using a drive letter using this code in a
login script, I get isolated-but-consistent client reports of network
latency when opening or saving a file; Word/Excel/whatever will choke
up for a good 5 or 6 seconds at a time.
If I disconnect the script-mapped drive and access this resource from
the same machine using any other method:
* map the drive using the GUI,
* map the drive from the CLI using 'net use', or
* manually enter the UNC path from the Run line
...all latency goes away. It's not OS-specific as far as I can tell;
the machines currently reporting the latency are a handful of XPSP2
and 2KSP4 machines that don't have much else unique in common.
I've determined that it's not specifically DFS-related, as I've tested
mapping directly to the physical servername instead of the DFS
sharename and produced identical results.
Neither is it relevant that the script is being run as part of a login
script/GPO, as running the script manually from an affected desktop
also produces the same behaviour.
So it's either a VBScript thing, or it's something client-specific
that I haven't isolated on the half-dozen desktops that are
experiencing the issue.
Google has thus far yielded no joy, has anyone run into this before?
--
---
Laura E. Hunter
Microsoft MVP - Windows Server Networking
Author: _Active Directory Cookbook, Second Edition_
(http://tinyurl.com/z7svl)
List info : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ma/default.aspx
List info : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ma/default.aspx
[ActiveDir] OT: Network latency on VBScript-mapped drive letters.
So I have a VBScript that I use to map a network drive to a DFS share,
as follows:
strDriveLetter = "S:"
strBaseDrivePath = "\"
Set objNetwork = CreateObject("WScript.Network")
objNetwork.MapNetworkDrive strDriveLetter, strBaseDrivePath
set objNetwork = nothing
When I map the DFS root using a drive letter using this code in a
login script, I get isolated-but-consistent client reports of network
latency when opening or saving a file; Word/Excel/whatever will choke
up for a good 5 or 6 seconds at a time.
If I disconnect the script-mapped drive and access this resource from
the same machine using any other method:
* map the drive using the GUI,
* map the drive from the CLI using 'net use', or
* manually enter the UNC path from the Run line
...all latency goes away. It's not OS-specific as far as I can tell;
the machines currently reporting the latency are a handful of XPSP2
and 2KSP4 machines that don't have much else unique in common.
I've determined that it's not specifically DFS-related, as I've tested
mapping directly to the physical servername instead of the DFS
sharename and produced identical results.
Neither is it relevant that the script is being run as part of a login
script/GPO, as running the script manually from an affected desktop
also produces the same behaviour.
So it's either a VBScript thing, or it's something client-specific
that I haven't isolated on the half-dozen desktops that are
experiencing the issue.
Google has thus far yielded no joy, has anyone run into this before?
--
---
Laura E. Hunter
Microsoft MVP - Windows Server Networking
Author: _Active Directory Cookbook, Second Edition_ (http://tinyurl.com/z7svl)
List info : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ma/default.aspx
