Where do I begin. Our network specialist (who is in another city) advised us to disable the "Remote Access Connection Manager" Service to avoid any intruders from coming in to our webserver. Well, our technician also disabled the "Remote Access Auto Connection Manager" Service, the "Remote Procedure Call (RPC)" Service, and the "Remote Procedure Call (RPC) Locator" Service. When we shut down and rebooted, all hell broke loose! Our websites on the werbserver are now not working, and to makematters worse, we can't open up any "properties" on any services to re-start/enable them. In fact, we can't open property sheets for any program. Also, when we tried to view contents of our hard drive, the WINNT folder shows 174 items, but no icons are displayed are can be selected (this only hapens to this folder). In the network Places, 4 items are said to exist, but none are shown. We have tried everything possible. We can't start the services that we disabled because we don't have a property sheet that shows. We know it acknowledges a property sheet because when we try to close the services window, it tells us to close all property boxes. Any suggestions as to how to reverse this mess? Thanks a million. Victor Puyada

so he left a mess.... Do you have adminstrator rights on the server?

Yes, he did his damage well (lol). Actually, I wanted to update this thread with a solution I just found. I fenagled around a bit until I realized that the registry would be my best friend. I went to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services Then I searched for the RPC services. I went to "RpcSs" and changed the 'start' value from "4" (disabled) to "3" (manual). I also did the same for "RpcLocator". shut down and rebooted. Voila! The services started up again as normal, and I was now able to view property sheets and our webpages were now accessible to the outside world. Hope this helps anyone who comes across this problem. For more detailed information, you can also view this link to a MS Knowledge Base thread that explains symptoms and possible solutions to this very problem: http://support.microsoft.com/default.aspx?scid=kb;en-us;307309 Thanks Vic