![]() ![]() So the Receiver for web was working fine. ![]() From routine visits to advanced services, our physicians practice at more than 100 locations across the Greater Houston area. We have over 2,000 health care providers with expertise in more than 80 specialties and subspecialties. ![]() There is a firewall between the external NetScaler and internal NetScaler that was creating this problem.įor the Receiver for web traffic, the traffic is coming to external NetScaler and to reach internal NetScaler it is using a different network path rather than what was being used for the Receiver and in that path there is no firewall. UT Physicians provides primary and specialty care for patients of all ages. That is because when the External NetScaler sends a client hello, in response we are seeing "continuation" with HTTP data in it due to which external NetScaler is resetting the connection with bad SSL record reset code. After the authentication when the external NetScaler tries to send the StoreFront discover request to the internal NetScaler we see that the SSL connection breaks. Customer has an external NetScaler on which the traffic would land and in the session profile of this NetScaler they had pointed the StoreFront LB VServer as Web Interface address and that LB Vserver is hosted on an internal load balancer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |