+ Reply to Thread
Results 1 to 10 of 10
Thread: error connecting to network
August 6th, 2003, 10:00 PM #1
error connecting to network
I'm getting an interesting error after leaving an XP PC attached to the network unattended for an extended time. When coming back and trying to access a network drive, I get: "The system detected a possible attempt to compromise security."
Logging off and logging back on cures this but I don't know how to make it not happen.
Last edited by MTAtech; August 7th, 2003 at 08:10 AM.
August 6th, 2003, 10:05 PM #2
August 7th, 2003, 08:04 AM #3
It's a domain.Conservatives: "If the facts disagree with our opinion, ignore the facts -- or at least misrepresent them."
August 7th, 2003, 08:15 AM #4
If this is a school domain they may have a policy enforced where if a pc is inactive for a predetermined amount of time, you get dropped. So when you try to use your pc again, it doesn't see you as being logged on anymore. Does this happen to anyone else?
August 7th, 2003, 08:17 AM #5
This is in my own home. I have Windows 2003 Server as the server and a few PCs and a Mac on the network. I have administrative rights.
The PC is left on. It was able to access network drives when initially logged on. After a number of hours one can't access the shared network drives and the above error is returned. Internet is uneffected.
This seems not to be only me having this problem:
Last edited by MTAtech; August 7th, 2003 at 08:21 AM.Conservatives: "If the facts disagree with our opinion, ignore the facts -- or at least misrepresent them."
August 7th, 2003, 08:44 AM #6
- Join Date
- Oct 2001
August 7th, 2003, 08:49 AM #7
August 7th, 2003, 08:51 AM #8
I tried it tonight. So far, no problems.
Interesting that there is no mention of this in the Microsoft knowledgebase.
Last edited by MTAtech; August 7th, 2003 at 09:11 PM.Conservatives: "If the facts disagree with our opinion, ignore the facts -- or at least misrepresent them."
August 10th, 2003, 07:28 AM #9
Well, that didn't work. Problem reappeared the next morning
March 19th, 2004, 01:12 PM #10
- Join Date
- Mar 2004
The problem could be due to your network having a DHCP server configured to use DNS servers outside of your network. If you have a broadband router acting as the DHCP server then make sure the DNS server(s) in the DHCP scope only contain internal ip address of your router (assuming it has the DNS proxy facility).
If not just set up the server to do DNS and DHCP and that should fix it.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)