Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Connection timed out |
|---|---|
| Date: | Tue, 14 Feb 2006 07:23:16 -0800 (PST) |
On Mon, 13 Feb 2006, Damm, Edward F. (E. Buddy) wrote:
Hi, I have a Linux machine that has the ssh daemon running, and am trying to access it via my windows xp machine with cygwin. I can ping the linux machine ip address, or nslookup the linux machine from cygwin. I can also do the reverse with the linux machine to windows. When I try ~# ssh myuserid@linux-ip-address or ~# ssh linux-ip-address it hangs for 15-20 seconds, then gives me the following error: ssh: connect to host xxx.xxx.x.xx port 22: Connection timed out
First, see if the Linux can SSH to itself. From some other connection or
from the console, run
ssh localhost
This will confirm that the sshd is running and accepting connections. If
it fails, you will know that the problem is on the Linux server.
Then make sure that you do not have a firewall that is blocking an
outbound connection on port 22 (normally). This might be a software
firewall running on your Windows PC. Windows XP SP2 has a built-in
firewall feature, but it is not supposed to block outbound connections,
only inbound connections. Others, though, such as those that are part of
Norton, Symantec, MacAfee, etc. security packages, can block outbound. If
you find one of these in place, you should be able to a) open the port in
question, b) authorize the program in question, or c) temporarily turn the
thing off for testing (be sure to turn it back on).
Finally, if the Windows PC has internet access, you could try connecting
via SSH to someone over the internet.
Regards,
....Bob Rasmussen, President, Rasmussen Software, Inc.
personal e-mail: ras@anzio.com
company e-mail: rsi@anzio.com
voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
fax: (US) 503-624-0760
web: http://www.anzio.com
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Bad utmp entry, Darren Tucker |
|---|---|
| Next by Date: | Re: openSSH of Solaris/Debian X does not work, Roland Turner (Security Focus) |
| Previous by Thread: | Connection timed out, Damm, Edward F. (E. Buddy) |
| Next by Thread: | Re: Connection timed out, Leif Ericksen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |