Hmmmph. Okay, from the above I collect that I really don't know what I'm doing more than usual. As for example I'm not quite clear about
You were close but on the wrong box. the zaurus ip should be 192.168.129.201 the windows box has to have the ip set to 192.168.129.1.
The Zaurus Manager application on the W2K desktop allows me to set a hostname (currently set to "poodle") and a host ip, currently set to 192.168.129.201. There's a little note that says the "Communications Setting must match the zaurus PC link settings".
On the Zaurus, there's a Security tab that has
- an authentication screen, I didn't change anything there
- a plug-ins screen, it's empty
- a login screen, it's set to to login automatically root
- and a sync screen, it's set to accept synch from network any, synch software Opie 1.0
Then there is a Network tab that shows two "up" connections. One is the local loopback, the other is
Ethernet (usbd0) 192.168.129.201
The configuration page for the usbd0 connection shows that it is set to "automatically bring up" and a static configuration with IP address 192.168.129.201 and subnet mask 255.255.255.0
And actually, that's pretty much all the relevant settings I can find without poking about in /etc files.
As I said, trying to reach the Z from my desktop basically times out, e.g.
[c:\]ping 192.168.129.201
Pinging 192.168.129.201 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 157.130.31.217: Destination host unreachable.
Ping statistics for 192.168.129.201:
  Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
  Minimum = 0ms, Maximum =  0ms, Average =  0ms
[c:\]ping 192.168.129.201
Pinging 192.168.129.201 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 157.130.31.217: Destination host unreachable.
Request timed out.
Ping statistics for 192.168.129.201:
  Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
  Minimum = 0ms, Maximum =  0ms, Average =  0ms
[c:\]telnet 192.168.129.201 4242
Connecting To 192.168.129.201...Could not open a connection to host on port 4242
: Connect failed
You'll note that in the last example I tried zenyatta's idea of a raw telnet to port 4242. I've also tried putty ssh connections, ftp to port 4242, and sundry pings. They time out.
Ideas?
Windrose