Service is running but not application is now working.
We are facing some issue in our Tunnel Client server (Windows). It is not able to communicate with tunnel server.
This application was working before suddenly this issue has come.
As per CA Team, they told me to check telnet on port(48003). when i checked the same the telnet is not happening internally to same server by given port (48003). CA team told 48003 is not enabled in firewall, first enable this after that they will work.
But as per my Network and Window server team, there is no issue with telnet service, given port is already allowed in firewall. They are suspecting some issue with application itself. Because we are able to do telnet to other server by same port and for this server internally it is not working.
So please suggest me what to do.
How can i resolve this issue ?
if u have access to case portal, so please refer the case id : 00909820
Tunnel Client Cannot Connect to Tunnel Server
Also check if nimsoft processes like hub, controller, hdb running on client hub
not able to fine anything useful.
It wont work in my case.
Do u have any other steps to suggest on the same.
Whether we can able to telnet locally using 48003?
we are not able to do telnet locally.
So it a application issue ,from when are facing this issue ,any recent changes in hub ,can u share logs if possible .
Check your tunnel certificate expiry date and check alerts for that hub,if u have a backup try to restore it and check once .
Please find the error snapshot.
Dec 11 17:51:50:927 hub: CTRL receive message failed for get id command (connection closed)
Dec 11 17:51:50:927 hub: CTRL failed to get ID from 100.64.5.110/48003
Dec 11 17:52:25:480 hub: CTRL receive message failed for get id command (connection closed)
Dec 11 17:52:25:480 hub: CTRL failed to get ID from 100.64.5.110/48003
Dec 11 17:52:31:722 hub: Got STOP command from 100.64.3.35/50359.
Dec 11 17:52:31:722 hub: main: nimSessionWait rc =4
Dec 11 17:52:32:269 hub: thread shutdown
Dec 11 17:52:32:881 hub: CORE exit
Dec 11 17:52:35:727 hub: EXIT HUB: hub shutdown
Dec 11 17:52:35:727 hub: Waiting for tunnel to terminate ...
Dec 11 17:52:35:727 hub: Waited for 0 seconds for tunnel to terminate (OK)
IT Operations Centre (ITOC)
HCL Services Ltd.
(A Subsidiary of HCL Info systems Ltd.)
RS No 107/5,6 & 7,Sedarapet,
Pondicherry India- 605111
Tel: 1860–425 -1803
The information transmitted is intended only for the person or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of,
or taking of any action in reliance upon, this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact the sender and delete the material from
Hi, for a review, I suggest checking out the firewall port reference guide in the documentation. This page goes over what ports and settings are required on a base level for UIM.
Turned out the cause.
We have a BAT file embedded in Robot 7.93 which is expected to run upon robot_update package deployment.
For a reason unknown, it was not executed and necessary file renaming was not done.
Then robot in hub tunnel client did not work at all.
After renaming them manually, robot started to work and hub tunnel client also started to work.