O.K., all problems solved! I had another talk with
our sys admin. and he had forgotten to "open" up port
22 on another machine (somehow we have 2 machines
controlling the firewall, which I don't quite understand,
but no matter). Now that he has done that, I can ssh to
machine C with no problem (I'm sending this email from
machine C via machine A right now)!
Thanks for your help,
Tom
On Fri, 14 Jul 2000, [EMAIL PROTECTED] wrote:
>
>
> On Wed, 12 Jul 2000, [EMAIL PROTECTED] wrote:
>
> > > If you have no admin access on C, you're kind of hosed unless you can get
> > > an opening in the firewall. You would have to get access to a machine
> > > D outside the firewall where you could SSH to using one of the above
> > > methods, and then SSH from D to C.
> >
> > I think I am hosed, and will have to come up for a legitimate case
> > for having our sys. admin. "open" up or "listen" on port 22 of the
> > firewall. If I could only find a site related to chip design that requires
> > me to login via ssh, I could go to my manager and make a business case,
> > otherwise I'm hosed.
> >
>
> O.K., I had a talk with our sys admin, and he agreed that we could
> "open" up port 22 on the firewall (I convinced him that SSH is more
> secure than telnet or ftp, which are both "open" ports on our
> firewall). However, I'm still having problems, as evidenced below:
>
> $ ssh -v Remote-User-Name@Remote-Machine
> SSH Version OpenSSH-1.2.2, protocol version 1.5.
> Compiled with SSL.
> debug: Reading configuration data /etc/ssh/ssh_config
> debug: Applying options for *
> debug: ssh_connect: getuid xxx geteuid 0 anon 0
> debug: Connecting to Remote-Machine [xxx.xxx.xxx.xxx] port 22.
> debug: Allocated local port 959.
> debug: Connection established.
> ssh_exchange_identification: read: Connection reset by peer
> debug: Calling cleanup 0x8058908(0x0)
>
> I'm getting closer now, as it seems a connection is now being
> established with the remote box (C from my earlier posts),
> however, it's immediately shutting down the connection. Is
> there still something more that has to be done on the firewall?
>
> Thanks,
> Tom
>
>
>