Quote:
Originally Posted by trist007
A good first step would be to make sure xdm is listening on the server machine. Login to the server and run
See if you see 0.0.0.0:6000 that is if X is running on :0
If is then, then see if you can reach it from your client.
From you client computer run this
Code:
nc -v hostname 6000
If it says connected then that's a good sign and the next step would be to look at xdm server configuration. |
the upper command is to be given on the machine that has the X running we want to connect to ("Serving X")
The lower command is to be given on the machine we want to connect from ("Client X"),
but the word "hostname" is to be replaced with either the "Serving X"s IP or DNS-name
The XDCP (is this name right?) is usually restrictive "out of the box" on Slackware, and maybe a FQDN might be needed:
Quote:
1. nc -v 192.168.1.2 6000
2. nc -v ithildin 6000
3. nc -v ithildin.bogous.lan 6000
|
hope this sheds some light on the issue?
in the later case You need to make up Your both machine /etc/hosts file to reflect the topology of Your particular network:
file:
/etc/hosts
Quote:
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server. Just add the names, addresses
# and any aliases to this file...
#
# By the way, Arnt Gulbrandsen <agulbra@nvg.unit.no> says that 127.0.0.1
# should NEVER be named with the name of the machine. It causes problems
# for some (stupid) programs, irc and reputedly talk. :^)
#
# For loopbacking.
127.0.0.1 localhost
127.0.0.1 <look below for this!!!>.bogous.lan <look left!>
#our "client X" host
192.168.1.1 rohan.bogous.lan rohan
#our "serving X" host
192.168.1.2 ithildin.bogous.lan ithildin
# End of hosts.
|
The marked entry will most probably be already there on Your machine(s) so You should take note of it, and lie it
as is 
The below is an illustration only of how a working hosts file might look, it was never tested (I wrote and edited quite few of them, and over quite a while, so I'm just comfortable it is probably correct) so I won't guarantee (GPL3 applies), but it is a good file IMHO.
Take note of the space separation and only full IP allowed
"#" denotes comment lines (not affecting DNS)
The file is checked by ping:
Code:
ping -c4 ithildin
ping -c4 ithildin.bogous.lan
for each IP and hostname used
Best regards,
Stevan C.
