Get network connection before login

February 18, 2009 at 08:30:51
Specs: Windows XP
Is there a way to have XP Pro establish a wired network connection before a user is able to log in?

Some of my users are logging into thier PCs before the network connection is established. This is causing issues with thier roaming profiles.

Thanks,
Scott


See More: Get network connection before login

Report •


#1
February 18, 2009 at 10:24:35
Users cannot login into a network, or a Domain, or into server unless they HAVE a network connection established first. The networking components work in the background as the OS loads before login. Sometimes there are delays in this though, especially with a poorly configured or optimized (slow) network or with some sort of HIPS ( http://www.webopedia.com/TERM/H/HIP... system running on the PC which can block access.

Could be Domain, policy issues, network issues, local PC issues; roaming profiles can be a drag (if they're big) on a 10/100 Mb LAN too.

Just another stupid saying...


Report •

#2
February 18, 2009 at 10:41:29
Perhaps clarifying what is happening will help.

I am a system admin of about 50 PCs. The clients experiencing this issue are connected to my active directory server over a gigabit LAN. Both are XP Pro, one is SP2 and one is SP3.

My user boots up his PC and immediately logs on. Often he receives a message saying his roaming profile could not be found. His local profile then loads and a warning is displayed that some network drives could not be connected. In some cases I can see the system tray icon showing DHCP acquiring an IP. When he logs out his local profile then overwrites his roaming profile. He then logs back in without any errors but is given his local profile because it was just copied to the server.

Thanks,
Scott


Report •

#3
February 18, 2009 at 10:55:36
There is a Registry setting that lets windows load the desktop, when the login script has finished.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
You may have to load the Windows Desktop
NewKey: RunLogonScriptSync
Value: 1
Type: DWORD

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
NewKey: RunLogonScriptSync
Value: 1
Type: DWORD


Note: The entry for HKEY_CURRENT_USER takes priority over HKEY_LOCAL_MACHINE

This may help.

Please send a reply, if you solved the problem !!!


Report •

Related Solutions

#4
February 18, 2009 at 11:30:12
Thanks for the quick reply.

I looked in the registry and could not find the NT subfolder for either registry edit.

While the registry edit may fix my problem, it is not the root cause, right? If possible I would like to find and correct the root issue.

Thanks,
Scott


Report •

#5
February 18, 2009 at 12:20:16
It's "Windows NT" not only "NT" and it must be there.

Please send a reply, if you solved the problem !!!


Report •

#6
February 18, 2009 at 12:23:48
This Registry Key causes Windows to start all services Windows needs to start, then login and then startup the Desktop.

So it might help on your root issue.

Please send a reply, if you solved the problem !!!


Report •

#7
February 18, 2009 at 12:44:19
I found the "Windows NT" folder.

I have little experience editing the registry. Am I suppost to create a new folder called RunLogonScriptSync?

I have seen it where a command can be entered into Run that updates the registry. Would you be able to write the commands that would do that for me?

Thanks,
Scott


Report •

#8
February 18, 2009 at 12:56:44
"My user boots up his PC and immediately logs on."

As in autologon? That is only a local logon which is your problem.

follow this but in reverse ie take away instead of add.

http://www.petri.co.il/configuring_...

and make sure the user doesn't have tweakui installed.


Report •

#9
February 18, 2009 at 12:57:19
Copy & Paste these two Registry settings, each from BEGIN ... to END... into a new file and save it as
RunWinLogonSync_on.reg
and the other as
RunWinLogonSync_off.reg

So you can simply double click at one of the files to change these settings from on to off and vice versa.

File RunWinLogonSync_on.reg

# BEGIN RunWinLogonSync on
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"RunLogonScriptSync"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]
"RunLogonScriptSync"=dword:00000001
# END RunWinLogonSync on


File RunWinLogonSync_off.reg

# BEGIN RunWinLogonSync off
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"RunLogonScriptSync"=dword:00000000

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]
"RunLogonScriptSync"=dword:00000000
# END RunWinLogonSync on

Please send a reply, if you solved the problem !!!


Report •

#10
February 18, 2009 at 13:18:54
I created the files and tried running them. I get the following error.

Cannot import x:\runWinLogonSync_on.reg: The specified file is not a registry script. you can only import binary registry files from within the same registry editor.

My users are not useing autologin.

Thanks,
Scott


Report •

#11
February 18, 2009 at 13:40:13
1. I'd NOT use roaming profiles, they're more a pain than they're worth.

2. Look at the Application, System, and Security Event Viewer logs on the PCs with issues and on the Server to see if there's any indications on what is going wrong.

3. Don't rule out a flaky NIC, bad Cat5 patch cable, flaky Switch port etc, or OS or Profile corruption, or even a local hardware issue (HDD on the fritz).

BTW, there's no good reason to use autologin (I know you said you're not using that), unless its special system CNC, or application without an HID. Autologin can be used in local or Domain instances too.

Just another stupid saying...


Report •

#12
February 18, 2009 at 14:26:39
Ok, so change the following line:

Old:

Windows Registry Editor Version 5.00

New:
REGEDIT4

Save the files and give it another try.

Please send a reply, if you solved the problem !!!


Report •

#13
February 19, 2009 at 05:24:20
Thanks for the suggestion but I still get an error. It is the same as before except the word "same" is not in it. I checked my version of regedit, it is 5.1. I tried changing the line to match but that did not help.

Thanks,
Scott


Report •

#14
February 19, 2009 at 05:50:50
I got the script to run!

Unfortunatly it did nothing to fix the problem. Any more thoughts?

Thanks,
Scott


Report •

#15
February 19, 2009 at 06:06:08
I knew that script wasn't going to work, see my post #11.

Just another stupid saying...


Report •

#16
February 19, 2009 at 08:07:37
have you turned off the autologon?????????

Report •

#17
February 19, 2009 at 08:53:14
He said he's NOT USING AUTOLOGIN.

Just another stupid saying...


Report •

#18
February 19, 2009 at 09:22:47
Really?

Doesn't this scream autologon to you?

"My user boots up his PC and immediately logs on" and "His local profile then loads"

What is the issue here? Oh ya its "get network connection before logon"

Is the issue a network issue or is it logging on to the domain issue?

Appears all hardware is working fine. That eliminates a network issue. If you logon locally do you get a domain logon? NO.

Did Scott check the reg entry? No statement saying he had. He just makes a statement they aren't using autologon.

So Scott did you check the reg entry I referred you to?

Do you have the same results if YOU logon?


Report •

#19
February 19, 2009 at 10:25:42
Scream? Not really, well, in typical COMPUTING.NET fashion, I find it amazing he's a SysAdmin w/ 50 PCs, and he's not familiar with the Windows registry. Having him dig around in there right away and run reg key scripts is a tad bit risky. He should read this (twice if need be) http://support.microsoft.com/kb/315231 to even see if the Autologin keys are there to begin with. Auto login are keys that have to be ADDED in order for AUTOLOGIN to even work. http://support.microsoft.com/kb/315231

Just another stupid saying...


Report •


Ask Question