Upgrade to 4.3.199: cannot start applications anymore!

[yoda-ict]

Hello,

I've upgraded my old 4.2 installation to the new 4.3 release. I'm using 1 loadbalancer serving 1 terminal server. Upgraded the loadbalancer, then uninstalled the client on the terminal server and installed it through the management console of the loadbalancer machine. All looks wel.
I can connect with the new 4.3 client. I see my published applications.
As soon as i click an application i get an messagebox error:

The Client could not access the remote application.
Terminal Server might be too busy to accept new connections or network problems are preventing your connection.
Please try connecting again later.

There are no current sessions on the TS server. The loadbalancer log says:

Fri Mar 02 00:48:17 2007 - User FrRa, Client LAPTOP, Address xxx.xxx.xxx.xxx wants to open "#1" Application, Server SRVTS:3389 is available
Fri Mar 02 00:48:17 2007 - User FrRa, Client LAPTOP, Address xxx.xxx.xxx.xxx tunneled to SRVTS:3389 and started Application "#1"

And that's it. no message when i click ok on the error, nothing when closing the client.

Please help!

Frans

 

[nixu]

Hi there,

Is the client trying to connect in SSL mode or Gateway mode??

I sugguest you try to connect in direct mode (just to test the connection) & again paste your log.

Thanks

Nixu

 

[yoda-ict]

Hi there,

Is the client trying to connect in SSL mode or Gateway mode??

I sugguest you try to connect in direct mode (just to test the connection) & again paste your log.

Thanks

Nixu

Hello Nixu,

It seems i found the problem: when i want to start a application the X2 client is trying to establish a connection to the gateway on a high portnumber (in my case, tried several times, always above 63000). This cases the failing applications, as i published the X2 gateway on SSL 442 only. When i'm connecting through my internal firewall, ISA firewall client is opening this secondary port and the applications are started as usual.

It seems like something has changed in the client that is requesting a secondary connection on a high port number. I hope this can be prevented.

Frans

PS i'm connecting in SSL mode

 

[zippo]

"then uninstalled the client on the terminal server and installed it"

The client should be installed on the client machine and not on the terminal server. Can you please explain your setup in more detail?

 

[zippo]

Please note that when connecting in SSL mode there is a local conection which then redirects the data to the gatewat. The connection to gateway is always on the same port (443) by default.

Hi there,

Is the client trying to connect in SSL mode or Gateway mode??

I sugguest you try to connect in direct mode (just to test the connection) & again paste your log.

Thanks

Nixu

Hello Nixu,

It seems i found the problem: when i want to start a application the X2 client is trying to establish a connection to the gateway on a high portnumber (in my case, tried several times, always above 63000). This cases the failing applications, as i published the X2 gateway on SSL 442 only. When i'm connecting through my internal firewall, ISA firewall client is opening this secondary port and the applications are started as usual.

It seems like something has changed in the client that is requesting a secondary connection on a high port number. I hope this can be prevented.

Frans

PS i'm connecting in SSL mode

 

[yoda-ict]

It seems to work now. External clients are able to start the applications. I tested it by going over 2 firewalls (internal to external and then external to internal again) but that caused the problems i described.
As long as external clients can login all is fine.

Frans

 

[flowerpowerx]

terminal server might be too busy to accept connections

In my case the connection problem internal / external was related to the binding of the network adapters in the terminal server properties sheet
in administrative tools- TS server configuration-rdp tcp properties
- network adapters - make sure all adapters are selected here than it will function from inside and outside the network.