- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: NIC Teaming conmunication issue
ProLiant Servers (ML,DL,SL)
1754015
Members
7731
Online
108811
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
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО04-08-2004 06:29 AM
тАО04-08-2004 06:29 AM
I have a customer using the 7.41.0.0 version of the HP ProLiant Network Configuration Utility.
They have TLB set up with two HP NC7781 Gig NICs.
The virtual NIC (HP Network Team #1) has the same IP address as the physical NIC 2.
They're using MAC balancing.
Here is the problem. Our packet capture driver is only binding to the virtual NIC, and we are unable to communicate with that NIC for some reason.
The customer can ping the machine and get the IP address associated with the team, and can also do a netstat -a on the server to see that our TCP port 2408 is listening. However, if the customer does a test using Telnet 2408, they get a connection failed type message.
If this were working properly, the Telnet screen would come back with a blank screen and blinking cursor.
Anyone have any ideas on why we can't communicate with this box?
Is there some sort of port filter that might be applied?
The customer says that there is no firewall between his machine and the server, so I'm trying to think of what else in the teaming setup might be disallowing us to communicate.
Any thoughts you may have are greatly appreciated. Please let me know if you need additional information.
They have TLB set up with two HP NC7781 Gig NICs.
The virtual NIC (HP Network Team #1) has the same IP address as the physical NIC 2.
They're using MAC balancing.
Here is the problem. Our packet capture driver is only binding to the virtual NIC, and we are unable to communicate with that NIC for some reason.
The customer can ping the machine and get the IP address associated with the team, and can also do a netstat -a on the server to see that our TCP port 2408 is listening. However, if the customer does a test using Telnet
If this were working properly, the Telnet screen would come back with a blank screen and blinking cursor.
Anyone have any ideas on why we can't communicate with this box?
Is there some sort of port filter that might be applied?
The customer says that there is no firewall between his machine and the server, so I'm trying to think of what else in the teaming setup might be disallowing us to communicate.
Any thoughts you may have are greatly appreciated. Please let me know if you need additional information.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2004 04:37 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2004 04:52 AM
тАО04-09-2004 04:52 AM
Re: NIC Teaming conmunication issue
Thanks for the feedback Randy. I just figured out the problem last night, or so I believe.
Our capture driver doesn't by default recognize virtual adapters. We have a registry entry that changes the default NIC filter to allow us to see virtual NICs.
I was under the impression that this entry was merely a display function, but discovered last night that it also resolved the communication issue. A single solution to two issues, gotta love it. :)
Thanks again for the help.
Our capture driver doesn't by default recognize virtual adapters. We have a registry entry that changes the default NIC filter to allow us to see virtual NICs.
I was under the impression that this entry was merely a display function, but discovered last night that it also resolved the communication issue. A single solution to two issues, gotta love it. :)
Thanks again for the help.
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