From: MARTIN Greg \(Powerlink\) (gmartin@powerlink.com.au)
Date: Tue Jul 06 2004 - 03:06:42 EDT
Summary of Problem:
I am trying to connect to a 4.0g box using Reflection X.
The connection appears to be established (ie. screen goes from a grey X screen to black) then just before the login box is displayed the connection is lost. Reflection reports socket error number 10054. According to wrq this error is normally associated with more than one machine with the same IP address.
Back Ground:
* The 4.0g box has a unique IP address
* The windows box has a unique IP address
* The windows box is on the same lan segment to remove any firewall/router issues
* I can connect using this method to other 4.0g boxes on the network.
* I can login on to the graphical console with both a root and a user account.
* The box is using CDE which is specified in the /etc/rc.config file.
* The box was cloned from another on the network using vdump. The creation process consisted of cloning the partitions, changing the host name and IP address in the rc.config file, adding an entry in the /etc/hosts file, editing and changing the name of the kernel config file in /sys/conf and rebuilding the kernel.
* I can reflection X to the box that this one was cloned from.
* The Xaccess file is the default one in /usr/dt/config which appears to grant service to all displays.
* The Xconfig file is the default one in /usr/dt/config. At one point I copied and edited this file to disable the MIT-MAGIC-COOKIE-1 this had the effect of removing the cookie file from /var/dt/authdir/authfiles directory. When I re-enabled this setting a new cookie file was written.
* The /var/dt/Xerrors file contains a line for each of the four graphical console screens as expected however nothing else.
* There are some other customised files in the /etc/dt/config directory however they are identical to ones on the boxes that work.
Suggestions made most of which I had tried but tried again just to be sure.
* xhost + : Thanks George Banane
* Confirm correct procedure to rename box : Thanks John Lanier
* export display to X server on PC and run up X application :Thanks James Sainsbury and John Lanier
* Check no firewalling software running on PC and prove port 6000 open : Thanks James Sainsbury
* Check entries in /etc/securettys and try adding specific entries in securettys : Thanks John Lanier and Colin Bull
The Solution:
I fixed the network interface to 100M full Duplex at the firmware prompt ie.
>>> set ewa0_mode fastfd
Then I set the 3com switch to 100M full Duplex and disabled auto-negotiate.
Now I can connect with xdmcp.
Interesting because as you can see from some of the other actions performed the network appeared to be functioning satisfactorily.
Regards
Greg Martin
EMS Support
Phone Ext. 2865
Mobile 0438105269
email gmartin@powerlink.com.au
__________________
Important Message:
This e-mail (which includes any attachments) may contain personal information and is confidential.
If this e-mail has been sent to you by mistake please inform us by reply e-mail and then delete the e-mail, destroy any printed copy and do not disclose or use the information in it.
There is no warranty that this e-mail is error or virus free.
If this is a private communication it does not represent the views of Powerlink.
This e-mail is copyright. Powerlink is not liable if an attachment is altered without its written consent.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:02 EDT