The Following User Says Thank You to fpp For This Useful Post: | ||
![]() |
2006-01-03
, 12:40
|
|
Posts: 1 |
Thanked: 0 times |
Joined on Dec 2005
@ Berlin
|
#2
|
![]() |
2006-01-03
, 21:52
|
|
Posts: 2,853 |
Thanked: 968 times |
Joined on Nov 2005
|
#3
|
I have two Windows PCs, one Gentoo box and a Sharp Zaurus on that LAN, all happily using this setup. The gateway (DSL router) is 10.10.10.1.
When I received the 770 I set it up the same way of course and at first all seemed to be well : it could connect to the web server on the Gentoo box and to the Internet through the router ; later when the vnc client became available it could connect to a vnc server on my XP box just fine.
The strange part came when I installed dropbear on the 770 and tried to connect from Windows with PuTTY : I just got an error message after a timeout period, no connection.
After double-checking the installation on the Nokia I tried connecting with a standard command-line ssh from the Gentoo box, then from the Zaurus : both relayed an error message from dropbear on the 770, something like "no route to host" or "destination unreachable". This led me to ping the 770 from every other machine on the LAN and sure enough, none could. I haven't found a "ping" utility on the 770 so I couldn't test the other way round, but remember, at the same time the Nokia was connecting just fine to those machines through http vnc etc.
At first I suspected a DHCP problem so I rewrote the connexion profile with fixed addresses for the 770, gateway and DNS, with the same result. Then on a hunch I changed the netmask to 255.255.0.0 (a class B address) and surprise, I could now ping the 770 and connect through ssh(*).
I wonder if this is an issue with the 770 TCP/IP stack or default setup, or something truly stupid I'm doing with my own LAN (but that at least four other machines, plus the occasional visiting laptop, have been happily ignoring up to now) ?
(*) though not very well yet, that's in the next post :-)