Do you know if the AR server is receiving the initial SYN packet? Is the client receiving the SYN/ACK packet? Window size shouldn’t really come into play until the three-way handshake between client and server has been completed. If I remember correctly once the TCP session has been established only then can the client & server negotiate the appropriate window size.
Have your network engineers checked the firewall logs to see if anything is being dropped by an ACL? Sometimes a different software version could potentially evaluate a rule differently (even though it shouldn’t). -Rick From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Manoj Kumar Sent: Thursday, June 16, 2016 4:15 AM To: [email protected] Subject: Unable to connect BMC Remedy client tools to Arserver ** Hi All > We are unable to Unable to connect BMC Remedy client tools to Arserver. There > was a recent firewall upgrade in our network and after which we are unable to > connect client tools to ARserver. Has anyone face this issue before. > > > > Error: Server 172.28.210.200 reports: ERROR (91): RPC call failed; > 172.28.210.200:2000<http://172.28.210.200:2000> ONC/RPC call timed out, 5060, > > > > We were able to connect to the server before the firewall upgrade. > > > > We are able to telnet the ARserver. But when we see the wireshark logs, we > see the window size as 65280. could this be the problem > > > > > > > > Thanks & Regards, > > Philip Richard > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
