"Loading Security Policy" < How do I get rid of this?

[ivanhasou]

I have windows 2000 running computer which starts up very slowly because it has to load a security policy. Is there anyway to get rid of that, so that it would startup faster? a reinstall of windows is not an option tho

[res0r9lm]

I haven't used windows in a long time but don't think getting rid of security is a good idea. I would think that it's got a problem with the policy where somethings are contradicting each other and needs to be redifined

[ivanhasou]

well, how can i get to the windows 2000 default settings, because this used to not appear at all and the startup was faster

[primesuspect]

Was it ever joined to an Active Directory domain? Because generally only members of domains have security policies... At the login screen do you have three boxes of information -- Username, Password, and Domain? Or just two...?

[profdlp]

prime - I'd bet you called it. Correct me if I'm wrong, but aren't most security policies usually stored on the server? (To make it easy for an administrator to make changes to all computers quickly.)

ivanhasou's delay might be from having to wait through the extra timeout while it searches for the network share with the security policy, (which isn't there).

[Leonardo]

I think it only has to do with domain security policies, as stated above. It shouldn't affect a LAN in a workgroup setup. See if "Security Policy" or an activity of similar wording is located in services. Then check for "dependancies".

[Straight_Man]

2000, if told to log into a LAN domain, will be hyperslow if no server (Domain type, as prime said) exists. When you setup an internent connection, with a proxy software to sahre internet, that proxy plays as "server" for some foms of Windows. So, is there any proxy software in use to shere internet??? Say, software for a Windows 98 box to share internet through a modem on a 2000 box???

Either internet was misconfigured, the box was lonce truely on a domain, or somehow 2000 tried to set up a "virtual" domain to get along with proxying software for another box-- possibly one hooked up by a direct-connect box-to-box data transfer cable.

OH, two other things can do this-- both AV and firewalls can setup looping internal to a box,. serving as pseudoproxies. Removing such without fixing the networking afterwards can leave a box trying to use a pseudoproxy it cannot log in to or through, on same box, and on a single box that was never on a LAN. If this applies, get rid of the pseudodomain. Technically, I have seen viruses create the appearance of this situation also, and that WAS on 2000. BUT, killing viruses got rid of problems-- in some case, network setup then had to be redefined also.

More info, please, thread starter. :D

John D.

[Leonardo]

John, would that proxy server also be considered a shared drive on LAN-workgroup?