Thanks, this pointed me in the right direction and saved me a lot of time.
Mike
Steven A. Fletcher wrote:
It sounds to me like you are running into a problem with the ForceGuest default setting on Windows XP. Are the machines in a Windows domain? If they are not, this is likely the problem.
By default, WinXP will authenticate a user who connects to the machine over the network as guest, even if you provide a username and password. More details can be found here: http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/e n-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-u s/prde_ffs_ypuh.asp.
Hope this helps.
Steve Fletcher Senior Network Engineer, MCSE, Master ASE, CCNA Integrity Technology Solutions Phone: (309)664-8129 Toll Free: (888) 764-8100 ext. 129 Fax: (309) 662-6421 [EMAIL PROTECTED]
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Gadoury Sent: Thursday, April 22, 2004 2:10 PM To: nessus List (E-mail) Subject: Scanning Window XP Question?
I am trying to scan a group of Windows machines and I'm getting mixed results.
I followed the directions given in the "Nessus Scanning on Windows Domain" pdf file. When I scan a Windows 2000 Client Nessus works as expected. I get access to the Registry and Nessus is able to read the keys of interest.
However when the same test/scan is performed against Windows XP, the scan fails to read any information from the Registry.
My questions is: Do I need to do anything special for XP in order to be able to read from the Registry? What about 98, and 95 and ME?
Thanks for any help!
Mike
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
