Is a firewall employed on either end of the system? Is the firewall
allowing port 22 connections?
regards,
Robert
On Wed, 24 Nov 2004 09:56:10 -0800
Chuk Goodin <[EMAIL PROTECTED]> wrote:
> > >http://www.linuxquestions.org/questions/showthread.php?s=&threadid
> > >=248641
> > >
> > >
> > >>Does
On Wed, 24 Nov 2004 09:56:10 -0800, Chuk Goodin <[EMAIL PROTECTED]> wrote:
> > What have you got that connects you to the Internet? A DSL router? If
> > so, have you configured port forwarding?
Yes, a DSL router. Yes, it should be forwarding to this machine (I've
also tried it with no router.)
-
> >http://www.linuxquestions.org/questions/showthread.php?s=&threadid=248641
> >
> >
> >>Does anyone have any suggestions about things I
> >>might have overlooked?
> >>Attempts to connect just timeout with no response.
> >#nmap [external_ip]
PORT STATE SERVICE
22/tcp open ssh
> >you can se
Sergio Basurto Juarez wrote:
--- Chuk Goodin <[EMAIL PROTECTED]> wrote:
I'm running mostly Woody with some Sarge updates,
and I can't seem to
SSH in to my machine from offsite. I can do it on
the LAN, so I know
sshd is running and working, and I can't do it when
I hook my Linux
box straight into
On 11/19/2004 07:00 PM, Chuk Goodin wrote:
I'm running mostly Woody with some Sarge updates, and I can't seem to
SSH in to my machine from offsite.
Click here to have your port 22 probed:
http://www.grc.com/port_22.htm
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
> I've asked other people on my ISP if their port 22 is being blocked,
> and I've also tried running sshd on port 60.
I would recommend talking to your ISP. I ran into a similar problem a
while back when my ISP moved me from a publicly accessible IP pool to
a firewalled IP pool. A quick email cl
--- Chuk Goodin <[EMAIL PROTECTED]> wrote:
> I'm running mostly Woody with some Sarge updates,
> and I can't seem to
> SSH in to my machine from offsite. I can do it on
> the LAN, so I know
> sshd is running and working, and I can't do it when
> I hook my Linux
> box straight into our DSL line, s
On Sat, 14 Aug 2004 17:56:35 -0500, Kent West <[EMAIL PROTECTED]> wrote:
> John Fleming wrote:
>
> >Since yesterday I can't ssh in to my Debian unstable box, fully upgraded.
> >When using Putty, as soon as the terminal window opens, it immediately
> >closes. This is true whether from another mach
How can you log in? Can you log in locally? Are you using IMAP and
POP with the same user?
What I am getting at is have you confirmed /etc/passwd, ~/bashrc, and
~/.bash_profile are correct? I had a similar problem when my shell in
/etc/passwd was /sbin/bassh. I have never used Putty so I do
John Fleming wrote:
Since yesterday I can't ssh in to my Debian unstable box, fully upgraded.
When using Putty, as soon as the terminal window opens, it immediately
closes. This is true whether from another machine on the LAN, or from a
more remote machine. I've checked with and without my Firest
FYI I solved it, and the solution was the same as that of the fellow in the
"ssh weirdness" thread. The problem was an ISP DNS issue. Namely, a
reverse lookup on my IP yielded a plausible name, but a forward lookup on
that name got nothing. This was causing the hosts.deny file to stop telnet
On Tue, Jul 10, 2001 at 10:47:41PM -0700, Owen G. Emry wrote:
> Yes, it's just got the default .deny and .allow files. Can't see anything
> wrong there. And all other services besides ssh and telnet seem to work
> fine. Very frustrating! Thanks for the suggestion, though.
What does "netstat
Yes, it's just got the default .deny and .allow files. Can't see anything
wrong there. And all other services besides ssh and telnet seem to work
fine. Very frustrating! Thanks for the suggestion, though.
-Owen
At 03:34 2001-07-11 -0300, Linuxero wrote:
> Some more information:
>
> Sinc
> Some more information:
>
> Since apache works perfectly, I stopped it and tried moving telnet to port
> 80. Still no connection. ssh didn't work over port 80, either, so I know
> it's not a firewall problem.
>
> After scouring the net, I read that sometimes having ipv6 enabled in the
> kernel w
Some more information:
Since apache works perfectly, I stopped it and tried moving telnet to port
80. Still no connection. ssh didn't work over port 80, either, so I know
it's not a firewall problem.
After scouring the net, I read that sometimes having ipv6 enabled in the
kernel will confu
As it turns out, the system wrote /etc/nologin and /etc/nologin.boot when I
rebooted the system (I didn't have to, but without console access, it was a
LOT easier that way).
It didn't remove them after startup, thus normal users couldn't log in.
Thanks for all the suggestions.
At 10:35 PM -0700 4
At 987701236s since epoch (04/19/01 06:27:16 -0400 UTC), Andre Berger wrote:
> * Deirdre Saoirse Moen <[EMAIL PROTECTED]>, 2001-04-19 09:53 +0200:
> >
> > (I'm still waiting for DNS to catch up with me...)
Perhaps that's your problem... do you have "ReverseMappingCheck" set to
"yes" in your /etc
> "Deirdre" == Deirdre Saoirse Moen <[EMAIL PROTECTED]> writes:
Deirdre> I rebooted my system today (probably after a few too many things
were
Deirdre> changed) and all of a sudden I can't ssh in as a normal user.
Deirdre> I've got a fairly minimal system, but it seems a strange
* Andre Berger <[EMAIL PROTECTED]>, 2001-04-19 12:43 +0200:
> * Deirdre Saoirse Moen <[EMAIL PROTECTED]>, 2001-04-19 09:53 +0200:
> > I rebooted my system today (probably after a few too many things were
> > changed) and all of a sudden I can't ssh in as a normal user.
> >
> > I've got a fairly mi
* Deirdre Saoirse Moen <[EMAIL PROTECTED]>, 2001-04-19 09:53 +0200:
> I rebooted my system today (probably after a few too many things were
> changed) and all of a sudden I can't ssh in as a normal user.
>
> I've got a fairly minimal system, but it seems a strange thing to break
> upon reboot. All
* Deirdre Saoirse Moen <[EMAIL PROTECTED]> [010419 00:27]:
> I rebooted my system today (probably after a few too many things were
> changed) and all of a sudden I can't ssh in as a normal user.
does this mean you *can* ssh as root? or does it mean you can't ssh in
at all?
> I've got a fairly mi
Please set your line length to 72 characters, without space padding.
on Thu, Mar 15, 2001 at 09:11:17PM -0500, Mark Livingstone ([EMAIL PROTECTED])
wrote:
> Hi!
>
> One of my boxes is running openssh_2.3.0 with only ssh2 enabled.. When
> i first installed Debian and ssh i could easily connect to
Torbjorn Pettersson <[EMAIL PROTECTED]> writes:
> It seems like there just was an update of the ssh package from
> the sequrity team, which supposedly fixes the problem.
>
It didn't... It was linked to some version of libcrypto which
wasn't on my machine
Regards
Tobbe
It seems like there just was an update of the ssh package from
the sequrity team, which supposedly fixes the problem.
Regards
--
##
Torbjörn Pettersson # Email [EMAIL PROTECTED]
Vattugatan 5
Hi,
little more info, I did manage to break something :)
my sparc boxes are clustered, so after doing the upgrade on the master
node (my last email) I did:
# for i in `members`;do ssh -f $i apt-get -qq -v upgrade;done
Three out of the eight remaining boxes choked (on glibc I think,
though might
Hi,
Now that I've secured my machines...
Sparcstation20 (sun4m Ross HyperSparc processor)
Setting up ssh (1.2.3-9.1) ...
Installing new version of config file /etc/ssh/sshd_config ...
Starting OpenBSD Secure Shell server: sshd.
The upgraded server is accepting both password and RSA authenticati
On Sat, Jan 20, 2001 at 11:41:33PM +0100, Torbjorn Pettersson wrote:
:
: When apt upgraded ssh from 1.2.3-8.0.1 to 1.2.3-9.1 for me it
:worked on the x86 boxen, but on all my sparcs, sun4m and sun4u,
:some using pam, and some don't, I got the same problem, that is
:I can't log in any more, and the
"Jonathan D. Proulx" <[EMAIL PROTECTED]> writes:
> On Fri, Jan 19, 2001 at 03:54:36PM +0100, Torbjorn Pettersson wrote:
>
> : Are the server a sparc? It seems that the ssh package from the
> :security team is broken on sparc, at least it doesn't work for me...
>
> I have ssh on 9 sparc 4m machin
What was the exact message you received?
Art Edwards
On Thu, Jan 18, 2001 at 12:42:49PM -0500, John F. Davis wrote:
> Hello
>
> I did a apt-get upgrade which restarted ssh and now I can't ssh into
> my box anymore. I keep getting a invalid password response.
>
> I can however login to the box v
On Fri, Jan 19, 2001 at 03:54:36PM +0100, Torbjorn Pettersson wrote:
: Are the server a sparc? It seems that the ssh package from the
:security team is broken on sparc, at least it doesn't work for me...
I have ssh on 9 sparc 4m machines working fine, can you be more
specific about the problem?
Hi,
don't have much light to shed on this but here's a few walls to bang
your head on:
/etc/hosts.{allow, deny}
/etc/ssh/sshd_config #especially AllowUsers if that's there only
specified users can connect, and
"PasswordAuthentication yes" for obvious r
"John F. Davis" <[EMAIL PROTECTED]> writes:
> Hello
>
> I did a apt-get upgrade which restarted ssh and now I can't ssh into
> my box anymore. I keep getting a invalid password response.
>
> I can however login to the box via the console with the same
> password.
>
> What gives?
> --
> We hos
On Thu, Jan 18, 2001 at 03:34:27PM -0500, David B. Harris wrote:
> To quote "John F. Davis" <[EMAIL PROTECTED]>,
> # Hello
> #
> # I tried to connect to the box from a machine which I have never
> # used as a client before. It failed also.
>
> Please be more specific with your problem. What vers
On Thu, Jan 18, 2001 at 08:21:56PM +0100, Norman Schmidt wrote:
> Hi!
>
> Did you try to login as root?
Nope.
>
> This is forbidden by default. You should not change this, but make sure
> you can su to root after logging in as known user.
Correct. I was logged in as a normal user.
>
> Check
To quote "John F. Davis" <[EMAIL PROTECTED]>,
# Hello
#
# I tried to connect to the box from a machine which I have never
# used as a client before. It failed also.
Please be more specific with your problem. What versions of SSH are on
each machine? What operating systems are on each machine? In
Hi!
Did you try to login as root?
This is forbidden by default. You should not change this, but make sure
you can su to root after logging in as known user.
Check your /etc/hosts.allow and /etc/hosts.deny files if there is any
restriction for the client you want to log in from.
"John F. Davis"
Hello
I tried to connect to the box from a machine which I have never
used as a client before. It failed also.
John
On Thu, Jan 18, 2001 at 12:05:59PM -0800, Robert L. Yelvington wrote:
> what is the specific message you are getting when you ssh in?
>
> when you restarted sshd it probably gene
what is the specific message you are getting when you ssh in?
when you restarted sshd it probably generated a new host key, right?
my guess is that you need to delete the old host key in your
~/.ssh/known_hosts file...perhaps...just a guess.
robt
"John F. Davis" wrote:
>
> Hello
>
> I did a
38 matches
Mail list logo
