Browsing issues between new AD and old NT4 domain

Giganews Newsgroups
Subject: Browsing issues between new AD and old NT4 domain
Posted by:  DennisMCSE (DennisMC…
Date: Fri, 16 Feb 2007

I have a strange issue. We migrated to a new AD domain at the end of January
(finally joining the corporate AD). Our production floor stayed in the old
NT4 domain and wasn't migrated. Up until Monday of this week, we were able to
browse, through My Network Places>Entire Network>Microsoft Windows Network,
and see all our production workgroups and our old domain. This is how our
engineers connected to the production floor computers to transfer information.

As of Tuesday, going through the same way, all we can see is the AD domain.
We can no longer view the production floor computers or our old domain. AD
points to the WINS server in the old domain. We didn't have any network
issues on Monday. We can still manually map a drive to the computers, but
with the number of computers on the production floor, the engineers will have
about 20 drive mappings.

In the Event Log, I see an Error and a Warning related to the Browse service:

Event Type: Error
Event Source: BROWSER
Event Category: None
Event ID: 8032
Date: 2/13/2007
Time: 2:02:28 PM
User: N/A
Computer: D-XXX-#####
The browser service has failed to retrieve the backup list too many times on
transport \Device\NetBT_Tcpip_{610C229D-36CE-43EF-B618-C0C1C4FD7387}. The
backup browser is stopping.

Event Type: Warning
Event Source: BROWSER
Event Category: None
Event ID: 8021
Date: 2/14/2007
Time: 8:37:48 AM
User: N/A
Computer: D-XXX-#####
The browser was unable to retrieve a list of servers from the browser master
\\L-XXX-##### on the network
\Device\NetBT_Tcpip_{610C229D-36CE-43EF-B618-C0C1C4FD7387}. The data is the
error code.

Also, the production floor is on a separate segment than the AD computers
(the old domain is also on the same segment as the production floor

If I remember correctly, each segment has a random client becoming a Master
Browser for the segment. In NT, the Master Browser in each segment sends it's
browse list to the Domain Master Browser, which in the case of our production
lines is still our old NT4 Domain Controller (although our production lines
are all in separate workgroups and not part of our old NT4 domain, they are
still part of the same segment). All our production machines are still in the
old segment, so all of them can see each other and the browse list in Windows
Explorer works as it should.

But now that we have the AD domain in the building, do the Master Browsers
in each segment also send the browse list information to the AD domain
controller (through the PDC Emulator or whatever)? We added our old domains
NT4 WINS server IP Address to be pushed out by DHCP in AD. So shouldn't the
same information be pulled into AD through WINS so that as computers register
in WINS, they should be accessible in AD? When I look at the database in
WINS, it has listings of all the new AD computers and all the production
machines that we are trying to access from AD computers.