HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Could not establish SSL\TSL connection with NLB an...
Windows Server 2003
1832515
Members
5042
Online
110043
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2006 04:11 AM
10-10-2006 04:11 AM
Could not establish SSL\TSL connection with NLB and HP Network Team on DL360 G4
This issue firstly appeared after SP1 for Windows Server 2003 was installed on all the network servers. Before the SP1 install the environment hadn’t have any issues similar to this one.
After SP1 install the whole system faced intermittent errors while establishing connection with NLB clusters addresses of the servers. These connection errors are of sporadic nature and occur from time to time. We used the special Microsoft tool named WFetch to trace HTTPS communications between the affected servers and saw that on average every five connection ended with the following error: “The underlying connection was closed: Could not establish secure channel for SSL/TLS.”. After dissolving HP Network Teaming this issue disappears. But at the moment the servers connections have lost hardware redundancy and the network bandwidth is decreased from 2 Gb/s down to 1 Gb/s. Does anyone know how to resolve this? What should we do to upgrade to SP1 without errors?
After SP1 install the whole system faced intermittent errors while establishing connection with NLB clusters addresses of the servers. These connection errors are of sporadic nature and occur from time to time. We used the special Microsoft tool named WFetch to trace HTTPS communications between the affected servers and saw that on average every five connection ended with the following error: “The underlying connection was closed: Could not establish secure channel for SSL/TLS.”. After dissolving HP Network Teaming this issue disappears. But at the moment the servers connections have lost hardware redundancy and the network bandwidth is decreased from 2 Gb/s down to 1 Gb/s. Does anyone know how to resolve this? What should we do to upgrade to SP1 without errors?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2006 07:11 PM
10-15-2006 07:11 PM
Re: Could not establish SSL\TSL connection with NLB and HP Network Team on DL360 G4
When you use Microsoft's NLB there may be problems with teamed NIC's
The reason why is that the network team in some configurations uses heartbeats to poll/check the status of the team. This can be in conflict with Microsoft's NLB heartbeat. Another problem is that two "layers" of virtual MAC addresses may not work.
http://support.microsoft.com/kb/278431/
Best suggestion I can give is to check you have the latest NIC drivers and NCU (Network Configuration Utility)(=teaming driver) installed. If still problems I would recommend not using teaming due to the above.
Cheers,
Rune
The reason why is that the network team in some configurations uses heartbeats to poll/check the status of the team. This can be in conflict with Microsoft's NLB heartbeat. Another problem is that two "layers" of virtual MAC addresses may not work.
http://support.microsoft.com/kb/278431/
Best suggestion I can give is to check you have the latest NIC drivers and NCU (Network Configuration Utility)(=teaming driver) installed. If still problems I would recommend not using teaming due to the above.
Cheers,
Rune
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP