WINS Domain Controller Entry is backup IP address

HI. I have two win2003 domain controllers that are
multihomed that run wins and dns. I am having some issues
with the WINS entries using the backup
network(192.168.1.100) addresses for several entries that
are definately problematic.

--__MSBROWSE__-

Domain Master Browser

File Server

Domain Controller

and so on. What can I do to setup static entries for these
because noone has access to that backup network and those
ip's will not work. It is definately causing issues with
browsing through network neighborhood because you cannot
see all the workstations just the servers that are on the
backup network. Thanks for your help. Eric

A multihomed master browser will cause you
problems the most common being the domain
wide list will not be merge rather two lists for
each subnet. Having said that it almost sounds
like you are trying to do some sort of load
balancing when you say "backup network"?
Can we assume both NICs are on the same
subnet?

"Eric Hughes" <(E-Mail Removed)> wrote in message
news:
>
> HI. I have two win2003 domain controllers that are
> multihomed that run wins and dns. I am having some issues
> with the WINS entries using the backup
> network(192.168.1.100) addresses for several entries that
> are definately problematic.
>
> --__MSBROWSE__-
>
> Domain Master Browser
>
> File Server
>
> Domain Controller
>
> and so on. What can I do to setup static entries for these
> because noone has access to that backup network and those
> ip's will not work. It is definately causing issues with
> browsing through network neighborhood because you cannot
> see all the workstations just the servers that are on the
> backup network. Thanks for your help. Eric
>
>
>

The backup network is on a different subnet. It is
specifically for doing tape backups during production
hours. That way the backups dont have any impact on
fileserver or database performance over the network. The
production network is 155.100.176 and the backup network is
192.168.1. I am still confused to say the least.
Thanks ERic
>-----Original Message-----
>A multihomed master browser will cause you
>problems the most common being the domain
>wide list will not be merge rather two lists for
>each subnet. Having said that it almost sounds
>like you are trying to do some sort of load
>balancing when you say "backup network"?
>Can we assume both NICs are on the same
>subnet?
>
>"Eric Hughes" <(E-Mail Removed)> wrote
in message
>news:
>>
>> HI. I have two win2003 domain controllers that are
>> multihomed that run wins and dns. I am having some issues
>> with the WINS entries using the backup
>> network(192.168.1.100) addresses for several entries that
>> are definately problematic.
>>
>> --__MSBROWSE__-
>>
>> Domain Master Browser
>>
>> File Server
>>
>> Domain Controller
>>
>> and so on. What can I do to setup static entries for these
>> because noone has access to that backup network and those
>> ip's will not work. It is definately causing issues with
>> browsing through network neighborhood because you cannot
>> see all the workstations just the servers that are on the
>> backup network. Thanks for your help. Eric
>>
>>
>>
>
>
>.
>

Multihomed Issues with Windows NT
http://support.microsoft.com/default...b;en-us;181774


"Eric Hughes" <(E-Mail Removed)> wrote in message
news:
> The backup network is on a different subnet. It is
> specifically for doing tape backups during production
> hours. That way the backups dont have any impact on
> fileserver or database performance over the network. The
> production network is 155.100.176 and the backup network is
> 192.168.1. I am still confused to say the least.
> Thanks ERic

I appreciate the link but these are very outdated articles
as they are written for nt4.0 and 3.51. Are there any
other things that I can try. Thanks Eric


>-----Original Message-----
>Multihomed Issues with Windows NT
>http://support.microsoft.com/default...b;en-us;181774
>
>
>"Eric Hughes" <(E-Mail Removed)> wrote
in message
>news:
>> The backup network is on a different subnet. It is
>> specifically for doing tape backups during production
>> hours. That way the backups dont have any impact on
>> fileserver or database performance over the network. The
>> production network is 155.100.176 and the backup network is
>> 192.168.1. I am still confused to say the least.
>> Thanks ERic
>
>
>.
>

The browser service is an NT legacy application. There are no new articles
because the browser service in w2k/2003 is essentially identical to NT4 .

If the backup network will work without Netbios over TCP/IP and
browsing, you could try disabling Netbt on the 192.168 NICs. But if you
need Netbt and browsing for backups, you are in a spot. The DCs cannot be
master browsers for both subnets at the same time.

"Eric Hughes" <(E-Mail Removed)> wrote in message
news:1d1101c4acb4$4ddb87a0$(E-Mail Removed)...
>I appreciate the link but these are very outdated articles
> as they are written for nt4.0 and 3.51. Are there any
> other things that I can try. Thanks Eric
>
>
>>-----Original Message-----
>>Multihomed Issues with Windows NT
>>http://support.microsoft.com/default...b;en-us;181774
>>
>>
>>"Eric Hughes" <(E-Mail Removed)> wrote
> in message
>>news:
>>> The backup network is on a different subnet. It is
>>> specifically for doing tape backups during production
>>> hours. That way the backups dont have any impact on
>>> fileserver or database performance over the network. The
>>> production network is 155.100.176 and the backup network is
>>> 192.168.1. I am still confused to say the least.
>>> Thanks ERic
>>
>>
>>.
>>