Ssh communication problem

[Petbul]

Is anybody who understand initial communication between client and server and is able to help us find the problem please ?
We have problem with Mincom MIMS (running on Tuxedo) client to server communication.
We are using TCP forwardig (SSH - Secure Shell) to get through Firewall.
We observed first TCP channel opened by MIMS client (WSL) is closed without
new TCP stream (WSH) from client to server established.
We do not know, why first TCP communication (WSL) failed.

I can send you complete dump of communication from MIMS client to ssh forwarding host, UBB config file etc...

Many thanks.
Petr
PS : Communication without ssh is OK ...

 

[blakej]

The tuxedo WSL will listen on a designated port of connection request. Once it receives a connection request it spawns the user off onto a WSH. By default the WSH will try to use a random port between 2048 and 65535.

You will run into problems if the high port ranges are blocked by a firewall. The MIMS front-end established a connection but soon drops it again because the firewall doesn't allow the WSH to talk to the client.

The solution was to unblock a port range on the firewall and change the UBB config file entry for the WSL to specify a port range with -p and -P

CLOPT="A -- -n//clsmnvt1:mimstrn -T120 -x10 -m20 -p 13450 -P 13500"

it worked perfectly.
Hope this helps.