B3Groover
asked on
Workstation service error 2250 in XP Pro
Hi everyone,
After scouring this message board and reading several close problems to mine, I have yet to find an answer.
I am running a three computer network centered around a cable modem router (the Linksys BEFSR41). Computer 1 is an AMD 1.0GHz Tbird with XP Pro. Computer 2 is a 733MHz PIII with XP Pro. And Computer 3 is a 266MHz PII laptop running Windows 98SE.
Upon bootup of XP Machine #1, I get the following error in the Event Log:
The Workstation service terminated with service-specific error 2250 (0x8CA).
Since Workstation cannot load, several other services related to networking also don't load. This leads to the following problem.
Computers 2 and 3 can see every other computer on the network including Computer 1. Computer 1 cannot see the other two or itself. This is because the Server service is running fine and the Workstation service will not run I believe.
I can ping every computer using the xxx.xxx.xxx.xxx protocol from Computer 1. I can also ping 127.0.0.1 Computer 1 can ping every computer by name (for instance, computer 2 is called "Audio") EXCEPT itself.
If I run "cmd net use" it replies: The network is not present or not started.
I can access the internet with no problems at all from Computer 1 as well as the other machines.
I have tried returning the TCP/IP registries to default according to the Microsoft Knowledge Base article on Computer 1. I have uninstalled all network drivers and the network card and reinstalled everything to no avail. I even tried replacing the network card. Nothing.
BTW, both copies of Win XP do not have SP1 installed.
Any ideas? Thank you in advance.
----B3Groover
After scouring this message board and reading several close problems to mine, I have yet to find an answer.
I am running a three computer network centered around a cable modem router (the Linksys BEFSR41). Computer 1 is an AMD 1.0GHz Tbird with XP Pro. Computer 2 is a 733MHz PIII with XP Pro. And Computer 3 is a 266MHz PII laptop running Windows 98SE.
Upon bootup of XP Machine #1, I get the following error in the Event Log:
The Workstation service terminated with service-specific error 2250 (0x8CA).
Since Workstation cannot load, several other services related to networking also don't load. This leads to the following problem.
Computers 2 and 3 can see every other computer on the network including Computer 1. Computer 1 cannot see the other two or itself. This is because the Server service is running fine and the Workstation service will not run I believe.
I can ping every computer using the xxx.xxx.xxx.xxx protocol from Computer 1. I can also ping 127.0.0.1 Computer 1 can ping every computer by name (for instance, computer 2 is called "Audio") EXCEPT itself.
If I run "cmd net use" it replies: The network is not present or not started.
I can access the internet with no problems at all from Computer 1 as well as the other machines.
I have tried returning the TCP/IP registries to default according to the Microsoft Knowledge Base article on Computer 1. I have uninstalled all network drivers and the network card and reinstalled everything to no avail. I even tried replacing the network card. Nothing.
BTW, both copies of Win XP do not have SP1 installed.
Any ideas? Thank you in advance.
----B3Groover
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
what firewall is installed/was installed?
ASKER
Hi Steven,
Thank you for your response. I do not have any firewall on this computer. My only firewall on the network is the one built into my router, the Linksys BEFSR41.
If I try to start the Workstation service after bootup, it gives the following message: "Windows cannot start the Workstation on Local Computer. For more information, review the System Event Log."
Upon reviewing the log, it gives an Event ID of 7024 and says: "The Workstation service terminated with service-specific error 2250 (0x8CA)."
Notice this is the same error the fellow in article Q_20383466 has above, but I do not have SP1 installed so his solution does not apply to me.
I know that error 2250 means no network present. Of course, there is a network present because my other two computer can connect to the main computer fine. It's just the other way around that doesn't work!
Here's another interesting thing: When I originally stated that I can ping every computer by name except for Computer 1 from Computer 1, that was not totally true I found out. I changed the name of Computer 1 from "PLEASEGO" to "MAIN" while trying to get it to network. If I pinged "MAIN" I got no response, even those it said in System Properties that it's name was "MAIN". If I pinged "PLEASEGO" which no longer existed (supposedly) it would ping itself. Yet every other computer saw Computer 1 as "MAIN". So obviously some file or files are not keeping up with the times on Computer 1.
I will try the Windows File System Checker Tool and get back to you.
Thanks!
-----B3Groover
Thank you for your response. I do not have any firewall on this computer. My only firewall on the network is the one built into my router, the Linksys BEFSR41.
If I try to start the Workstation service after bootup, it gives the following message: "Windows cannot start the Workstation on Local Computer. For more information, review the System Event Log."
Upon reviewing the log, it gives an Event ID of 7024 and says: "The Workstation service terminated with service-specific error 2250 (0x8CA)."
Notice this is the same error the fellow in article Q_20383466 has above, but I do not have SP1 installed so his solution does not apply to me.
I know that error 2250 means no network present. Of course, there is a network present because my other two computer can connect to the main computer fine. It's just the other way around that doesn't work!
Here's another interesting thing: When I originally stated that I can ping every computer by name except for Computer 1 from Computer 1, that was not totally true I found out. I changed the name of Computer 1 from "PLEASEGO" to "MAIN" while trying to get it to network. If I pinged "MAIN" I got no response, even those it said in System Properties that it's name was "MAIN". If I pinged "PLEASEGO" which no longer existed (supposedly) it would ping itself. Yet every other computer saw Computer 1 as "MAIN". So obviously some file or files are not keeping up with the times on Computer 1.
I will try the Windows File System Checker Tool and get back to you.
Thanks!
-----B3Groover
ASKER
Steven, you are a genius. SFC worked like a champ. Is there a log file that this creates?! I'd like to see what it did. Whatever it did, I can see and access the network now from Computer 1. Brilliant! Thank you so much!
If you like jazz, check out my organ trio @ www.organissimo.org I'll send you a free CD of the trio for your help! :) Email me from the site.
Thank you!
-----Jim
If you like jazz, check out my organ trio @ www.organissimo.org I'll send you a free CD of the trio for your help! :) Email me from the site.
Thank you!
-----Jim
Jim
Glad to help! Not sure about a log file, never bothered to check LOL
I do know it check for bad or missing files, and replaces them if needed
Glad to help! Not sure about a log file, never bothered to check LOL
I do know it check for bad or missing files, and replaces them if needed
This is obviously an extremely old issue, but I figured I'd chime in with my experience on a Windows XP SP3 issue that mirrored this problem.
The problem was exactly the same, and the error when trying to start the workstation service was the same - as was the message in event viewer. I initially tried to run an sfc /scannow, but that process required a Windows CD to complete, and this machine is 2000 miles away from my location, with no CD on site.
Solution:
I delved deeper into the Event Viewer, and there were a couple of other errors from source "Workstation".
-"Could not load Rdbss device driver."
-"Could not load RDR device driver."
I browsed to the C:\Windows\system32\driver
I'd be curious to have seen what other Event Viewer errors you had when you were dealing with this issue. Checking through several other topics on this issue on Google, it seems that any number of drivers could be throwing the same error, and causing the Workstation service not to load - but the process for replacing the corrupt version should be the same as that with the rdbss.sys driver above - just use Event Viewer to find which driver is causing the problem.
The problem was exactly the same, and the error when trying to start the workstation service was the same - as was the message in event viewer. I initially tried to run an sfc /scannow, but that process required a Windows CD to complete, and this machine is 2000 miles away from my location, with no CD on site.
Solution:
I delved deeper into the Event Viewer, and there were a couple of other errors from source "Workstation".
-"Could not load Rdbss device driver."
-"Could not load RDR device driver."
I browsed to the C:\Windows\system32\driver
I'd be curious to have seen what other Event Viewer errors you had when you were dealing with this issue. Checking through several other topics on this issue on Google, it seems that any number of drivers could be throwing the same error, and causing the Workstation service not to load - but the process for replacing the corrupt version should be the same as that with the rdbss.sys driver above - just use Event Viewer to find which driver is causing the problem.
Special thanks to stevenlewis for the help. Logged in here this morning after searching many other places and found this thread. Short story is 'problem solved'! File System Checker Tool did the trick for me too!
Thanks so much,
Bill
Thanks so much,
Bill
Was totally stumped. Used the open discuss notes at the bottom. Found a copy and replaced the missing Rdbss.sys. Workstation Service started successfully. Thank you snydersofhanover.
https://www.experts-exchange.com/questions/20383466/Internet-up-but-Home-Network-down-on-WinXP-Pro.html