[isalist] Re: Publishing a SSH Server (The solution)
- From: "Thomas W Shinder" <tshinder@xxxxxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Wed, 10 May 2006 08:36:46 -0500
Hi Wilmar,
They didn't provide any information on why this would be required? I
have to say that it doesn't make any sense at all!
Thanks!
Tom
Thomas W Shinder, M.D.
Site: www.isaserver.org <http://www.isaserver.org/>
Blog: http://blogs.isaserver.org/shinder/
Book: http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7>
MVP -- ISA Firewalls
________________________________
From: isalist-bounce@xxxxxxxxxxxxx
[mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Wilmar Perez
Sent: Wednesday, May 10, 2006 8:22 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Publishing a SSH Server (The solution)
Hello everybody
Well, I don't know how many of you remember this thread but I
said I will tell everybody the solution once it were found. There it
goes: according to Microsoft what I needed to do was to create a route
relationship between the internal SSH server and the External Network
even if I already have a NAT relationship between the DMZ, where the
internal SSH server is located, and the External Network.
As weird as it seems (at least it is weird for me), it works.
And that was all I needed to do. It would be nice to hear an
explanation of someone who actually understand how it manages to work
that way.
Thanks a lot to all those who helped me to find out an answer to
this problem.
Regards
Wilmar Perez
Other related posts:
