Heedh Posted August 5, 2002 Report Share Posted August 5, 2002 (Posted this last week to the "Networking" forum and didn't get any responses. Hoping for better luck from the gurus over here). I am running Retrospect Workgroup Edition 5.6.132 on a Win2K server that is multi-homed. While trying to add clients to the backup database, I have become painfully aware of the single-subnet limitation. My question involves subnet selection. Retrospect has selected the "wrong" (wrong for my purposes, at least) subnet for its broadcasts. It appears to have bound to the first NIC in the TCP I/P stack -- which must remain the first NIC for reasons having to do with with VPN configuration. Unfortunately, that NIC connects to my DMZ, which does not contain any of the computers that I wish to back up. The other "internal" NIC connects to the subnet with all of the clients that I would like to back up. How can I change which of the two subnets it will back up? Is there a magical registry setting, incantation, or live sacrifice I can make? Thanks in advance, -Ed Harris Link to comment Share on other sites More sharing options...
ChuckS Posted August 7, 2002 Report Share Posted August 7, 2002 The only trick available to solve the problem involves changing the order of the network connections in 2000's Advanced Network Settings, but you've indicated that this isn't an option. Unlike for the client, there is no registry value to change to force the application to bind to another NIC (that I am aware of). You may have to either purchase 5.6 Server, or upgrade to 6.0 Single Server, both of which have the multiple-subnet functionality you're looking for. Retrospect also does not support live or burnt sacrifices. Alternately, if you have another computer available, you might consider backing up from another computer on the "inside" of your network. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.