Networking Forums  

Go Back   Networking Forums > Networking Newsgroups > Windows Server Networking

Windows 2003 and AD Browsing

Reply
 
Thread Tools Display Modes
  #1  
Old 01-05-2006, 01:46 PM
Default Windows 2003 and AD Browsing



When I attempt to browse my AD using Network Neighborhood (Windows XP
Client). I get the message that the AD is not available for browsing, or I
don't have enough privlidge. I am trying to browse as with a Domain Admin
account.

The Network Neighborhood on the AD Controller see's all the machines on the
network. The AD controller has 2 NICs, on different subnets. It is also
doing DHCP, WINS, and DNS.

I have no issues connecting directly to a machine with \\machinename, but
browsing just isn't working.

Any ideas?


Brian Smith
Reply With Quote
  #2  
Old 01-05-2006, 04:00 PM
Robert L [MS-MVP]
Guest
 
Posts: n/a
Default Re: Windows 2003 and AD Browsing

It is not recommended to install a DC with DNS and WINS on a multihomed computer. otherwise, you may have a computer browsing issue. Any errors in Event Viewer?

Computer Browser
Master Browsing issue on Multihomed DC One computer screw up the network Re-register
NetBIOS name What is NetBT_<driver_name> ...
www.chicagotech.net/browser.htm

Troubleshooting computer browsing issues
Master Browsing issue on Multihomed DC One computer screw up the network The
browser was unable to retrieve a list of servers from the browser master ....
www.chicagotech.net/computerbrowsingissues.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Brian Smith" <(E-Mail Removed)> wrote in message news:B1B60376-2980-48B7-823C-(E-Mail Removed)...
When I attempt to browse my AD using Network Neighborhood (Windows XP
Client). I get the message that the AD is not available for browsing, or I
don't have enough privlidge. I am trying to browse as with a Domain Admin
account.

The Network Neighborhood on the AD Controller see's all the machines on the
network. The AD controller has 2 NICs, on different subnets. It is also
doing DHCP, WINS, and DNS.

I have no issues connecting directly to a machine with \\machinename, but
browsing just isn't working.

Any ideas?
Reply With Quote
  #3  
Old 01-05-2006, 04:01 PM
Herb Martin
Guest
 
Posts: n/a
Default Re: Windows 2003 and AD Browsing

"Brian Smith" <(E-Mail Removed)> wrote in message
news:B1B60376-2980-48B7-823C-(E-Mail Removed)...
> When I attempt to browse my AD using Network Neighborhood (Windows XP
> Client). I get the message that the AD is not available for browsing, or
> I
> don't have enough privlidge.


What specifically do you mean by "browse AD"?

Browsing in Network Neighborhood is COMPLETELY unrelated
to both AD and to permissions.

Only the actual connection to a share (clicking on a server\share)
is dependent on permissions. (Not the browsing itself.)

The only relationship to a domain (e.g., AD) is that the servers
are displayed/maintained on a per domain (master browser etc)
basis.

> I am trying to browse as with a Domain Admin account.


If you are trying to connect to the shares after browsing then
most likely you have an AUTHENTICATION problem on your
XP machine.

Practically all such authentication (and replication too) problems
are REALLY DNS PROBLEMS.

> The Network Neighborhood on the AD Controller see's all the machines on
> the
> network.


That is based on NetBIOS (broadcasts and WINS server).

> The AD controller has 2 NICs, on different subnets. It is also
> doing DHCP, WINS, and DNS.


Two NICs CAN be problematic for a DC/WINS server but I
have generally been able to get it to work just fine (despite others'
reports of trouble.)

Generally I don't recommend it since so many people seem to have
trouble with that but I would NOT start claiming that this is "your
problem."

> I have no issues connecting directly to a machine with \\machinename, but
> browsing just isn't working.


Well, now I am back to HOW SPECIFICALLY "isn't it working"?

Browsing (showing up in Net Neighborhood) is one function,
name resolution is another, connecting is a third, and authentication
is a fourth (which itself may have name resolution and connectivity
issues.)

Really. Browsing is MUCH more complex than most people
ever imagine. Not difficult, just many different functions that can
fail.

> Any ideas?


For Authentication problems DCDiag (run on EVERY DC) and
NetDIAG (run on affected non-DCs) are your friends.

These are both in Support Tools on the Server CDROM.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Reply With Quote
Reply

Tags
2003, browsing, windows

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT. The time now is 08:18 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.