Hi Paula,
I started reading about the issue you are having. A user has reported behavior
like this before.
Please try to see log files of openvas to see what went wrong with the login
exactly.
There's a few general remarks on the preparation of your target:
http://www.openvas.org/compendium/preparing-the-microsoft-windows-target.htmlYou
need the Windows credentials for an administrative user. Usually this is the
user name (Default is "Administrator") and the correct password for this user.
There is no default password, this has been defined before during the Windows
installation process.These credentials are entered in the OpenVAS-Client GUI as
SMB Credentials and are used on every host in the target list.If you plan to
scan a whole Windows Domain, you can enter the Domain-Administrative user and
password instead of the target host credentials.Make sure the
Windows-(personal) Firewall is disabled for the OpenVAS Server host, or a
correct rule for the Test-Network is entered.
Also you could try an Nmap scan to see if port 445 (SMB) is listening.
Last but not least, try to use an auxiliary module for SMB in msfconsole to see
if GSAD or the target is the problem:
msf > use auxiliary/scanner/smb/smb_loginmsf auxiliary(smb_login) > set SMBUser
<ABCD>msf auxiliary(smb_login) > set SMBPass <EFGH>msf auxiliary(smb_login) >
exploit
Best regards,Jelmer
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
