When I try connecting to my Debian ssh server from Windows using Kitty, the connection times out. The Windows client and the Debian server are on the same wifi network. It doesn't even prompt me for a username. I can ssh into localhost from the server, and it worked when the server was on a different wifi network. I can connect to the internet from the server and the client. What could be going wrong?

Hi,

what sort of wireless network is this? Many wireless networks (including home routers) are setup to disallow traffic between devices on the network.
Can you ping one machine from the other?

Evo2.

Hi, is the iptables running in your server?When you ssh the server,what is the default port number used by kitty?

This is my home router. I have access to the router configuration page. When I ping the server's IP from the Windows client, I get a reply from a different IP.

iptables -L gives this:

Does that mean it's off?

Kitty uses port 22 by default. To make sure, I've tried specifying the port before I connect.

Hi,

so this looks like a network problem, not sshd problem and not a firewall problem (on the machine running sshd).

Have you tried running a traceroute to 10.0.0.61?

Evo2.

How can I work around this network problem?

Hi,

I think you need to configure your router. Point your browser at it and configure it. It may have built in help, or you may need to read the manual.

Cheers,

Evo2.

1 members found this post helpful.

My server was disconnecting from the wifi network whenever I logged out of Gnome. I went to the wifi options and enabled the connection for all users. Now it's working.

I'm having exactly the same problem, with the same ping/iptables/traceroute results, but with another ssh server (this thread seems reusable). This time, I've verified that it's connected to the internet by pinging google.com from the server. I've enabled and disabled every option on the router configuration pages. This took ages, and yielded no results.

Finally, I tried forwarding port 22 to the ssh server. Now I can ssh into it by using my external IP address. Is ssh through the external IP address inefficient? I'll be using this server for SFTP frequently, so I need speed. Samba isn't working either. If I can get ssh to work within the LAN, I bet Samba would work too.

Another issue: Both this server and the other one spontaneously disconnect from the wifi network after a few minutes. Since this server is headless and monitor/keyboardless, I have to restart it whenever this happens. I only have access to a keyboard and monitor for a few minutes at a time.

The wifi router is a Netgear WNR2000, and the usb wifi adapter is a D-Link DWL-G122.

The post quoted says it all. You could explore your router how to make a workaround on this.

I've enabled and disabled every option possible on the Netgear WNR2000 router. (I can't ping the server)

I have no problem sshing from my laptop running the ssh client Kitty on Windows 7 to another old laptop running Debian, my rooted Android phone running a ssh server, and my rooted Nook running an ssh server. I have no problem sshing into these three other devices. This leads me to believe this is a problem with this individual computer.

Hi,

Really?

If you want help I strongly suggest you very briefly describe exactly what the problem is in a new thread.

If this is an ssh problem. You should include information like:
- Results of ssh to localhost
- Confirmation of ping to the server
- Confirmation the port is open on the server (eg nmap)
- Contents of /var/log/auth.log on the on the machine running sshd when you try to ssh to it
- Output of "ssh -vvv" when you try to ssh to the server

Etc.

Evo2.