Trouble Mapping a Windows 2003 Server Share from Windows Vista

[Guest 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

[Guest Jabez Gan [MVP]]

Re: Trouble Mapping a Windows 2003 Server Share from Windows Vista

 

Can you try disablign auto tuning in Windows Vista? See this page for more

information: http://www.neoblog.co.uk/?p=13

http://www.petri.co.il/improve_windows_vista_network_performance.htm

 

--

Jabez Gan

Microsoft MVP: Windows Server - File Storage

"brianjester" <brianjester@gmail.com> wrote in message

news:d77e047f-1824-402b-8d69-fa6edc509f9a@d21g2000prf.googlegroups.com...

> 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

[Guest brianjester]

Re: Trouble Mapping a Windows 2003 Server Share from Windows Vista

 

Jabez,

 

[snip]

> Can you try disablign auto tuning in Windows Vista? See this page for more

> information:http://www.neoblog.co.uk/?p=13

 

[snip]

 

Yes, I disabled auto-tuning per the reference (setting the machine to

the default Windows XP behavior), rebooted and our Vista machines now

work fine now with the share from the Windows 2003 Server file server.

 

The command was run in an Administrator cmd window:

 

netsh interface tcp set global autotuning=disabled

 

Cheers,

 

Brian Jester

[Guest brianjester]

Re: Trouble Mapping a Windows 2003 Server Share from Windows Vista

 

[snip]

 

Thank you!

 

-Brian

[Guest Jabez Gan [MVP]]

Re: Trouble Mapping a Windows 2003 Server Share from Windows Vista

 

You are always welcome ;)

 

--

Jabez Gan

Microsoft MVP: Windows Server - File Storage

"brianjester" <brianjester@gmail.com> wrote in message

news:e452458e-73e5-45d5-aca4-127c82750516@e23g2000prf.googlegroups.com...

> [snip]

>

> Thank you!

>

> -Brian