- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: BL870C Network
BladeSystem - General
1748182
Members
3524
Online
108759
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
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
тАО09-29-2009 11:46 PM
тАО09-29-2009 11:46 PM
BL870C Network
We have hp bl870c server .It have 4 network card different ip adderss but same subnet mast we got a one error msg like A duplicate name has been detected on the TCP network. The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2009 04:46 AM
тАО09-30-2009 04:46 AM
Re: BL870C Network
You're using some version of Windows, I assume?
As it says, you have a duplicate _name_, not a duplicate _address_.
In other words, two different servers may be using the same Computer Name (Control Panel -> System -> Computer Name). You can't have two computers with the same name in the same domain/workgroup.
Use the command listed in the error message (nbtstat -n) to identify the name that has "Conflict" in the status field.
You can also find the IP address of the conflicting server by looking at the data field of the error message in the Event Log.
MK
As it says, you have a duplicate _name_, not a duplicate _address_.
In other words, two different servers may be using the same Computer Name (Control Panel -> System -> Computer Name). You can't have two computers with the same name in the same domain/workgroup.
Use the command listed in the error message (nbtstat -n) to identify the name that has "Conflict" in the status field.
You can also find the IP address of the conflicting server by looking at the data field of the error message in the Event Log.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2009 01:48 AM
тАО10-01-2009 01:48 AM
Re: BL870C Network
thanks- you for replay. sir we are using windows 2008 server 64bit BL870C SERVER.
WE ARE using MS DTC SQL clustering . so we are using 4 network card. but same System name.
i had viewed my domain server DNS. Address.it have 4 network cards have Same System Name..
how can i slove this problem sir.
WE ARE using MS DTC SQL clustering . so we are using 4 network card. but same System name.
i had viewed my domain server DNS. Address.it have 4 network cards have Same System Name..
how can i slove this problem sir.
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