Hi It works,
First you will give root a Password.
Second you have to generate some hostkeys for the transport.
Last you have to put your Network in the Hosts.allow
After that putty will work as expected.
To get winscp to work you need some more
Install ncurses and probably bash
That's it
Helfrie
--On Monday, March 03, 2003 04:57:24 PM -0800 Ray Olszewski
<[EMAIL PROTECTED]> wrote:
At 04:41 PM 3/3/2003 -0800, Tom Eastep wrote:
iptables can generate an RST response as well which is what Shorewall
has it generate in response to a REJECTed TCP connection request.
Thanks, Tom. I'd missed
At 04:41 PM 3/3/2003 -0800, Tom Eastep wrote:
--On Monday, March 03, 2003 12:59:51 PM -0800 Ray Olszewski
<[EMAIL PROTECTED]> wrote:
That is the putty message you get when there is no server running on the
target host. I don't know (and cannot readily test) if it is also the
message you get in
--On Monday, March 03, 2003 12:59:51 PM -0800 Ray Olszewski
<[EMAIL PROTECTED]> wrote:
That is the putty message you get when there is no server running on the
target host. I don't know (and cannot readily test) if it is also the
message you get in response to an icmp reject (the kind of REJECT
Try this link for a start.
http://home.attbi.com/~srlohman/linux/firewall/es-remoteacc.html
His putty instructions worked but his sshd instructions did not.
I am using Dachstein CD 1.0.1 and connect from one windows machine on
the LAN to the LRP box.
To get sshd to work I had to load sshd.lrp,
At 03:05 PM 3/3/2003 -0500, [EMAIL PROTECTED] wrote:
Hi,
i trying to get the following situation to work:
Windows pc with Putty connecting to Bering Firewall.
When i make the connection via Putty i get the following reply:
* Network error. Connection Refused.
I have read the online Bering Openssh
