Hello,
Running W2K server/SP4 with 2 NICs. One NIC has a public IP and the other a private IP. I need a service to be bound to the public NIC. It is the Liebert Multilink service used for UPS communications/shutdowns. After the second NIC with the private IP was added, this service bound itself to the private NIC card after rebooting.
The software vendor stated that the app. does not support 2 NICs and the service will "randomly" choose the NIC it binds itself to. I asked if you could manually change the registry to bind the service to the other NIC and he said you could try that, but it's unsupported (naturally).
The private NIC is a copper gig card that is being used for an iSCSI backup scheme. The public NIC is a copper 10/100 copper card being used for all other communications. When all is said and done there will be about 50 servers with gig & 10/100 NICs that this service may affect depending on it's random choosing of NIC card to apply its service...So swapping IP addresses on the two NICs in each server isn't an option as the gig card has to be used for the iSCSI and purchasing additional gig cards is not an option at this time.
Any registry guru's that could offer any suggestions would be greatly appreciated.
Thanks!
Running W2K server/SP4 with 2 NICs. One NIC has a public IP and the other a private IP. I need a service to be bound to the public NIC. It is the Liebert Multilink service used for UPS communications/shutdowns. After the second NIC with the private IP was added, this service bound itself to the private NIC card after rebooting.
The software vendor stated that the app. does not support 2 NICs and the service will "randomly" choose the NIC it binds itself to. I asked if you could manually change the registry to bind the service to the other NIC and he said you could try that, but it's unsupported (naturally).
The private NIC is a copper gig card that is being used for an iSCSI backup scheme. The public NIC is a copper 10/100 copper card being used for all other communications. When all is said and done there will be about 50 servers with gig & 10/100 NICs that this service may affect depending on it's random choosing of NIC card to apply its service...So swapping IP addresses on the two NICs in each server isn't an option as the gig card has to be used for the iSCSI and purchasing additional gig cards is not an option at this time.
Any registry guru's that could offer any suggestions would be greatly appreciated.
Thanks!