- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Data Protector Express 4.00 sp1 using wrong IP add...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
12-09-2010 10:28 AM
12-09-2010 10:28 AM
We recently installed a second NIC in the Windows 2003 server acting as the Data Protector Express 4.00 sp1 domain server. The server is now binding to the wrong NIC so it is using the wrong IP address. Our other servers can't communicate with Data Protector although they can communicate with the server in general (ping and DNS work).
I don't see any reference to NIC or IP address in the dpconfig.ini file. However when we check the properties - connections section of the server it shows it is using the wrong IP address. We can't edit this field however.
How do we change the Data Protector Express NIC address binding? Is there another INI file it uses?
Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2010 08:51 AM
12-10-2010 08:51 AM
SolutionI found the answer in another post on this site:
I have two or more network cards in my machine, is this preventing connection to the Data Protector Express Storage Domain?
In some cases a machine with multiple network cards may not be able to connect to the Data Protector Express Storage Domain because communication is attempted via the 'wrong' network card. The solution is to bind Data Protector Express to the network card in the network used by the Data Protector Express Storage Domain.
To bind DPX to a specific network card perform the following steps:
Close Data Protector Express.
Stop the Data Protector Express Service.
Open the dpconfig.ini (Install_Path\config, by default) with a text editor (e.g., Windows NotePad).
In the configuration section, add the following line:
bindTo=xxx.xxx.xxx.xxx
Where xxx.xxx.xxx.xxx is the IP address of the local network card that communicates with the Data Protector Express Storage Domain.This section should resemble the following:
configuration
lastUser=Admin
lastDomain=Data Protector Express Storage Domain
nodeGuid={00001001-421F132A-0003F771-FFE580D7}
databaseServerAddress=localhost
isDatabaseServer=Yes
databaseServerName=Data Protector Express Storage Domain
disableNetwork=No
remoteAdmin=No
bindTo=xxx.xxx.xxx.xxx ;(IP address here)Save the file as a text file and close it.
Start the Data Protector Express Service.
Data Protector Express should now be able to connect to the Data Protector Express Storage Domain.