Xmanager Forum

System Administrator

Last post: Thursday, September 13, 2012 10:48 PM by Support, 3 reply

 
Thursday, September 6, 2012 9:16 AM - John P

System Administrator

 
When creating a XDMCP session on Win 7_64 system with multiple ehternet interfaces, the "Local Address" setting in the Session properties does not seem to work correctly when the "Connection Address Type" is set to Automatic. It seems that the index is bad becaus no mater what Local Address s select, the host being connected to always tries to respond to the next one listed in the dropdown.

Then only way I can get it to work is if I manually edit the .xdts file and clear the "LocalAddressIndex=' setting. Then when that session is launched, the IP selector pops up and allows the selection of the return IP to use.

I am attaching Xmanager log files from the two scenarios (X0.log is the failed attempt)

Program Ver. : Xmanager 4
Connect Method : XDMCP connection
Thursday, September 6, 2012 6:45 PM - Support

Re: System Administrator

 
To change the LocalAddressIndex value, you need to set the Local Address field not the Address Type field.

Address type in Connection Address is used in cases you want x11 client to connect to a different host than your PC.

Please let us know if we can be of further assistance.

---
Technical Support
Thursday, September 13, 2012 7:19 AM - John P

Re: System Administrator

 
That is exactly what is not working. Assuming my Local Address drop-down has:
Auto Select, 10.10.2.213, 10.10.0.75, 192.168.255.225 in that order.

When I select 10.10.0.75 the host at 10.10.0.76 tries to connect to 192.168.255.225.
netstat on the host shows:
10.10.0.76.33371 192.168.255.225.6001 0 0 49640 0 SYN_SENT

If I select 10.10.2.213 (the one before it) connecting to the same host works fine. If I select "Auto Select" the host tries to respond to 10.10.2.213

I just found out that if I select the last one in the drop-down, Xmanager crashes.
Thursday, September 13, 2012 10:48 PM - Support

Re: System Administrator

 
I have successfully duplicated the problem. It has been reported to the developers. Thank you for reporting the problem.


---
Technical Support