81 Socket connection timeout reached

[notamonopoly]

Setup:
- 2XApplicationServer running on Windows XP Pro machine
- 2XApplicationServerClient running on Ubuntu 7.04 (Feisty)

Remote Desktop has been enabled in Windows and the 2X Console looks good.

I can easily connect to the XP box using Ubuntu's built in terminal server client but can not connect using 2X.

Trying:
"./appserverclient -s xxx.xx.xxx.xxx -u remoteuser -p xxxxxxx -d Mshome -a IEXPLORE -o3"
Result: "81 Socket connection timeout reached"

I do not have a firewall and have tried other ports to no avail.

I can provide any required details to help resolve the issue.

 

[Lee]

do you have a windows terminal server in place?

Windows XP can run the publishing agent and console, but WinXP itself is not designed to publish applications.

 

[notamonopoly]

I thought that the 2XApplicationServer was acting as a terminal server. In the console under "Terminal Servers" it has localhost checked, type RDP with a status of Agent Okay.

I've followed these steps: http://searchenterpriselinux.techtarget ... 29,00.html

So I believe that I have everything I need to make this work, I'm just wondering what the most likely cause of this error "81 Socket connection timeout reached" would be.

 

[notamonopoly]

C8 Segmentaion fault signal caught

I tried a different IP address from the applicationserverclient and receive the following:

"C8 Segmentaion fault signal caught".

So what does this mean?

It would be really nice if the application could provide a little more information. I mean that is not very useful. I've read over the manual and it was of no help.

Am I the only one that is a little concerned about Segmentation being spelled wrong? The error message has a spelling error. That's a first.

Seriously, can someone help me out?

 

[notamonopoly]

WTF

Well I finally got it working. Following another thread I discovered the need to install the file: http://www.kood.org/Termiserv_XPSP2_i386_1.0.exe on XP.

I've noticed that many people are asking for the same solution, which makes sense since Windows XP is currently the most widely used desktop on earth. I've also noticed that the immediate reply is a snarly "XP is not supported".

1) It should be, obviously.
2) Even if it isn't supported officially, why not provide the required information so that people who do want to, can try it. Then they're on their own.

This whole experience was bad. There was no help, except from other people being shunned http://www.2x.com/forums/viewtopic.php?t=864

Even once I got it running it was unstable and very unpredictable.

In hacking my way though to get it working other things stopped, such as my Samba shares. Great.

So you can claim that the problems are all because XP isn't officially supported but consider the number of problems people using the officially supported servers are having. There is no reason for it to be this complicated.

 

[gmax4]

Re: WTF

2) Even if it isn't supported officially, why not provide the required information so that people who do want to, can try it. Then they're on their own.

This is hilarious! First reason that I thinks is that it is illegal to convert XP into Terminal Server. You are trying to rip off Microsoft. Did they try to rip you off ?

I was read other forum posts with published applications on XP works. You need to disable fast user switching and disconnect from domain.

http://www.2x.com/forums/viewtopic.php?t=864