I figured it should work myself and within the network the client connects without a hitch, actually I figured I would be able to connect to the server directly without a problem through the VPN. Is there some type of nessus access control that prevents the client from connecting to the server on a different subnet?
On Fri, Oct 10, 2008 at 1:54 PM, Sat Jagat Singh <[EMAIL PROTECTED]> wrote: > If ssh is working across the vpn connection, then the port forwarding should > work. Putty is o.k. for this. I have made that work. I generally prefer > the cli ssh client available through the cygwin distribution. For my way of > thinking it is easier to remember the setup because the syntax is identical > to other implementations; e.g. linux. Putty has so many configuration tabs > to go through to set this up that it can be confusing. > > --- On Thu, 10/9/08, Stephen Reese <[EMAIL PROTECTED]> wrote: > > From: Stephen Reese <[EMAIL PROTECTED]> > Subject: Re: Tunnel Nessus client over ssh > To: [EMAIL PROTECTED], [email protected] > Date: Thursday, October 9, 2008, 4:39 PM > >> Are you doing > ssh like this: >> >> ssh -Nf <remote_host> -L1241:localhost:1241 >> >> Then point your Nessus client at localhost 1241. You will probably be >> prompted about the SSL certificate having changed or being for a new host >> and asking you whether you want to accept the certificate. Then it just >> works. I do it all the time. > > I was trying to connect via Microsoft XP box with a Cisco VPN client. > Then using Putty to ssh to the server running the Nessus daemon. I can > ssh without a problem but my port forwarding must be off because I > have yet to be able to make a connection. > > _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
