Windows 2003 DC not able to browse network (long-ish post)

[Newbie]

Hello all,

We have what I think is a master browser issue on a new Windows 2003
Server that is really really annoying me.

Our set-up is mixed 2000 and 2003 - but the new AD integrated 2003
server cannot "net view"
System error 6118 has occurred.

The list of servers for this workgroup is not currently available

Using net view with UNC is fine
Net view \\other_dc

From Network Neighbourhood - Browse our Domain - times out with
standard blurb of:
<DOMAIN> is not accessible. You might not have permission to use this
network resource….. The list of servers for this workgroup is not
currently available

I have stopped the two other W2K DCs from becoming master browsers
(via registry) - they still see the network servers correctly.

I am reasonable confident the DNS and AD is okay - we can force
replication for AD for any DC and all okay, DNS servers records are
reflected correctly across all servers.

All other W2K3 servers (running Terminal Services - but not DC's or
anything else interesting) cannot net view or browse properly either,
all W2K machine can.

LATEST UPDATE (after much troubleshooting) - I transfered the FSMO
roles to the 2003 DC and I can now browse the network from that DC
(great!)
Using browstat sta from any DC (either 2000 or 2003) now works and
reports the 2003 DC and master browser.

But no joy for other 2003 server - so if I disjoin and then rejoin a
2003 member server using on the 2003 DC as the DNS to use it rejoins
fine, but still cannot browse.

I have also tried setting the Domain controller security policy
settings for Microsoft Network Client: Digitally sign communications
(Always) &
Microsoft Network Server: Digitally sign communications (Always) to
Disabled.
No joy.

Furthermore:
1) These are all on the same subnet - so not that problem either!
2) Other suggestions of disabling NIC firewall have been double
checked - they are not enabled.
3) We are not using WINS or LMHOSTS and don't want to really


I would really really appreciate some help on this

Cheers,

Greg

 

[Eric Chamberlain, CISSP]

If you're not using WINS or LMHOSTS files, why bother with NetBIOS at all?
Search AD for your resources, instead of browsing the network.

 

[Newbie]

Hi Eric,

Thanks for you response - I understand what you are saying, BUT
browsing for resources via Network Neighbourhood is something users
expect to be able to do -and the first place they normally check.

It is kinda hard to sell Windows 2003 and being "better" than 2000
when users perceive that they are losing something they use all the
time.

Cheers,

Greg

 

[Simon Geary]

You need WINS to browse Network Neighbourhood. There are new ways of
searching for resources in Active Directory so this sounds like a case of
user education and the difficult task of changing the way people work.