Slow preparing network connections/loading settings

[TechTJ]

Ok, I have noticed that some XP Pro machines take too long Preparing Network Connections and once you log on it takes about the same time Loading Personal Settings. This was a major issue at work that we had to downgrade new workstations to W2K Pro.

Does anybody have a clue? ... or even better, the fix?

Thanks

 

[TechTJ]

I found this article on Technet.com but it didn't work. You might get luckier than me and get it to work. Go to Technet and search for article 329457.

Good luck and keep me posted

 

[Pehooo]

Is it connected to 2k Domain ?

 

[rmarton]

I had the same problem on a NT Domain with WinXP Pro clients. The initial network setup was painfully slow.

I call MS Tech Support and it's a known issue and had the problem solved free by MS Tech support.

The solution to my issue is in the following Knowledge base article.

Microsoft Knowledge Base Article - 321169

 

[rmarton]

Further to the Hot fix is the XP Local Security settings in Group Policy. The fix is as follows.

Configuring SMB Signing in Windows2000, XP and .NET:
==============================================

SMB Signing should be configured via Policies as a local registry value change will not have an affect if there is an overriding Domain policy. The associated registry values that are changed when the Policy is configured are also included.

Configured via Group Policy / Security Settings / Local Policies / Security Options:
----------------
(This example uses the default values for a domain member that is not a Domain Controller)

Workstation / Client:
Digitally sign client communication (always) Disabled
Digitally sign client communication (when possible Enabled

Server:
Digitally sign server communication (always) Disabled
Digitally sign server communication (when possible) Disabled


Windows2000 SMB Signing Registry keys associated with the above Policy configuration:

-------------------------
"Digitally sign client" in the policy maps to the following registry key:

HKey_Local_Machine\System\CurrentControlSet\Services\LanManWorkstation\Parameters

Value Name: RequireSecuritySignature
Data Type: REG_DWORD
Data: 0 (disable), 1 (enable)
Default value: The default is 0 (disable)

Value Name: EnableSecuritySignature
Data Type: REG_DWORD
Data: 0 (disable), 1 (enable)
Default value:
Domain Controllers: The default is 1 (enable)
Other machines: The default is 0 (disable).


"Digitally sign server" in the policy maps to the following registry key:

HKey_Local_Machine\System\CurrentControlSet\Services\LanManServer\Parameters
Value Name: RequireSecuritySignature
Data Type: REG_DWORD
Data: 0 (disable), 1 (enable)
Default value:
The default is 0 (disable)

Value Name: EnableSecuritySignature
Data Type: REG_DWORD
Data: 0 (disable), 1 (enable)
Default value:
Domain Controllers: The default is 1 (enable)
Other machines: The default is 0 (disable).


Value Name: EnableW9xsecuritysignature
Data Type: REG_DWORD
Data: 0 (disable), 1 (enable)
Default value:
This registry value does not exist in the registry by default.

NOTE:
For WindowsNT4 machines to negotiate and use SMB Signing when connecting to a Windows2000 or later machine, the following must be used: This is described in the unfinished article "Q319220 Windows NT 4.0 cannot connect
to Windows 2000 with SMB Signing". There is no policy associated with EnableW9xsecuritysignature registry value.

 

[TechTJ]

Well, I was wrong. It seems that the patch DID WORK in my case. I just needed to reboot a couple of times and now my system boots normally.

Cheers