windows 2003 domain dfs

[zeezam]

We have DFS setup and after we upgrade our clients to windows 7 they got problem with accessing the dfs share sometimes. Works fine with windows xp.

The file server is a Windows 2008 R8 and our AD domain Windows 2003.

We have mapped the share with a loginscript for our clients.

Sometimes the share gets inaccessible for the user, or when accessing the share - windows explorer "jumps" back to My Computer.

Any ideas?

We have tried with changing this registry value but no success.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]

"lmcompatibilitylevel"=dword:00000001

[Tripredacus]

Do a test on a Win7 PC. Go into Network Properties and disable the two Link Layer Topology options (mapper and scanner) and reboot and see if it is any better. It might not be related...

[zeezam]

Do a test on a Win7 PC. Go into Network Properties and disable the two Link Layer Topology options (mapper and scanner) and reboot and see if it is any better. It might not be related...

What makes you think that would help?

I'll make a try

Any event logs or something I can check next time it happens?

Edit:

Is it possible to turn off in registry?

Edited November 3, 2011 by zeezam

[Tripredacus]

You can change it in Local Security Policy, but if the boxes were checked prior to using this setting, the boxes will remain checked even though the it will actually be disabled.

The reason I brought up this idea was because I had similar situation when Vista and 7 came out. Copying files over the network was extremely slow for Vista and 7 clients but not for XP. When I say slow, I mean it takes XP 6 minutes and takes Vista 6 hours. Disabling those two network options would "fix" a Vista or 7 PC and transfer was normal.

However, once we put a DC in that was 2008, the problem went away and we didn't have to disable those settings anymore. How those work is that Vista would go out and try to map out the network, basically sending out packets similar to DHCP Discover, because it is expecting a response from a DC. Unfortunately, Server 2003 did not have the LLT Responder either enabled or installed by default, so no response would be sent. This made the client keep sending out these packets and it would slow its own network speed down. The Server 2008 DC was able to send the response. And also because XP also doesn't come with this ability installed, it doesn't bog itself down with these packets even if there is a Server 2008 on the network.

It may not be related, but its easy enough to test.

[zeezam]

You can change it in Local Security Policy, but if the boxes were checked prior to using this setting, the boxes will remain checked even though the it will actually be disabled.

The reason I brought up this idea was because I had similar situation when Vista and 7 came out. Copying files over the network was extremely slow for Vista and 7 clients but not for XP. When I say slow, I mean it takes XP 6 minutes and takes Vista 6 hours. Disabling those two network options would "fix" a Vista or 7 PC and transfer was normal.

However, once we put a DC in that was 2008, the problem went away and we didn't have to disable those settings anymore. How those work is that Vista would go out and try to map out the network, basically sending out packets similar to DHCP Discover, because it is expecting a response from a DC. Unfortunately, Server 2003 did not have the LLT Responder either enabled or installed by default, so no response would be sent. This made the client keep sending out these packets and it would slow its own network speed down. The Server 2008 DC was able to send the response. And also because XP also doesn't come with this ability installed, it doesn't bog itself down with these packets even if there is a Server 2008 on the network.

It may not be related, but its easy enough to test.

It seems to work so far with disable LLT.

I can't disable those with gpo in 2003 dc. Is there any registry settings I can put in a login script?

[Tripredacus]

Yeah I can see that being an issue.

I can't see how to disable just those two options in the registry, only how to disable IPv6.

It doesn't seem there is an ADMX for Server 2003 that will allow it to disable the M/R on a Vista or Win7 PC, although it is available for Server 2008... which obviously this wouldn't be an issue.