Warble
asked on
Workstation Service keeps browsers from working
Hi,
I have a Compaq Presario 3000 running XP home and it got a bit of adware and a couple of virii on it that I removed using Trendmicro Housecall, and Adaware.
Just after removing this stuff, the computer was working great, and the internet was working as well, I remember using IE extensively.
The next morning I booted up and could not access any web pages in IE. I also had an installation of Firefox, which didn't work either. I was able to ping and resolve DNS via the command prompt, but no Web browser.
The even viewer shows a bootup error from the Workstation Service: "Initialization failed because the requested service redirector could not be started" EventID 3113
This now happens every time I boot, and I cannot ever access anything via a browser, but the connection is good.
Just so you know I have a local lan that I connect through via Ethernet, with DHCP. Like I said, I can ping outside the network fine from the command prompt.
Any ideas on what might be going on here? I sure would appreciate it!
I have a Compaq Presario 3000 running XP home and it got a bit of adware and a couple of virii on it that I removed using Trendmicro Housecall, and Adaware.
Just after removing this stuff, the computer was working great, and the internet was working as well, I remember using IE extensively.
The next morning I booted up and could not access any web pages in IE. I also had an installation of Firefox, which didn't work either. I was able to ping and resolve DNS via the command prompt, but no Web browser.
The even viewer shows a bootup error from the Workstation Service: "Initialization failed because the requested service redirector could not be started" EventID 3113
This now happens every time I boot, and I cannot ever access anything via a browser, but the connection is good.
Just so you know I have a local lan that I connect through via Ethernet, with DHCP. Like I said, I can ping outside the network fine from the command prompt.
Any ideas on what might be going on here? I sure would appreciate it!
ASKER
I saw that, but it happens each time it boots, rebooting does not help.
I am the sysadmin, and unfortuanatly a lot more knowledgeable about unix stuff than windows. I'm running a Suse linux box that's connected to my cable modem. It's running NAT, dhcp, caching DNS and a firewall, and I have 2 win2k machines connected to it via a hub. The laptop is also connected to this hub.
So, there's no DC per-se.. It should just get and address, gateway, and dns servers, and be happy, right?
I am the sysadmin, and unfortuanatly a lot more knowledgeable about unix stuff than windows. I'm running a Suse linux box that's connected to my cable modem. It's running NAT, dhcp, caching DNS and a firewall, and I have 2 win2k machines connected to it via a hub. The laptop is also connected to this hub.
So, there's no DC per-se.. It should just get and address, gateway, and dns servers, and be happy, right?
Hm, yes it should.
Try changing the machine in question's name to something totally different. Let it reboot. Change the workgroup and let it reboot. Then change the workgroup back, reboot and change the name back. Then, you guessed it, reboot.
That should do all the same things as changing a machine name and domain if you dont have a DC around
Try changing the machine in question's name to something totally different. Let it reboot. Change the workgroup and let it reboot. Then change the workgroup back, reboot and change the name back. Then, you guessed it, reboot.
That should do all the same things as changing a machine name and domain if you dont have a DC around
ASKER
Thanks, I tried that, and only got part way. Here's what happened: I went into the control panel, then system properties, and clicked on the Computer Name tab to change the name. I clicked on the 'Change' button and changed the computer name, but the workgroup textfield was greyed out.
I rebooted, and went back in to change the workgroup name, but couldn't because it was still greyed out. I don't know if I'm completely spaced out, and this isn't the place to change workgroup name, but it can't be done that way.
Possibly related?
I rebooted, and went back in to change the workgroup name, but couldn't because it was still greyed out. I don't know if I'm completely spaced out, and this isn't the place to change workgroup name, but it can't be done that way.
Possibly related?
I am assuming that the Domain box that you can change was also greyed out?
ASKER
There is no domain box. It's XP Home. Just Computer Name and Workgroup.
Oh. That won't help. Then yes, I imagine the two are related. I assume you can get online now? If you want send an assistance request to quinnf@easynet.co.uk and I can take a look.
I think it may be the actual service that is at fault. Have you tried restarting it manually?
I think it may be the actual service that is at fault. Have you tried restarting it manually?
ASKER
I'm online on my linux box. I cannot get online on the laptop yet, although some stuff works, so I'll try and send out a request.
I did try restarting the service manually, but it does not start. I get the same error I mentioned above.
I did try restarting the service manually, but it does not start. I get the same error I mentioned above.
In that case assistance wont do much good. Try a system rollback to a week ago? Or a month, just go through the restore points until one works then add your patches one at a time from there and try to isolate the problem
ASKER
The computer did not have any restore points. I ended up reinstalling windows, this did not work either as the same problem remained, so I formatted the hard drive (after backing up!) and installed from scratch. The unit works great now.
Thank you for your help.
Thank you for your help.
ASKER
As I resolved this by reinstalling XP, I'm asking to have this question deleted.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you have rebooted and are still getting the problem try disjoining the domain and then rejoining. It could be that for some reason the SID for your system has altered (renamed system, damaged registry etc) and the DC is no longer recognising it.
If you are not the sysadmin you will need to speak to them to sort out the domain membership as it requires domain admin passwords.