Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Nessus N00b question |
|---|---|
| Date: | Mon, 14 Apr 2008 16:10:05 -0400 |
OK, I'm new to Nessus and I want to use it to supplement my use of eRetina.
I installed Nessus on my local machine (both server and client) and started
scanning MS machines with the three sections for Windows plugins selected.
However all my attempts at scanning show limited access to the target
machine. The results show vulnerabilities per port, but doesn't no where
does it show the Microsoft patches I know are missing (ones that eRetina
does find).
I configured the scan policy to use an account with domain admin privileges,
but I cannot get registry access. I tried using the local machine admin
account (username: machinename\admin-name), but either I entered it wrong or
it can't get registry access either via Nessus.
The Nessus report has these entries:
Local Checks Failed
Synopsis :
It was not possible to log into the remote host
Description :
The credentials provided for the scan did not allow us to
log into the
remote host.
Also:
SMB log in
Synopsis :
It is possible to log into the remote host.
Description :
The remote host is running one of the Microsoft Windows
operating
systems. It was possible to log into it using one of the
following
account :
- NULL session
- Guest account
- Given Credentials
And:
Synopsis :
Nessus is not able to access the remote Windows Registry.
Description :
It was not possible to connect to PIPE\winreg on the remote
host.
If you intend to use Nessus to perform registry-based
checks, the
registry checks will not work because the 'Remote Registry
Access'
service (winreg) has been disabled on the remote host or can
not be
connected to with the supplied credentials.
I checked my sanity by opening up regedit and confirming I could open the
remote registry using the domain admin credentials. When I use eRetina,
using the domain account or the local admin account, it scans the registry
with no problems.
I reviewed the manual and searched the archives. I found the following
discussion which seems to mirror the issue I'm having:
http://mail.nessus.org/mailman/htdig/nessus/2003-October/007431.html, but
this solution didn't work for me.
Any suggestions or am I just missing something and Nessus is functioning
correctly?
Thanks for any help.
reswob
-------------------------------
Motivation is what gets you started, habit is what keeps you going. - Jim
Ryun
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Administrator and Guest Accounts, Adam Campbell |
|---|---|
| Next by Date: | Plug-in ID 10934, Mark A Timm |
| Previous by Thread: | Re: Host identification b/w workstation and server( or internet facing system), Chak Kevin |
| Next by Thread: | Plug-in ID 10934, Mark A Timm |
| Indexes: | [Date] [Thread] [Top] [All Lists] |