3 AD Problems -- Probably All related -- Help Plz

  • Thread starter Thread starter Yogi_Bear_79
  • Start date Start date
Y

Yogi_Bear_79

I have newly built Win2k Adv Svr runnin AD. I have it built and all my users
are currently running off of it. My three problesm are:

1.) Users can not use the Add Printer Wizard to connect to printers on the
server. But they can right click them in Windows Explorer and connect and
use them just fine.

2.)If I try to make someone a local admin on their box, I can't browse the
AD, but I can manually type their account and domain info in and it works.

3.) Tried to bring up a BDC today. It won't. First thing I notice is I can't
get past step 1 on the wizard if it uses my fully qualified domain, but If I
just use the domain without suffix it is fine. Same thing happens later
when it asks which domain to be the BDC for. Finally it just fails when
trying to replicate, says it can't connect to the domain it is
non-exisistant.


Help
 
Hi Yogi,

This might seem obvious, but the first thing I'd check is
the DNS settings of your clients. If they're not pointing
to an active DNS server, then you'll likely get problems
similar to what you're describing - particularly the one
with a prospective DC not finding the domain.

I would do the following things: -
1) Make sure that the DNS service is working properly on
your Windows 2000 AD server (or your primary DC if you
have more than one).
2) If you use DHCP, change the scopes to point clients to
your primary Windows 2000 server for DNS (the one running
AD), or change the clients manually if you don't use DHCP.
3) Make sure that your prospective AD server is pointing
solely to the existing AD server for DNS before running
DCPROMO.

Another note that might apply to you. I have on occasion
had a non-AD DNS server in my list of DNS servers for AD
clients. This seems like a good idea for redundancy (so
if your primary server fails the clients can still access
the Internet etc) but has often ended up with niggly
problems occuring on clients. This can happen if for any
reason the client starts accessing the non-AD DNS source
and then has no knowledge of dynamic DNS entries (such as
the AD domain name). If you currently have non-AD DNS
servers on your list of DNS sources for clients (or other
servers), try removing them (even if it's only temporary)
to see if this helps with the problems that you've been
having.

Hope this helps!


Richard Kell
Kell Consulting.
 
Back
Top