Prev: KDE Crashing on starup
Next: Reading El Torito
From: Jim Howes on 14 Feb 2007 11:58
We have a DL-320 server here, which we set up in the usual way.

However, in this particular install, we set up eth1 as 192.168.0.x for the
internal lan (because that is what Kudzu found first), and eth0 as 192.168.111.x
for the yet-to-be-installed other network.

We set up the vnc-server, and discovered it didn't work.

Much scratching of heads later, removing firewall rules, and general mucking
about, we are no nearer a solution, when we swap the IP assignments of the
ethernet ports around so it is similar to the server two inches below it on the
rack. Consistency is, after all, good. At least we have tested both ethernet
ports, and they work just fine.

VNC works - xdmcp fires off the gdm-login stuff, etc. etc.

Change it back. Doesn't work.
Change it back, works fine.

We've even tried connecting another machine via eth1 and it seems that xdmcp
must be able to see the vnc client machine via eth0. We don't know why, because
Xvnc runs on the server, so is communicating with applications (and xdmcp) via
127.0.0.1

Any ideas why xdmcp is eth0-sensitive?

Jim
From: ale.cx on 15 Feb 2007 12:42
On Feb 14, 4:58 pm, Jim Howes <sewoh....(a)moc.gisorp.backwards.invalid>
wrote:

> Any ideas why xdmcp is eth0-sensitive?

Try 'lsof -i' to see what address(es) the relevant services are
listening on.

alexd

From: Jim Howes on 16 Feb 2007 05:55
ale.cx wrote:
> On Feb 14, 4:58 pm, Jim Howes <sewoh....(a)moc.gisorp.backwards.invalid>
> wrote:
>
>> Any ideas why xdmcp is eth0-sensitive?
>
> Try 'lsof -i' to see what address(es) the relevant services are
> listening on.

Hmm. Did that, and it does seem to be very eth0-oriented, despite eth0's
address not appearing in /etc/hosts, nor being served up by any nameserver
(because there isn't one on that network). The machine's hostname IS, however,
reported correctly by the DNS which the machine is using via eth1, and in
/etc/hosts, so I have no idea why Xvnc is opening buckets of sockets on eth0.

Jim
From: Colin McKinnon on 18 Feb 2007 10:59
ale.cx wrote:

> On Feb 14, 4:58 pm, Jim Howes <sewoh....(a)moc.gisorp.backwards.invalid>
> wrote:
>
>> Any ideas why xdmcp is eth0-sensitive?
>
> Try 'lsof -i' to see what address(es) the relevant services are
> listening on.
>
> alexd

lsof lists a lot of stuff - I'd suggest netstat -nap and post the results
here. Also check /etc/hosts.allow / ...deny

HTH

C.
 | 
Pages: 1
Prev: KDE Crashing on starup
Next: Reading El Torito