dfreitus
asked on
An Attempt to Compromise Security has been Detected
Domain Controller runs windows server 2003 ent
All computers run Win XP Pro
Sometimes when i try to connect to a shared network resource via a workstation, i get "An attempt to compromise security has been detected" and i cant access the resource. This happened so far when I have tried to access some shared music, it will cut out randomly and display that message (the songs are on the DC) and recently i tried to install a network printer on a workstation and i got the same message. Also I get error messages occasionally about not being able to local the domain controller, but eveything appears to work fine with the exception of those two things. the dc is also the dns server and users can login without problems, so there is communication........
All computers run Win XP Pro
Sometimes when i try to connect to a shared network resource via a workstation, i get "An attempt to compromise security has been detected" and i cant access the resource. This happened so far when I have tried to access some shared music, it will cut out randomly and display that message (the songs are on the DC) and recently i tried to install a network printer on a workstation and i got the same message. Also I get error messages occasionally about not being able to local the domain controller, but eveything appears to work fine with the exception of those two things. the dc is also the dns server and users can login without problems, so there is communication........
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Found the problem... it is indeed a DNS error!!!
Your domain server should be set to a static IP address.
Use this address as your primary DNS for each workstation. If you have a network that is configured DHCP, you can add the DNS entry to your DHCP server or router.
Use a public DNS as your secondary DNS so that you can access any workstations remotely if needed. 4.2.2.1 works as a secondary public address. This will also help (god forbid!) if your server goes down. Your workstations will still have internet access by reverting to their secondary DNS entry.
Your domain server should be set to a static IP address.
Use this address as your primary DNS for each workstation. If you have a network that is configured DHCP, you can add the DNS entry to your DHCP server or router.
Use a public DNS as your secondary DNS so that you can access any workstations remotely if needed. 4.2.2.1 works as a secondary public address. This will also help (god forbid!) if your server goes down. Your workstations will still have internet access by reverting to their secondary DNS entry.
Thanks,
Brian Weiss