ssh problems ...

2006-07-31 Thread Kevin Brick

Hi All,

I'm trying to ssh to a remote linux PC using the command:

ssh [EMAIL PROTECTED] -l kb5 -v

doing this presents me with an error below :

OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to ssh.sanger.ac.uk [193.62.203.55] port 22.
debug1: connect to address 193.62.203.55 port 22: Connection refused
debug1: Connecting to ssh.sanger.ac.uk [193.62.203.54] port 22.
debug1: connect to address 193.62.203.54 port 22: Connection refused
ssh: connect to host ssh.sanger.ac.uk port 22: Connection refused

I've tried also to connect to a nother host (which I know works) with
similar results.  I'm a bit of a newbie to this whole ssh thing, so I'm not
sure if I should check for conflicts on port 22, or something like that ?
I've already disabled my local firewall with no luck, but was wondering if
the problem could be the overall network firewall blocking my access ?

Thanks for any help ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ssh problems ...

2006-07-31 Thread Eric
Kevin Brick wrote:
 Hi All,
 
 I'm trying to ssh to a remote linux PC using the command:
 
 ssh [EMAIL PROTECTED] -l kb5 -v
 
 doing this presents me with an error below :
 
 OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
 debug1: Reading configuration data /etc/ssh/ssh_config
 debug1: Applying options for *
 debug1: Connecting to ssh.sanger.ac.uk [193.62.203.55] port 22.
 debug1: connect to address 193.62.203.55 port 22: Connection refused
 debug1: Connecting to ssh.sanger.ac.uk [193.62.203.54] port 22.
 debug1: connect to address 193.62.203.54 port 22: Connection refused
 ssh: connect to host ssh.sanger.ac.uk port 22: Connection refused
 
 I've tried also to connect to a nother host (which I know works) with
 similar results.  I'm a bit of a newbie to this whole ssh thing, so I'm not
 sure if I should check for conflicts on port 22, or something like that ?
 I've already disabled my local firewall with no luck, but was wondering if
 the problem could be the overall network firewall blocking my access ?
 
 Thanks for any help ...

i just sshed to ssh.sanger.ac.uk and it connected just fine, so it looks
like you have something going on thats blocking access to the machine in
question. Of course I couldnt connect, but i had to add the host to my
known hosts and it asked me for a PW, etc.

If you are at work, there is most likely a firewall in place blocking
outbound access on everything but a very few select ports (port 80, etc).

can we get some more details on your setup?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


ssh problems after unrelated changes

2003-10-06 Thread Jesse Sheidlower

I'm running FreeBSD 4.8. I recently did some assorted work on
my system, upgrading a disk drive and rebuilding (not updating)
my kernel.

Now, I can't seem to ssh from my normal user account. When I try,
I get the error:

monopoly~ $ ssh somedomain.com
ssh_askpass: exec(/usr/X11R6/bin/ssh-askpass): No such file or directory
Host key verification failed.
monopoly~ $

I'm not trying to use any kind of graphical connection method, I
just want the usual login. I've tried unsetting $DISPLAY, and re-installing
OpenSSH from Ports, both with no effect. In the process of playing around
I accidentally deleted my .ssh/known_hosts file, but this also has had
no effect. I never had an ssh_config file in the first place.

Oddly, I _can_ ssh normally when sudo'd to root, but I can't see any
obvious reason--I don't have an ssh_config file as root, etc.

Thanks for any suggestions.

Jesse Sheidlower
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ICMP(ping) ssh problems

2002-12-17 Thread Edmond Baroud
hi,

pkg_info |grep -i sshd ( if sshd is installed :))
ps -aux|grep sshd ( to see if ssh is running )
netstat -an|grep -i listen|grep .22 ( if its listening on port 22)
which sshd (where's ur binary?)
or whereis sshd
if you have all these,
try to run it manually by typing sshd on ur shell
and add this to ur /etc/rc.conf
sshd_enable=YES
sshd_program=/path/to/sshd usually /usr/sbin or /usr/local/sbin
sshd_flags=

Ed.

Quoting Brian Henning ([EMAIL PROTECTED]):
 Hello-
 i am having problems connecting to my laptop. I just installed 4.7 the other
 day with mostly a default configuration. I am having problems with SSH and
 ICMP (ping). I think that the deamon that starts these servers is not
 running. what can i do to make assure the items i need running are running.
 
 thanks,
 brian
 
 
 result from ssh
 ---
 OpenSSH_3.4p1 FreeBSD-20020702, SSH protocols 1.5/2.0, OpenSSL 0x0090607f
 debug1: Reading configuration data /etc/ssh/ssh_config
 debug1: Rhosts Authentication disabled, originating port will not be
 trusted.
 debug1: ssh_connect: needpriv 0
 debug1: Connecting to 192.168.1.44 [192.168.1.44] port 22.
 
 
 
 telnet
 --
 [/root] telnet 192.168.1.44 22
 Trying 192.168.1.44...
 
 
 
 [/root] ping 192.168.1.44
 PING 192.168.1.44 (192.168.1.44): 56 data bytes
 ^C
 --- 192.168.1.44 ping statistics ---
 3 packets transmitted, 0 packets received, 100% packet loss
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message

-- 
Edmond Baroud 
UNIX Systems Admin mailto:[EMAIL PROTECTED]
Fingerprint  140F 5FD5 3FDD 45D9 226D  9602 8C3D EAFB 4E19 BEF9
UNIX is very user friendly, it's just picky about who its friends are.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: ICMP(ping) ssh problems

2002-12-17 Thread Edmond Baroud
make that, pkg_info |grep -i openssh
Quoting Edmond Baroud ([EMAIL PROTECTED]):
 hi,
 
 pkg_info |grep -i sshd ( if sshd is installed :))
 ps -aux|grep sshd ( to see if ssh is running )
 netstat -an|grep -i listen|grep .22 ( if its listening on port 22)
 which sshd (where's ur binary?)
 or whereis sshd
 if you have all these,
 try to run it manually by typing sshd on ur shell
 and add this to ur /etc/rc.conf
 sshd_enable=YES
 sshd_program=/path/to/sshd usually /usr/sbin or /usr/local/sbin
 sshd_flags=
 
 Ed.
 
 Quoting Brian Henning ([EMAIL PROTECTED]):
  Hello-
  i am having problems connecting to my laptop. I just installed 4.7 the other
  day with mostly a default configuration. I am having problems with SSH and
  ICMP (ping). I think that the deamon that starts these servers is not
  running. what can i do to make assure the items i need running are running.
  
  thanks,
  brian
  
  
  result from ssh
  ---
  OpenSSH_3.4p1 FreeBSD-20020702, SSH protocols 1.5/2.0, OpenSSL 0x0090607f
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: Rhosts Authentication disabled, originating port will not be
  trusted.
  debug1: ssh_connect: needpriv 0
  debug1: Connecting to 192.168.1.44 [192.168.1.44] port 22.
  
  
  
  telnet
  --
  [/root] telnet 192.168.1.44 22
  Trying 192.168.1.44...
  
  
  
  [/root] ping 192.168.1.44
  PING 192.168.1.44 (192.168.1.44): 56 data bytes
  ^C
  --- 192.168.1.44 ping statistics ---
  3 packets transmitted, 0 packets received, 100% packet loss
  
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-questions in the body of the message
 
 -- 
 Edmond Baroud 
 UNIX Systems Admin mailto:[EMAIL PROTECTED]
 Fingerprint  140F 5FD5 3FDD 45D9 226D  9602 8C3D EAFB 4E19 BEF9
 UNIX is very user friendly, it's just picky about who its friends are.
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message

-- 
Edmond Baroud 
UNIX Systems Admin mailto:[EMAIL PROTECTED]
Fingerprint  140F 5FD5 3FDD 45D9 226D  9602 8C3D EAFB 4E19 BEF9
UNIX is very user friendly, it's just picky about who its friends are.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message