B
brianjester
Background:
In our office we have three (3) Windows Vista clients (new Dell PC's),
and twelve (12) Windows XP SP2 clients (older PC's Dell, HP, etc) and
a Windows 2003 Server (older Dell PC) that we use as a file server
using simple sharing.
The twelve (12) Windows XP SP2 clients can map the share with no
problem ( I:\ drive mapped to \\X.Y.Z.155\Integration) and also use
Explorer to navigate to the UNC path with no problem (\\X.Y.Z.
155\Integration)
The Problem/Symptoms:
The three (3) Windows Vista clients can map the drive and navigate to
the UNC path but all experience severely reduced functionality
manifested as:
1) long delays traversing the directory structure - like 15 to 30
seconds to go up or down one directory within the share.
2) "Not Responding" in the title bar of the Explorer window during
directory traversals.
Remediation Steps We Tried:
We had thought that the NTLMv2 settings in the Local Security Policy
(Network security:LAN Manager authentication level) werre incorrect or
different between Windows Server 2003 and Windows Vista, so we then
set both to: "Send NTLMv2 response only\refuse LM & NTLM" (http://
technet2.microsoft.com/windowsserver/en/library/b7cff04a-53d0-44a7-
b2f4-496a17470fb41033.mspx?mfr=true)
But the symptoms experienced by the three (3) Windows Vista clients
are the same.
Workaround (SneakerNet):
Now, all three (3) of the Windows Vista client users have to use UFD
(USB Flash Drives) or burn CDROMs/DVD/s and carry them over to the
Windows 2003 Server to add files or just sit at the File Server in
order to access our shared files - a sad "punishment" for using the
Windows Vista.
Other options we are considering are running Windows XP virtual
machines in either VMWare or MS Virtual PC on each Windows Vista
machine as a workaround
Question:
Is this a known issue between Windows Vista and Windows 2003 Server or
any other O/S.
Brian Jester
In our office we have three (3) Windows Vista clients (new Dell PC's),
and twelve (12) Windows XP SP2 clients (older PC's Dell, HP, etc) and
a Windows 2003 Server (older Dell PC) that we use as a file server
using simple sharing.
The twelve (12) Windows XP SP2 clients can map the share with no
problem ( I:\ drive mapped to \\X.Y.Z.155\Integration) and also use
Explorer to navigate to the UNC path with no problem (\\X.Y.Z.
155\Integration)
The Problem/Symptoms:
The three (3) Windows Vista clients can map the drive and navigate to
the UNC path but all experience severely reduced functionality
manifested as:
1) long delays traversing the directory structure - like 15 to 30
seconds to go up or down one directory within the share.
2) "Not Responding" in the title bar of the Explorer window during
directory traversals.
Remediation Steps We Tried:
We had thought that the NTLMv2 settings in the Local Security Policy
(Network security:LAN Manager authentication level) werre incorrect or
different between Windows Server 2003 and Windows Vista, so we then
set both to: "Send NTLMv2 response only\refuse LM & NTLM" (http://
technet2.microsoft.com/windowsserver/en/library/b7cff04a-53d0-44a7-
b2f4-496a17470fb41033.mspx?mfr=true)
But the symptoms experienced by the three (3) Windows Vista clients
are the same.
Workaround (SneakerNet):
Now, all three (3) of the Windows Vista client users have to use UFD
(USB Flash Drives) or burn CDROMs/DVD/s and carry them over to the
Windows 2003 Server to add files or just sit at the File Server in
order to access our shared files - a sad "punishment" for using the
Windows Vista.
Other options we are considering are running Windows XP virtual
machines in either VMWare or MS Virtual PC on each Windows Vista
machine as a workaround
Question:
Is this a known issue between Windows Vista and Windows 2003 Server or
any other O/S.
Brian Jester