Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- Server refusing connection.
- Lief Erickson
May 17, 2007, 3:27 am
rate this thread
I need some assistance to figure out why my ssh server is refusing my
server: sshwindows on Windows XP Home
client: PuTTY on Windows 2000
Here is the log:
Originally Posted by Serverlog
debug2: read_server_config: filename /etc/sshd_config
debug1: sshd version OpenSSH_3.8.1p1
debug3: Not a RSA1 key file /etc/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #0 type 1 RSA
debug3: Not a RSA1 key file /etc/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
....snip boring stuff....
debug1: server_input_channel_open: ctype direct-tcpip rchan 257 win
16384 max 16384
debug1: server_request_direct_tcpip: originator client-side-connection
port 0, target <hostname>.dyndns.org port 9000
debug2: fd 11 setting TCP_NODELAY
debug2: fd 11 is O_NONBLOCK
debug2: fd 11 is O_NONBLOCK
debug1: channel 1: new [direct-tcpip]
debug1: server_input_channel_open: confirm direct-tcpip
debug3: channel 1: waiting for connection
debug1: channel 1: not connected: Connection refused
debug2: channel 1: zombie
debug2: channel 1: garbage collecting
debug1: channel 1: free: direct-tcpip, nchannels 2
debug3: channel 1: status: The following connections are open:
#0 server-session (t4 r256 i0/0 o0/0 fd 9/8)
debug3: channel 1: close_fds r 11 w 11 e -1
I'm trying to connect to port 9000 or 3483. When I type http://localhost:9000
or http://localhost:3483 on the client machine, I get the above
message error in my SSH server log. If I type any other port, for
instance, http://localhost:50873, nothing appears in the server log
(which I presume means everything is working correctly). My research
has shown that others have had similar messages in their logs, but I
couldn't find someone with the same log message as me and a solution.
A client-initiated channel is successfully created. From what I can
tell, it appears that the server is refusing the connection, but I'm
not clear as to why it is.
Hopefully, someone here can help.
Re: Server refusing connection.
It seems that your server isn't refusing connections, but encounters
refused connections when trying to obey your port forwarding directives.
I.e. the port forwarding, which you didn't tell us anything about beyond
the local ports that you are trying to connect to, makes the server try
to connect to <hostname>.dyndns.org port 9000, and that connection is
refused. Obviously we can't know why.
- » SSH without password - problems with particular userid
- — Next thread in » Secure Shell Forum
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum