Problem after SSH/SSL upgrade

From: Ifan Jones (ifan_at_draig.co.uk)
Date: 07/16/03

  • Next message: Ed J. Aivazian: "Re: Allow logins by username" 
    Date: Wed, 16 Jul 2003 12:35:05 +0100
To: <secureshell@securityfocus.com>

    Looking for a quick fix..........

    I've recently updated all my clients VPN's to OpenSSH 3.6.1p2 and OpenSSL0.9.7b.

    All the upgrades went fine except for one. The VPN connection starts just fine and logs in passwordless as expected - connection stays up for varying times, when it drops, the message on the client side is 'connection reset by peer' I can restart the connection no problem...

    I also have a ping command in the crontab which sends the results to me via email in a vain attempt to keep the connection active....

    I can no longer log in remotely to the SSH server (even though it's running) but local login is fine. This doesn't really matter as I start the connection from the client which allows me to connect remotely. Both machines are on Mandrake 8.2

    SCP has also stopped working - can't copy anything either way accross the machines. Which meant I had to use a floppy and my car to get the public keys sorted!

    Anyone have a few pointers of where I should start looking?

    Regards

    Ifan

  • Next message: Ed J. Aivazian: "Re: Allow logins by username"

    Relevant Pages

    • working with XP network
      ... >creating the gateway. ... >machines into it, and verify that you have a LAN. ... >You can configure your clients to use static IP ... >connection in the same IP ...
      (microsoft.public.windowsxp.network_web)
    • Windows 98 to 2003 terminal server problem
      ... I have just installed a 2003 Terminal Server and all clients connect except ... the 4 Windows 98 machines. ... the connection is done via the local network, ...
      (microsoft.public.win2000.termserv.clients)
    • Windows 98 connecting to 2003 Terminal Server
      ... I have just installed a 2003 Terminal Server and all clients connect except ... the 4 Windows 98 machines. ... the connection is done via the local network, ...
      (microsoft.public.windows.server.networking)
    • Windows 98 connecting to 2003 terminal server problem
      ... I have just installed a 2003 Terminal Server and all clients connect except ... the 4 Windows 98 machines. ... the connection is done via the local network, ...
      (microsoft.public.windows.server.general)
    • Re: Connecting Out of Process Servers via COM+
      ... connection, and in fact we can only use one connection because of the way ... years ago when I needed a number of clients to share a single serial ... it would create a Dispatcher-Object first and registers ... > This means, altough COM+ would allow parallel requests, the calls would be ...
      (microsoft.public.vb.com)