That support search engine must have missed it :)


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman
Sent: Thursday, May 27, 2004 4:04 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] strange error on logon

Have you seen:

 

824204 You receive an "Error at logon: Cannot find the file..." error message

http://support.microsoft.com/?id=824204

 

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al
Sent: Thursday, May 27, 2004 2:51 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] strange error on logon

 

Just a guess.

 

Check the registry on the workstation.  That file error throws some hits on the net referring to shell startup.

This maybe the key.  You can search the registry and find a reference to the idlist portion of your error.  I wouldn't rule out GPO just yet either as it could be something that got locked down inadvertently.  Or maybe folder redirection?  Seen some reference to Norton, but...

 

HKCR\Folder\shell\rootexplore = "Explore From Here"
  command = "Explorer.exe /e,/root,/idlist,%I"

 


 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Thursday, May 27, 2004 3:20 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] strange error on logon

I have never seen an error like that so once you nail down what is running that is throwing the error up, then we can go from there.

 

   joe

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raymond McClinnis
Sent: Thursday, May 27, 2004 12:41 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] strange error on logon

I began receiving calls yesterday about a strange looking error that users were getting at logon.  Here is the message:

 

Cannot find the file '/idlist,:0:1140,\\DOMAINCONTROLLER\NETLOGON' (or one of its components).

 

I originally thought that it may be an issue with a script I was pushing through group policy, but that is not the case.  I still need to look at the startup on the machines in question and see if there is anything there.

 

Thanks,

Raymond McClinnis

Reply via email to