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

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Eric Chamberlain, CISSP (eric.chamberlain_at_newsgroups.nospam)
Date: 06/08/04 

Date: Mon, 7 Jun 2004 18:03:25 -0700

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. 

-- 
Eric Chamberlain, CISSP
"Newbie" <gregholroyd@hotmail.com> wrote in message
news:95b30c37.0406070420.59975568@posting.google.com...
> 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

Relevant Pages

  • Re: Fully parallel Scheme-based language w/ evaluator
    ... Windows Server 2003 and networks in simple - and irreverent - terms. ... If networking really is a big deal, ... Concepts and Terminology in Part I, and The Design and Deployment of Network ...
    (comp.lang.misc)
  • Re: How to connect the NT4 PCD from windows 2003 server
    ... internal is on top of external on the network connection ... for lmhosts files on NT4 server, ... >> type glcdom, which is my NT4 domain controller name, it ...
    (microsoft.public.win2000.security)
  • Re: Outgoing POP3 email missing/lost/not received
    ... Funny thing is that I have had this ISP for 8 years and it has always been ... It looks like when you last ran CEICW, you set the ISP's mail server to: ... Internet Connection Wizard. ... After the wizard completes, the following network connection ...
    (microsoft.public.windows.server.sbs)
  • Re: proper naming of a domain
    ... The primary reason for not being able to see resources/browse etc during a VPN is that the IPschema of remote network is the same as the LAN that you are connecting to. ... from home I can Connect to the server and it tells me that I am connect to ... resources it tells me that the path cannot be found. ...
    (microsoft.public.windows.server.sbs)
  • Re: Logon Server Unavailable
    ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
    (microsoft.public.windows.server.general)