An XP pro system joined to a domain, appears to login with the cached user credentials, can access the Exchange server and the internet, but cannot access the MS network. in services found the workstation service would not start, and the net logon service wuld also not start. I have removed the networking components, removed the NIC, reinstalled all - no success. I have removed all XP and explorer patches, no success, then installed XP SP 1a no success. Any Suggestions? If not I am going to lose a day wiping out the OS and starting over...all those applications and downloaded patches.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Workstation service fails to start with 2250 error
- Thread starter lanclass
- Start date
If you cannot reinstall SP1, verify that the Objectname string value is set to LocalSystem in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan
After you do so, delete the following registry subkeys. These subkeys on a Windows XP-based computer that does not have SP1installed can cause the symptoms described earlier:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\25
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\26
To delete these keys, follow these steps.
Note This procedure includes steps to back up the registry keys before you modify them.
Click Start, and then click Run.
In the Open box, type regedit, and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan
On the File menu, click Export.
In the File Name box, type exported rasman key, and then click Save.
In the RasMan key, locate and then click the ObjectName string value.
If this value is not set to LocalSystem, follow these steps:
On the Edit menu, click Modify.
In the Value data box, type LocalSystem, and then click OK.
Locate and then double-click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\25
On the Edit menu, click Delete.
Click Yes to confirm that you want to delete the selected registry key.
Repeat steps 7 to 9 to delete the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\26
Quit registry editor, and then restart your computer.
You should re-apply Service Pack 1.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan
After you do so, delete the following registry subkeys. These subkeys on a Windows XP-based computer that does not have SP1installed can cause the symptoms described earlier:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\25
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\26
To delete these keys, follow these steps.
Note This procedure includes steps to back up the registry keys before you modify them.
Click Start, and then click Run.
In the Open box, type regedit, and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan
On the File menu, click Export.
In the File Name box, type exported rasman key, and then click Save.
In the RasMan key, locate and then click the ObjectName string value.
If this value is not set to LocalSystem, follow these steps:
On the Edit menu, click Modify.
In the Value data box, type LocalSystem, and then click OK.
Locate and then double-click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\25
On the Edit menu, click Delete.
Click Yes to confirm that you want to delete the selected registry key.
Repeat steps 7 to 9 to delete the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\26
Quit registry editor, and then restart your computer.
You should re-apply Service Pack 1.
- Thread starter
- #3
Well, I tried this suggestion, although you may have missed my problem in the original post. Windows XP svc pack 1a is installed. The problem is in connecting to the network. I cannot identify when the system quit starting the workstation service and netlogon. What I get now when I try nd manually start the Workstation service is a failure with error code 2250. Yet, Outlook 2000 and the connection to and sharing of calendars in Exchange Server is working.
If you have no other suggestions, I have scheduled the normal MS solution, fdisk and complete re-install, thursday am.
If you have no other suggestions, I have scheduled the normal MS solution, fdisk and complete re-install, thursday am.
A re-install is not warranted in this situation. The 2250 error is relatively benign. It means only that the connection expected was not available. For example, if you in a batch file had referenced a drive letter that had been previously mapped but no longer was you would receive this error.
Something in the logon script or other .bat or .cmd or .vbs or other things called during startup are referncing a network device that has not been preceded with a map.
If this is a Windows 2000 Domain, be certain that you specify in Group Policy that the default policy for asynchronous logon processing is disabled. open the MMC and add the group policy snap-in. Under Computer Configuration-->Administrative Templates-->System-->Logon, change "Always wait for the network at computer startup and logon" to ENABLED.
This can be fed to clients via a group policy from a Windows 2000 server by upgrading the standard policy template with the XP policy template. Since this is an XP only command, non-XP systems will ignore it in a domain distributed group policy.
I suspect that reinstalling the XP OS in the alternative will not address your underlying issues.
Something in the logon script or other .bat or .cmd or .vbs or other things called during startup are referncing a network device that has not been preceded with a map.
If this is a Windows 2000 Domain, be certain that you specify in Group Policy that the default policy for asynchronous logon processing is disabled. open the MMC and add the group policy snap-in. Under Computer Configuration-->Administrative Templates-->System-->Logon, change "Always wait for the network at computer startup and logon" to ENABLED.
This can be fed to clients via a group policy from a Windows 2000 server by upgrading the standard policy template with the XP policy template. Since this is an XP only command, non-XP systems will ignore it in a domain distributed group policy.
I suspect that reinstalling the XP OS in the alternative will not address your underlying issues.
Check the registry entries. You will be very unappy with Domain communications if, as in this case, your cannot start your Winlogon and Server Services from the workstation.
If this is exactly your problem, the most common cause is either your have msblast or a newer variant, or you removed msblast with a removal tool that left these services unstarted as an unintended side-effect.
1. Try restoring the original registry entries for all service entries. It does depend on your version of XP. BlackViper's site has some .reg files you can use:
2. If, after a reboot, your services are still not starting, do a maintenance reinstallation of the OS. There are things possible by accessing the OS that cannot be done simply with registry changes.
3. If that is not working, do a clean install.
Make sure you are absolutely certain that in your case the issue is identical to the one that started this thread: Winlogon and Server services cannot start. I would really hate to see you have other likely issues that show similar symptoms but not identical solutions.
You can always check your services through Control Panel, Administrative Tools, Service. You can always do a Start, Run services.msc.
If you really cannot re-start the services, a repair installation or unfortunately a clean install is often the shortest answer.
If this is exactly your problem, the most common cause is either your have msblast or a newer variant, or you removed msblast with a removal tool that left these services unstarted as an unintended side-effect.
1. Try restoring the original registry entries for all service entries. It does depend on your version of XP. BlackViper's site has some .reg files you can use:
2. If, after a reboot, your services are still not starting, do a maintenance reinstallation of the OS. There are things possible by accessing the OS that cannot be done simply with registry changes.
3. If that is not working, do a clean install.
Make sure you are absolutely certain that in your case the issue is identical to the one that started this thread: Winlogon and Server services cannot start. I would really hate to see you have other likely issues that show similar symptoms but not identical solutions.
You can always check your services through Control Panel, Administrative Tools, Service. You can always do a Start, Run services.msc.
If you really cannot re-start the services, a repair installation or unfortunately a clean install is often the shortest answer.
- Thread starter
- #7
It is entirely possible the user did a self removal of blaster or any number of other problems. He is frequently messing things up. I have no sympathy. I am more than happy to spend time helping polite users, but am not about to waste a minute on the unwashed. I fdisked and reinstalled clean back on 9-23. Hope he backed up things he wanted. Thanks for the links to the registry info, will check for future reference.
- Status
Similar threads
