reply in-line<br><br><div class="gmail_quote">On Thu, Jul 30, 2009 at 12:17 PM, Andrew Browning <span dir="ltr"><<a href="mailto:drew826@gmail.com">drew826@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Thu, Jul 30, 2009 at 11:59 AM, E.H.<<a href="mailto:leprkhn@gmail.com">leprkhn@gmail.com</a>> wrote:<br>
> andrew: 192.168.0.5 is the only interface, should i change it back?<br>
<br>
</div>There's no real need to do so, unless you plan on changing the IP<br>
address in the future and don't want to have to edit the configuration<br>
file. I tend to keep my config file directives at default values<br>
unless there's a compelling reason to change them, but there's nothing<br>
wrong with specifying a particular interface to use (in fact, it's<br>
encouraged in certain situations).<br>
<div class="im"><br>
> ps says<br>
> that /usr/sbin/ssh is running. i can log into an ssh session from the<br>
> console, but not from putty.<br>
<br>
</div>Did you mean sshd? On the distros I'm familiar with, /usr/bin/ssh is<br>
the client and /usr/bin/sshd is the daemon. However, since you said<br>
you can log in to an ssh session from a console, I'll assume that<br>
means that sshd is in fact running.</blockquote><div> </div><div>it is. my mistake. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Are you logging in from a console<br>
on the same Ubuntu machine, or from a different one?</blockquote><div><br>same machine.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If you can log in<br>
locally but not from a remote machine, then your Ubuntu machine might<br>
not be accepting outside connections.<br>
<br>
You can check to see if your Ubuntu machine is listening on the sshd<br>
port with telnet. From your Windows machine, open a command prompt<br>
(Start->Run->cmd) and at the terminal, type<br>
"telnet 192.168.0.5 22" without the quotes (note there is a space, not<br>
a colon, between the IP address and the port). If you get a response<br>
along the lines of "Could not open connection...," then the Ubuntu<br>
machine _is not_ accepting outside connections on that port. If you<br>
instead get some kind of banner, along the lines of<br>
"SSH-2.0-OpenSSH_5.2," then the Ubuntu machine _is_ accepting outside<br>
connections on that port.</blockquote><div><br>i can telnet in and get a banner<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
If your Ubuntu machine is not accepting outside connections, then it<br>
might have a default firewall blocking port 22, or it might be using<br>
the hosts.allow/hosts.deny files.</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The files /etc/hosts.allow and /etc/hosts.deny specify which hosts are<br>
allowed to connect to your Ubuntu machine and one which ports. If your<br>
/etc/hosts.deny file has a line that reads something like "ALL: ALL:<br>
DENY," then you'll need to make sure that your /etc/hosts.allow file<br>
has a line that reads something like "sshd : ALL : allow" (assuming<br>
you're comfortable with all local network traffic being able to<br>
connect to your Ubuntu machine on TCP port 22). You can change the ALL<br>
to a specific hostname or subnet if you desire to do so. If your<br>
/etc/hosts.deny file is empty, then it pretty much allows all traffic<br>
through, so it might be a firewall issue instead.</blockquote><div><br>both hosts files are empty<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
I assume that Ubuntu uses iptables for a firewall; you can view its<br>
current configuration with (as root):<br>
#iptables -L -n<br>
If the INPUT chain lists a REJECT line for tcp dpt:22, then the<br>
firewall (if running) is blocking port TCP port 22, and you'll need to<br>
change that. If that's the case, respond back and we'll help with<br>
that.</blockquote><div><br>there are no iptables rules.<br><br>thank you for the great attempts though!<br><br>erik<br></div></div>