All Remote Clients Fail To Retrieve Server Status And Time Out While Performing Synchronization With Errors SBL-NET-01033: The SISNAPI handshake timed out (Doc ID 3070527.1)

Last updated on FEBRUARY 03, 2025

Applies to:

Symptoms

There is a network maintenance operation few days back and since then all Siebel Remote clients fail to synchronize with Remote Servers.
Synchronization stuck at the "retrieve server status" step and time out eventually.

While trying to analyze the network traffic from the client machines,  found that the initial TCP handshake gets an ACK from the Siebel server but then nothing.
On the server side the session being initialized but then it fails with the following error identified in Synchronization Manager log file:

The synchronization was working fine last week for all our remote users and no other operation or change was done. The network operation was rolled back but we still have the problem.

The issue can be reproduced at will with the following steps:
1. Open Siebel Remote client by clicking Icon in end user machine
2. Once log in to Remote clients invoke synchronization to synch the data with Siebel Remote Server

Changes

 Network team performed maintenance activities with TCP related changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.