At home, I have a Netgear router flashed with DD-WRTv24 with remote SSHd running. TCP forwarding is enabled.
At my remote location, I use KiTTY.
When I start the connection to my IP (or even a DynDNS that redirects to my IP), it almost immediately says "server unexpectedly closed connection".
Once before, I could connect using my IP, with port 22, and with dynamic TCP forwarding enabled for port 8080. The next day, it suddenly stopped working, probably because the sysadmin blocked it.
The problem is probably not the port because I have tried using port 23, 80, and 8080. The router was notified of the port changes.
It's not KiTTY or the router because I had a friend at his house connect to it fine.
It's not my IP being blocked because I can connect to an HTTP server hosted on it... both with IP and DynDNS.
Does anyone have any ideas on what to try next?
I just tried again using a new installation of PuTTY and then KiTTY, no luck.
Are you behind an HTTP proxy? Try getting the internet explorer proxy settings and putting them into putty, with the help of [url]http://ntlmaps.sourceforge.net/[/url] if necessary.
Even if you aren't, consider setting one up on your home PC to get around any filters for HTTP traffic.
That's why I'm setting up the SSH... to tunnel!
if your remote location is running a proxy with the NTLM authentication scheme (if you nmap the proxy, you'll most likely see SquidAuth or something very similar), you'll need to download configure ntlmaps (linked 2 posts above this) to automatically authenticate your connection (most programs only use basic authentication and do not have an option for NTLM), and to fake your useragent to make it look like you were using a browser.
Also try to SSH into your server from another place with open internet (like a cell phone or a friend's house) to make sure that port 22 isn't being blocked by your ISP. Usually ISPs will block port 80 and port 443, some will unblock if you ask, others use it to make you buy their business package. If you can connect just fine, then your issue is probably just the NTLM authentication.
Sorry, you need to Log In to post a reply to this thread.