- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Network Connectivity on DL360G5 server
ProLiant Servers (ML,DL,SL)
1753515
Members
5447
Online
108795
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
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
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-30-2007 02:45 AM
10-30-2007 02:45 AM
Network Connectivity on DL360G5 server
Hi,
Almost for a month our team has been struggling over this network problem and by now all ideas as to how to fix the issue have been exhausted.
We have purchased relatively new servers DL 360G5 and already started to blame the new G5 generation as on the old G4 with the same configuration we’ve never had similar errors and all functions smoothly.
We have two servers with Windows 2003 Web Edition SP2. They are configured with VLAN interfaces on the first network adapters. We created Network Load Balancing cluster using Windows 2003 NLB Manager on these two servers. The multicast mode is used. The second physical interface is disabled on each server. The TCP Offload Engine and Receive Side Scaling options are disabled in the Network Configuration Utility. We disabled the TCP Chimney functionality in the stack with the help of the following command in the command prompt: "nets int ip set chimney DISABLED".
When we check the connections to the servers on their main addresses using HTTPS, all works fine. However, when we check the NLB address using HTTPS we get these intermittent errors: "An existing connection was forcibly closed by the remote host".
We have the latest firmware and driver version installed. Also we have tried the server resetup and it does not eliminate the problem. To exclude a possibility of IIS connection, we’ve updated the SCHANNEL.DLL file to version 5.2.3790.4008. One certificate is used for both servers. “Require Secure Channel (SSL)” and “Require 128-bit encryption” options are enabled in the IIS configuration.
If anyone has ever seen the similar issue, could you please come with your suggestions? Any advice/help would be very much appreciated.
Many thanks
Almost for a month our team has been struggling over this network problem and by now all ideas as to how to fix the issue have been exhausted.
We have purchased relatively new servers DL 360G5 and already started to blame the new G5 generation as on the old G4 with the same configuration we’ve never had similar errors and all functions smoothly.
We have two servers with Windows 2003 Web Edition SP2. They are configured with VLAN interfaces on the first network adapters. We created Network Load Balancing cluster using Windows 2003 NLB Manager on these two servers. The multicast mode is used. The second physical interface is disabled on each server. The TCP Offload Engine and Receive Side Scaling options are disabled in the Network Configuration Utility. We disabled the TCP Chimney functionality in the stack with the help of the following command in the command prompt: "nets int ip set chimney DISABLED".
When we check the connections to the servers on their main addresses using HTTPS, all works fine. However, when we check the NLB address using HTTPS we get these intermittent errors: "An existing connection was forcibly closed by the remote host".
We have the latest firmware and driver version installed. Also we have tried the server resetup and it does not eliminate the problem. To exclude a possibility of IIS connection, we’ve updated the SCHANNEL.DLL file to version 5.2.3790.4008. One certificate is used for both servers. “Require Secure Channel (SSL)” and “Require 128-bit encryption” options are enabled in the IIS configuration.
If anyone has ever seen the similar issue, could you please come with your suggestions? Any advice/help would be very much appreciated.
Many thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2007 07:13 AM
10-30-2007 07:13 AM
Re: Network Connectivity on DL360G5 server
Hello,
I have came across different forums with same issue; most of them suggesting to sniff for the packets.. & check what happens to it..
Like this one in microsoft's MSDN;
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=497825&SiteID=1
Try the NETMON (link provided).
Another guy, Running AS 2005 SP1 on Windows Server 2003 had to delete & create his windows profile to get rid of this.. as some drivers were conflicting..which one?..its a mystery.
Regards.
PS: Im not an network/scripting expert; Hence, excuse me if this was not relevant.
I have came across different forums with same issue; most of them suggesting to sniff for the packets.. & check what happens to it..
Like this one in microsoft's MSDN;
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=497825&SiteID=1
Try the NETMON (link provided).
Another guy, Running AS 2005 SP1 on Windows Server 2003 had to delete & create his windows profile to get rid of this.. as some drivers were conflicting..which one?..its a mystery.
Regards.
PS: Im not an network/scripting expert; Hence, excuse me if this was not relevant.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP