Weird problems with an XP PC.
Posted on 2006-11-30
I just had a weird experience with an XP domain member PC. The machine is a win2k workstation that had been upgraded to XP several months ago. It doesn't have many applications installed on it as it is used primarily as a proxy (WEB) on which an application named "WEBMarshal" is running. WEBMarshal receives requests from within our domain for web pages and determines through policies and member lists whether that request should be honored and that page displayed to the requestor . The problems started yesterday with pages not being displayed as requested. I looked at the PC and couldn't get any pages on the actual proxy PC itself I tried pinging other machines ao our network and was able to ping every one I tried. I tried pinging the proxy from the other workstations and was able to do that also. I made sure that all of the setting for the application and it's proxy configuration were correct, and they were.I made certain that our DNS & DHCP records all looked correct and they did.
The other weird thing going on was after a reboot, I got this message, "Your system has no paging file, or the paging file is too small. To fix this problem, go to system in the control panel, click the advanced tab, settings and advanced. Click custom size and set the pagefile to at least.............." I did all that and the pagefile had been set to something like 245 MB and the PC has created a temporary pagefile of 265 MB to get around the issue. I clicked Custom and set it to a minimum of 1500 MB with a maximum of 2300 MB and clicked set. After clicking it, it remained at a size of 265 MB and said it needed a reboot. I rebooted and got the error again and reset the size again and rebooted again, several more times and it never changed.
I then got the bright idea to use system restore to fix whatever the problem was, so I started System restore and figured that if I returned the system to the 1st of November, that we'd be OK. I did and it went through the process and rebooted, after rebooting it said that it wasn't able to restore the sytem to that date. I tried another date with the same results and again it failed.
Looking in the event viewer I noticed the following Information Event, " NMS initialization during system startup failed" and couldn't remember having seen that one before. With no Internet I wasn't able to Google it so I decided to look through the services.msc and found several services disabled, they are/were. "Intel NMS", "Network DDE" and "Network DDE DSDM". I was able to start the Intel NMS and the Network DDE after reading the descriptions it sounded as if they were necessary for network connectivity so i changed their states from "disabled" to "Automatic" and started each one. Now, however the Network DDE is back to "disabled" somehow. Anyways, as soon as I started those, I was able to get a web page and shortly after that everyone else was able to as well. So now everybody is happy because they can get on the web and check out the scores on ESPN, or whatever, but I'm wondering what the heck happened to cause all of that. The machine in question is in a locked office (mine) and is never even looked at unless something goes wrong with the web access so I know that no one tampered with it.
Anyone have any ideas on why those services were disabled (they sound like they are necessary services) and are disabled again. And why everything worked after I started them? Or why I couldn't use sytem restore, or what happened with the pagefile?