Confucious say...Never trust a network admin, followed by beligerant
Turns out the end point had lock down their firewall to the point of
allowing clients in by source IP. Since over the weekend, when I
installed m0n0wall, our NAT "overload" IP changed, which prevented us
from getting in.
Apparently, they were getting hit with a lot of brute-force attacks.
On Thu, 31 Mar 2005 13:11:31 -0500, Chris Buechler <cbuechler at gmail dot com> wrote:
> No problem. Sorry I couldn't get back to you sooner. The entry you
> posted from status.php shows that the state to the remote server was
> indeed successfully created.
> The way I would test it, for future reference, is to telnet to port 22
> (SSH) on the server IP and see if it answers. For example, when I try
> this to one of my servers from a Windows system at the command prompt:
> C:\>telnet 188.8.131.52 22
> SSH-2.0-OpenSSH_3.5p1 FreeBSD-20030924
> Protocol mismatch.
> Connection to host lost.
> If you hit enter a couple times after the initial SSH banner, it'll
> say protocol mismatch and drop the connection. That verifies that you
> have basic network connectivity.
> On Thu, 31 Mar 2005 10:01:46 -0500, Don Munyak <don dot munyak at gmail dot com> wrote:
> > Hold off on anything.
> > Looks like there may be a problem at the remote server, eventhough we
> > were originally told otherwise.
> > sorry to have bothered you.
> > -Don
> > ---------- Forwarded message ----------
> > From: Don Munyak <don dot munyak at gmail dot com>
> > Date: Thu, 31 Mar 2005 08:35:32 -0500
> > Subject: m0n0wall Outbound Secure Shell problem
> > To: Chris Buechler <cbuechler at gmail dot com>
> > re: Outbound Secure Shell problem
> > Hey Chris,
> > I posted a questions on the list server. Please forgive me if I'm
> > bugging you...but. I honestly have been trying for two days to figure
> > this out before emailing you.
> > Do you have any suggestions I might want to take to make ssh work from
> > a lan client to a wan side ssh server ?
> > Thanks,
> > - Don