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.




Network Security Nessus-Users
[Top] [All Lists]

Re: cannot connect to server

Subject: Re: cannot connect to server
Date: Fri, 28 Oct 2005 20:12:31 -0400
On Fri, Oct 28, 2005 at 01:53:43PM -0600, Anna Zapata wrote:

Nessus Console [Version 1.4.5] Ready
SSL library initialized
Connecting to server 172.16.5.15 (port 1241) using TLSv1 encrypted 
connection...
ERROR: Cannot establish connection with 172.16.5.15 (Socket error 1813)

Nessus is running on Red Hat 9.0.  I've tried a reboot.  I've tried nessusd 
-D and all it does is load the plugins.

It was running fine a few weeks ago, but no longer.  I try to connect via the 
NessusWX client as well as on the server.  No go.

I don't know what error 1813 means in the Winsock API, but here are some
questions that might help pinpoint the source of your particular problem:

  - Is nessusd still running?

  - Is nessusd listening on port 1241 on an interface reachable
    via client? That is, are you running it as something like
    "nessusd -a 127.0.0.1"?

  - Is either tcp_wrappers or a firewall blocking access to
    nessusd?

  - Is nessusd configured to use TLS? In other words, is
    there a line in nessusd.conf that says something like
    "ssl_version = NONE"?

  - Can you connect successfully using NessusWX on a
    different machine? What about using a different
    client entirely such as the unix client on the same
    host as nessusd itself?

  - Are there any interesting errors logged in either the
    system's messages or nessusd.messages log files?

George
-- 
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>