03-09-22 03:51 PM
Hello,
We recently migrated our servers to the cloud; after migration, we are receiving the following error message from IC/Runtime machines.
Error: Could not connect to connection 'L&R Dev'
Client is unable to finish the security negotiation within the configured timeout (00:00:08.9292655). The current negotiation leg is 1 (00:00:08.9292655).
Please let me know if you have any suggestions about this error message.
Regards,
Hari
05-09-22 02:07 PM
06-09-22 05:17 PM
20-03-23 03:18 PM
@ewilson I know the conversation didn't go anywhere because the previous submitter didn't have their ports open; however, we do have our ports open on our firewall and we are having issues. We have a BP environment (AppServers, ICs, and RRs) in a hosted cloud which is connected to network via S2S VPN/Firewall trying to talk to an on-prem RR and it is currently not working. We have all the FW Rules/Ports in place. The on-prem RR can see the Cloud Hosted Dev environment and AppServer; however, when we try to have the AppServer conncet to RR or run a process on the RR, it can never connect and times out. Any ideas?
21-03-23 05:16 PM
So the App Server in the hosted cloud environment cannot communicate at all with the on-prem RR's? On the on-prem RR's can you see the traffic hitting the machine from the app server? Or does the app server come into the RR and the RR simply rejects it?
Cheers,
21-03-23 06:08 PM
There's bidirectional communication three hops over a firewall security appliance with firewall port openings for tcp/udp 8181,8199 in wcf with encryption mode. The runtime resources can sign in, but the callback fails and they show as offline.