XP and sucking chest wounds. OK, maybe just sucking.

[Mercutio]

"The system detected a possible attempt to compromise security. Please
ensure that you can contact the server that authenticated you"

XP SP1a. Windows 2000 Server.

This machine is just like every other XP computer in the building. Gets all info from the same DHCP server. It authenticates just fine.

It's just that it throws this error when I try to access (or map) shared resources.

I've done ipconfig /flushdns, release & renew, pinged my server, repaired my network connection, even logged in to Exchange and OWA on the stupid thing.

The machine account is enabled and not locked out. Nor are the user accounts I've tried.

Has anyone run into this one before???

 

[Buck]

Although I don't have an answer, as clarification, is this with Windows XP Professional or Home?

 

[Mercutio]

Pro. The bit about accounts being locked and enabled and stuff would be the tip in this case.

 

[Fushigi]

Never seen it before. Is the XP Firewall enabled? Anything in Event Viewer?

 

[Buck]

Does this occur when logged in as Administrator?

 

[Mercutio]

Yup.

 

[Mercutio]

Event Viewer brings up that same error message and there's a bunch of crap its printer (lexmark POS) threw in there (in the system log, go figure) but everything else looks normal.

 

[Buck]

Have you removed and recreated your network connection?

 

[blakerwry]

you could try reinstalling TCP/IP..

At the command prompt type:
netsh int ip reset c:\log.txt


and reinstall the NIC... making sure that the apropriate client for MSN is enabled and that unnecessary things are disabled... all you should need is client for MSN and TCP/IP to access windows shares... also, i'd make sure that the firewall is disabled...

 

[blakerwry]

oh.. forgot to mention.. XP's firewall is poopy... I've had it enabled on one adapter and not on another, just to find out in reality it was enabled on both connections dispite what the GUI said... so better yet, just disable the IPSec service altogether...

 

[Mercutio]

Reinstalling TCP/IP didn't fix it, but doing an SFC seems to have done it.

I really despise the fact that I have no idea what happened or how it was fixed.

 

[blakerwry]

yeah, it didn't really sound like a TCP problem as you said you could ping, authenticate and such... but it was my best guess short of doing a restore/repair on the OS... i somehow always forget about the system file checking tool

 

[Howell]

Reinstalling TCP/IP didn't fix it, but doing an SFC seems to have done it.

I really despise the fact that I have no idea what happened or how it was fixed.

No report?!

 

[mubs]

I've heard of several goofy problems that mysteriously disapper when you do an SFC, even though SFC has nothing to do with the problem. Who knows how the beast's nevous system is wired.

 

[Mercutio]

No report?!

Not for SFC. It just asks for a CD and tells you to reboot when its done. I don't even think it puts anything in the event logs.

 

[blakerwry]

merc, i have a crappy XP home SP1 problem...

fairly new install of XP.. when I'm trying to browse networks shares it's ungodly slow.

This happens when browsing shares from samba, winXP pro, or even from the local host... The problem is that I can see the workgroup, I can see the shares on a server, login(if needed) is quick and speedy, but when I go to open a share it stalls for about 3-5 minutes and the explorer/my computer window effectively is frozen for that time period.

while that's working or after it's done I can usually immediately open up another explorer window and then freely browse to the share fine... upon reboot I get the same thing...

These shares all work fine from my XP pro box.


i've followed the instructions here, but i think this is a fix for bringing up a slow share list... my problem is I can open the list, but then can't open the shares like I should be able to...

I have tried repairing the connection, running the SFC, reinstalling the NIC and TCP/IP.. all to no avail.

any ideas?

 

[mangyDOG]

I have had exactly this problem. To fix it, I set up the Win2k server to be running a dns server and made sure the winXP box has the ip address of the server as its primary dns server...

(at least it worked for me when I did that)


Cheers,
mangyDOG

 

[blakerwry]

thanks mangyDog, i had forgoten that i posted this here ;-)

What fixed the problem was to disable the webclient service that is automatically running on XP boxes.


Your problem actually sounds like a name resolution problem that would make it slow to bring up the list of shares and/or login to the computer. (both of these operations worked fine for me)

If you want a less resource intensive fix you could probably disable the DNS server and use the HOSTS file instead... or map a fixed network drive using the IP address of the computer instead of the name.