XP Service Pack 3 Upgrade - No Incoming Network After Install and Constant Rebooting
Hello All,
I have a strange problem with XPSP3. I've found various inconsistencies that are more than a little frustrating.
Many of my system, that I upgrade perpetually reboot after the install. After a little research I found that without exception, (for me anyway) it's the usbport.sys file that causes this. If you grab the old one from the "service Pack uninstall" folder and copy it to the c:\windows\system32\driver
So I wrote a script to try and get around this:
start " " /b /wait "\\server\XP_Service Packs\XP-SP3.EXE" /passive /norestart"
rename c:\windows\system32\driver
copy /y /v "\\server\it$\Scripts\XPSe
shutdown /f /r /t 00
There's quite a lot more but this is the bit that matters. I can find no other way to remedy this problem, and that is absolutely crazy considering that this does not appear to be obscure in the least.
Does anybody have a better solution? If not, then the other problem I've encountered is that if you delete anything out of "c:\windows\system32\drive
Next issue, After a successful install of SP3, I've noticed that when the system comes back up, I as an Admin can not connect to it. I can ping it, and from the users perspective they can browse and access the network fine, but it will not let anything connect to it from the outside. I can't hit any shares, including the c$ or connect to it in anyway other than ping it. If I reboot them they work fine, sometimes it takes a couple reboots but that always fixes it. Does anybody have a solution to this one? I've made sure Computer Browser is running and that the firewall hasn't been activated none of this is the problem.
As always, thanks for the help
Eric
I have a strange problem with XPSP3. I've found various inconsistencies that are more than a little frustrating.
Many of my system, that I upgrade perpetually reboot after the install. After a little research I found that without exception, (for me anyway) it's the usbport.sys file that causes this. If you grab the old one from the "service Pack uninstall" folder and copy it to the c:\windows\system32\driver
So I wrote a script to try and get around this:
start " " /b /wait "\\server\XP_Service Packs\XP-SP3.EXE" /passive /norestart"
rename c:\windows\system32\driver
copy /y /v "\\server\it$\Scripts\XPSe
shutdown /f /r /t 00
There's quite a lot more but this is the bit that matters. I can find no other way to remedy this problem, and that is absolutely crazy considering that this does not appear to be obscure in the least.
Does anybody have a better solution? If not, then the other problem I've encountered is that if you delete anything out of "c:\windows\system32\drive
Next issue, After a successful install of SP3, I've noticed that when the system comes back up, I as an Admin can not connect to it. I can ping it, and from the users perspective they can browse and access the network fine, but it will not let anything connect to it from the outside. I can't hit any shares, including the c$ or connect to it in anyway other than ping it. If I reboot them they work fine, sometimes it takes a couple reboots but that always fixes it. Does anybody have a solution to this one? I've made sure Computer Browser is running and that the firewall hasn't been activated none of this is the problem.
As always, thanks for the help
Eric
ASKER
Thanks grtraders,
These systems have updated drivers. Not sure how you missed this being an issue. It's all over Microsoft's site with basically the same fix as I stated above. Which isn't really a fix. This is a much larger problem on the newer systems I have than the older ones.
Being in the I.T. industry I know many people around town in my field. They have seen this issue since day one and are also just having to deal with it. Not to mention it's all over the Internet with, again, basically this same fix. On a side note, my brother called me a couple of weeks ago because his system was rebooting after applying SP3, he has about a 1 year old Alienware system and his drivers are most definitely up to date. Drivers do not appear to be the issue (other than Microsoft's usbport.sys file that is).
Moreover, I highly doubt that out of the 10 system, (6 different models, and 6 different loads) they all would have exactly the same corrupt files, to cause exactly the same exact issue. However, I'm running System File Checker on one of my problem system anyway.
These systems have updated drivers. Not sure how you missed this being an issue. It's all over Microsoft's site with basically the same fix as I stated above. Which isn't really a fix. This is a much larger problem on the newer systems I have than the older ones.
Being in the I.T. industry I know many people around town in my field. They have seen this issue since day one and are also just having to deal with it. Not to mention it's all over the Internet with, again, basically this same fix. On a side note, my brother called me a couple of weeks ago because his system was rebooting after applying SP3, he has about a 1 year old Alienware system and his drivers are most definitely up to date. Drivers do not appear to be the issue (other than Microsoft's usbport.sys file that is).
Moreover, I highly doubt that out of the 10 system, (6 different models, and 6 different loads) they all would have exactly the same corrupt files, to cause exactly the same exact issue. However, I'm running System File Checker on one of my problem system anyway.
ASKER
System File Checker didn't do anything. No problem there.
Bios upgrades !! did you check for them?
I know Bios won't be the issue here but I guess, something was erronously fixed at a hardware level in the Bios (leaving an error) which was then later again fixed in SP3. Maybe your machine is somewhere in between.
Anyways as a workaround, delete the usbport.sys from the c:\windows\system32\dllcac
Ravi.
I know Bios won't be the issue here but I guess, something was erronously fixed at a hardware level in the Bios (leaving an error) which was then later again fixed in SP3. Maybe your machine is somewhere in between.
Anyways as a workaround, delete the usbport.sys from the c:\windows\system32\dllcac
Ravi.
ASKER
Got any ideas on my last paragraph?
Sorry about that, re-read your Question.
No ideas about ur last para ... "Next issue, After a successful install of SP3, I've noticed that when the system comes back up....... I've made sure Computer Browser is running and that the firewall hasn't been activated none of this is the problem."
Forigve me but I think something is really screwing up the sytems harshly.
Are you confident about the file genuinity of the SP3 file / CD . I would check the MD5sum to be sure. How about going through the known issues of SP3 installs at the microsoft website and see if there is a workaround.
The install is not going on smoothly and in my opinion network connectivity should not fail as reported by you,
Regarding the reboots, you can try this to avoid them --
Control Panel >> system >> advanced tab >> settings button under Startup and recovery >> uncheck "automatic restart" under system failure,
Ravi.
No ideas about ur last para ... "Next issue, After a successful install of SP3, I've noticed that when the system comes back up....... I've made sure Computer Browser is running and that the firewall hasn't been activated none of this is the problem."
Forigve me but I think something is really screwing up the sytems harshly.
Are you confident about the file genuinity of the SP3 file / CD . I would check the MD5sum to be sure. How about going through the known issues of SP3 installs at the microsoft website and see if there is a workaround.
The install is not going on smoothly and in my opinion network connectivity should not fail as reported by you,
Regarding the reboots, you can try this to avoid them --
Control Panel >> system >> advanced tab >> settings button under Startup and recovery >> uncheck "automatic restart" under system failure,
Ravi.
Regarding the shares, do a disk check & maybe it would correct any permissions going haywire. Create new accounts and see if they also fail. Could be some issue with the user profiles.
Ravi.
Ravi.
ASKER
Well I figured out what the problem is, even if I don't know why or how.
I have a group policy that disables my firewalls internally on all my workstations. Now, if you go into services and look at the firewall, it will show disable and it is stopped. Now since I have a group policy it won't let me start it. So, I decided to kill the group policy and then do a gpupdate /force on the workstation. Next I went in and set the service to manual and started it. Then I turned it off. All of the sudden I can hit the machine again.
I'm now quite sure the Firewall is running on my workstation even though I have a group policy that tells it not to, and despite the fact that from the view in Services it says otherwise.
Very strange. Does anybody have an idea what this all about? I could really use some help here.
Thanks
Eric
I have a group policy that disables my firewalls internally on all my workstations. Now, if you go into services and look at the firewall, it will show disable and it is stopped. Now since I have a group policy it won't let me start it. So, I decided to kill the group policy and then do a gpupdate /force on the workstation. Next I went in and set the service to manual and started it. Then I turned it off. All of the sudden I can hit the machine again.
I'm now quite sure the Firewall is running on my workstation even though I have a group policy that tells it not to, and despite the fact that from the view in Services it says otherwise.
Very strange. Does anybody have an idea what this all about? I could really use some help here.
Thanks
Eric
Is it the windows firewall we are talking about or something else. If something else, maybe the firewall is just not obeying the Group Policy rules.
Ravi.
Ravi.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I think you need to get updated drivers for your motherboard from the manufacturer's website and install them. Most probably the problems should sort themselves out.
Moreover have you tried sfc /scannow Type the Bold text in the Run dialog box and let windows replace any corrupt system files that you may be having. You will need your windows CD in hand just in case the utility asks for it.
Ravi.