cluberti

Instead of deliberately taking steps that are quite likely to either completely break XP, or cause it to go into an SFC panic, how about creating a shortcut to the application instead, and configure the shortcut's properties to start the application in Windows 95 compatibility mode?

What happens if you try to access \\pc2\ipc$ ?

Good to hear - watch those creative drivers, and avoid their products if at all possible due to issues like this.

Don't double post - it's in the forum rules. Deleting your other duplicate post from the other sections of the boards.

When you look at the system event log, do any of the Service Control Manager errors specify why the service won't start? Also, what account is being used to run the services?

What about a network trace from a client of this happening, to see what kind of auth the client is sending, and the 403 response from the server should tell us what level of auth the server is requiring (they'll likely not match).

The local GPO does have software restriction policies being applied, that's what the Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers\ registry keys point to, and specifically the rule for Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers\TransparentEnabled set to 1 means that Software Restriction Policies are enabled and functional from policy. So, you need to look just a little harder at the local group policies, because your statement before means you missed something obvious: If you need help figuring out how to turn this off, try looking at this technet article. It's in there, and gpresult says so.

See if you can boot the XP CD to the recovery console, and either disable the Creative service or rename that file on disk.

http://www.microsoft.com/communities/newsg...957f673&p=1

Actually, you probably got a STOP 0x7E in the ctoss2k.sys driver, and since that's a somewhat well-known issue with the Creative drivers, you should try booting in safe mode and uninstalling the creative drivers and software to get your box booting again.

That's hard to say - perhaps you could get a memory dump for us to look at?

Can you provide the exact error, or the server OS, or any other pertinent info?

Which hotfix are you attempting to install?

Well, for example: gpresult /z > C:\gpresult.txt ... will create the file gpresult.txt on C:\.

What group policies are being applied to this user and this computer? Run a gpresult /z out to a txt file to see.

The cryptographic service isn't a "service" in the SCM on Windows 2000, it runs in kernel and is always running - you won't see it in the services list. Try running regsvr32 on the following .dlls, reboot, and see if things work: wintrust.dll initpki.dll dssenh.dll rsaenh.dll gpkcsp.dll sccbase.dll slbcsp.dll cryptdlg.dll

Because it doesn't work the way you are thinking - it blocks the COMPUTER ACCOUNT for that computer from accessing the folder (really the LocalSystem account running under that computer's context), but not the user account on that machine. AD doesn't work that way.

OK, so an administrator has created a software restriction policy in group policy for msi packages.

If it boots in safe mode, but not a regular boot, it sounds almost like a driver is causing it. Are you sure it's rebooting, and not bugchecking and automatically rebooting?

Run Process Explorer and see which process is taking up the CPU time. Once you know which one it is, go to the properties of that process and look at the threads tab to get a better idea of which thread in the process is using the CPU time. This information will help us better help you fix this.

I think the thinking behind this was, if you need more than 99 users on a system, you need a TERMINAL SERVER, not a desktop .

Have you tried safe mode w/ networking, to see if the same behavior occurs there?

Well, not to be mean, but yes - you could search google and find your answer too .

It can work, but most home networking gear is a crapshoot (and that is why businesses buy business-class wireless devices from vendors like Cisco). Take a look at the results and see if you want to try this with two routers, or if you just wish to purchase an extender device if the range you want to roam on isn't large.

It's telling you the "Help and Support" service isn't running - click start > run and type in services.msc , then click OK. This will open the services applet, and you should find a service in the list called "Help and Support" - that service needs to be running for the Help and Support functionality of XP to work properly.