Cannot log in to machine on local network

[GoogleCodeExporter]

I have a machine on my LAN that has an external name (foo.dyndns.org) and
an internal name (foo.local). While on my LAN, I can't connect using the
external name, because the router doesn't support it. If I try to connect
using the internal name, ConnectBot does one of two things: either, the
screen goes straight back to the host menu, with no message, or, if I have
previously tried to connect using the external name (which starts the
connection attempt, but the connection is never made, exactly as expected),
then it tries to connect using the external name (foo.dyndns.org is shown
on screen, although I just asked for foo.local). The IP addresses for the
two names are of course different: foo.dyndns.org is a public IP address,
and foo.local is a LAN address.

If I am outside my LAN (e.g. by switching wireless off on my G1) then I can
connect fine using the external name.

Other machines on the LAN can connect fine using the internal name.

What is the expected output? What do you see instead?

What version of the product are you using (you can see this by using Menu
-> About in the Host List)?
1.5.3.

What type of system are you trying to connect to?
Ubuntu Jaunty.

Original issue reported on code.google.com by reubenrh...@gmail.com on 23 Jun 2009 at 9:27

[GoogleCodeExporter]

Is the .local name resolved via mDNS? I don't think Android supports that, if 
so.

I imagine it brings up foo.dyndns.org when you ask for foo.local because it's 
still
attempting to connect to foo.dyndns.org (i.e., the network connection hasn't 
timed
out yet)

Original comment by kenny@the-b.org on 23 Jun 2009 at 1:07

[GoogleCodeExporter]

> Is the .local name resolved via mDNS? I don't think Android supports that,
> if so.

I suspect this is the problem. Using the IP address works fine.

I notice, however, that if I try to connect to a non-existent
hostname, an error message does appear in the terminal screen, but
this is quickly replaced by the host menu, which is unhelpful.

> I imagine it brings up foo.dyndns.org when you ask for foo.local because
> it's still
> attempting to connect to foo.dyndns.org (i.e., the network connection hasn't
> timed
> out yet)

Quite possibly. But why? I selected foo.local, not foo.dyndns.org.

Original comment by reubenrh...@gmail.com on 25 Jun 2009 at 8:06

[GoogleCodeExporter]

> I notice, however, that if I try to connect to a non-existent
> hostname, an error message does appear in the terminal screen, but
> this is quickly replaced by the host menu, which is unhelpful.

Yes, sometimes the console disappears instead of sticking around when it can't 
connect.

> Quite possibly. But why? I selected foo.local, not foo.dyndns.org.

You can be connected to multiple hosts at once, so it's just displaying the
connection that is open in the ConsoleActivity. 

Original comment by kenny@the-b.org on 25 Jun 2009 at 8:15

[GoogleCodeExporter]

> You can be connected to multiple hosts at once, so it's just displaying the
> connection that is open in the ConsoleActivity. 

I don't understand. I click on one host, it shows me a connection to another. 
Why? I
would expect it to just go back to the host list if it can't open the host I 
want...

Original comment by reubenrh...@gmail.com on 25 Jun 2009 at 8:18

[GoogleCodeExporter]

Yeah, that could be made better. Basically it's trying to open your host, but it
can't connect immediately and destroys the terminal view leaving you with the 
one
that was already open.

The Multicast DNS thing is already Issue 118

Original comment by kenny@the-b.org on 30 Jun 2009 at 9:28

• Changed state: Duplicate