All of lore.kernel.org
 help / color / mirror / Atom feed
From: "teddymills" <teddymills@knet.ca>
To: Darryl On Linux <1stflight@ameritech.net>, linux-admin@vger.kernel.org
Subject: Re: SSH connecting at the wrong port?
Date: Thu, 31 Jul 2003 10:17:58 -0400	[thread overview]
Message-ID: <002401c3576e$8cc18e20$76cebfd8@ncct.on.ca> (raw)
In-Reply-To: 200307301810.07412.1stflight@ameritech.net

try
ssh -v -v   x.x.x.x







----- Original Message -----
From: "Darryl On Linux" <1stflight@ameritech.net>
To: <linux-admin@vger.kernel.org>
Sent: Wednesday, July 30, 2003 6:10 PM
Subject: SSH connecting at the wrong port?


> I connected from work to my server using ssh (ssh2, once), using Putty.
> However I see that the ssh ports I connect to aren't 22, what's going on
> here?
>
> P.S.  Servernames,  IP's and dates, changed, ports and other information
not
> changed.
>
> Jul 29 14:14:56 Servername sshd[30302]: Accepted password for me from
1.1.1.1
> port 56182 ssh2
> Jul 29 14:20:11 Servername sshd[30638]: Accepted password for me from
1.1.1.1
> port 62144
> Jul 29 14:20:56 Servername sshd[30693]: Accepted password for me from
1.1.1.1
> port 62687
> Jul 29 15:48:47 Servername sshd[3051]: Accepted password for me from
1.1.1.1
> port 50979
> Jul 29 15:49:05 Servername sshd[3079]: Accepted password for me from
1.1.1.1
> port 51287
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


      parent reply	other threads:[~2003-07-31 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 22:10 SSH connecting at the wrong port? Darryl On Linux
2003-07-30 22:15 ` Mike Dresser
2003-07-30 22:23 ` Matt Hemingway
2003-07-31 14:17 ` teddymills [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002401c3576e$8cc18e20$76cebfd8@ncct.on.ca' \
    --to=teddymills@knet.ca \
    --cc=1stflight@ameritech.net \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.