On Tue, 21 Aug 2001, Jason Majors wrote:
> I have four machines: a firewall, an internal server, and two workstations.
> When I try an SSH connection from the firewall to the server, or from outside
> the firewall using its port forwarding to go to the server, I get the error:
> ssh_exchange_ident
on Tue, Aug 21, 2001 at 01:43:20PM -0700, Jason Majors ([EMAIL PROTECTED])
wrote:
> On Tue, Aug 21, 2001 at 02:37:00PM -0500, Nathan Poznick wrote:
> > On Tue, Aug 21, 2001 at 11:02:51AM -0700, Jason Majors wrote:
> > > No. I don't think the firewall is the problem. I have problems connecting
> >
On Tue, Aug 21, 2001 at 05:30:20PM -0400, dman wrote:
> On Tue, Aug 21, 2001 at 01:57:40PM -0700, Jason Majors wrote:
> | The box I'm trying to connect from is 192.168.1.1.
> | And I don't think these files affect sshd. On the firewall I have
> ALL:PARANOID
> | for hosts.deny and nothing in hosts.
On Tue, Aug 21, 2001 at 01:57:40PM -0700, Jason Majors wrote:
| The box I'm trying to connect from is 192.168.1.1.
| And I don't think these files affect sshd. On the firewall I have ALL:PARANOID
| for hosts.deny and nothing in hosts.allow,
That means you are denying all incoming access to the sy
The box I'm trying to connect from is 192.168.1.1.
And I don't think these files affect sshd. On the firewall I have ALL:PARANOID
for hosts.deny and nothing in hosts.allow, and I'm running mutt on that box
right now through SSH.
On Tue, Aug 21, 2001 at 03:51:43PM -0500, Nathan Poznick wrote:
> On
I don't have that in there. In hosts.deny it's ALL:ALL, and in hosts.allow it's
ALL: 192.168.1.*.
On Tue, Aug 21, 2001 at 02:37:00PM -0500, Nathan Poznick wrote:
> On Tue, Aug 21, 2001 at 11:02:51AM -0700, Jason Majors wrote:
> > No. I don't think the firewall is the problem. I have problems conne
I've been reading the sshd thread and thought I'd run the verbose output
mentioned there:
OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090601f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Seeding random number generator
debug1: Rhosts Authentication disabled, originating port
No. I don't think the firewall is the problem. I have problems connecting
through that box as well as from that box. It's not a firewall appliance, it's
a Potato/Woody box running ipchains and ipmasq.
On Tue, Aug 21, 2001 at 01:57:00PM -0400, Wes Byne wrote:
> If your firewall is like mine (linksy
If your firewall is like mine (linksys) then it messes up the connection when
the daemon forks if it attaches to a privileged port (< 1023). Try using ssh
-P hostname to get the daemon to go to a non-privileged port behind the
firewall.
-Wes
On Tue, Aug 21, 2001 at 10:16:12AM -0700, Jason Ma
I have four machines: a firewall, an internal server, and two workstations.
When I try an SSH connection from the firewall to the server, or from outside
the firewall using its port forwarding to go to the server, I get the error:
ssh_exchange_identification: Connection closed by remote host
I can
10 matches
Mail list logo