Re: Cannot join the domain
From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 06/30/04
- Next message: Erik Tamminga: "Re: Cannot connect to computer not joined to domain"
- Previous message: Phillip Windell: "Re: Service stops and freezes apps"
- In reply to: Greg: "Re: Cannot join the domain"
- Next in thread: Greg: "Re: Cannot join the domain"
- Reply: Greg: "Re: Cannot join the domain"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 30 Jun 2004 20:12:10 GMT
Your domain controllers need to have static IP addresses. You can configure a sort of
static IP address by having reservations in the dhcp scope [which they may have] but
I prefer static IP or bad things can happen
A computer will NEVER broadcast for a dns server. If it is not configured to use a
dns server in tcp/ip properties or via a dhcp scope then it can not use a dns server
and can only resort to netbios name resolution unless the hosts file has entries.
Ipconfig /all will show what dns servers a computer is currently using, and looking
in the dhcp scope options will list the dns servers for the scope. What many do, is
INCORRECTLY configure their domain computers with dns server entries for both their
domain controller and their ISP dns server which will cause all kinds of havoc. If
you want to get everything working correctly you need to make sure the domain
controllers have static IP addresses and that W2K/XP Pro computers use only domain
computers for their preferred dns servers. I have not had experience with a single
label dns zone, so I can give limited advice. I suggest you also post in the
win2000.dns newsgroup for best way to proceed from here with the least
sruption. --- Steve
"Greg" <gregb-nospam@hal-pc.org> wrote in message
news:40e2ded7$0$444$be864849@news.hal-mli.net...
> Still working on this problem.
>
> "Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
> news:mxsCc.95529$eu.65743@attbi_s02...
> > You really should use a fully qualified domain for your internal domain
> name.
> I didn't set it up and I have to live with what it is unless someone knows a
> way to change it.
>
> > The biggest mistake in configuring an AD domain is improper dns
> configuration. The
> > domain controller MUST point to itself as it's preferred dns server and
> all domain
> > members and those ready to be joined to the domain must point to an AD
> domain
> > controller running dns [usually they all do]. NEVER point a domain
> computer to an ISP
> > dns server or bad things will happen.
> This may be what is happening. When I enter nslookup, it responds with the
> isp as the default server. What really puzzles me is that we do have some
> computers on the domain and I cannot find anything that is different about
> them; including the response from nslookup. I thought about setting the
> prefered domain controller to the ip of our server; however, it has a
> dynamic ip.
>
> I've been trying to go back to the basics but I'm still not finding
> anything. Correct me if I'm wrong on how it works. First, the computer
> broadcasts over the network looking for an IP address which the DHCP server
> (our router) responds with. Somewhat later when joining the domain, the
> computer then broadcasts looking for the DNS server which the server is
> suppose to respond with. But if the ISPs DNS server is getting set for the
> computers then maybe the local DNS server isn't answer the broadcast. But
> that doesn't seem likely since there are computers that are able to join our
> domain. Perhaps the computers that are on where set to look at the local
> DNS server the changed to find it; however, they still remember where it was
> and keep looking there. Maybe the firewall is stopping us from looking
> stuff up. The guy who's been in charge says he hired people to put the
> computers on the network that are on. He also told me that the reason I was
> having trouble ping is that the firewall stops pings. I don't see how that
> is possible on an internal ping. I can ping IP addresses but not domains.
>
> I'm kind of shooting in the dark on this. I'm a little leery of making
> changes as somethings work now. If I knock off the computers that are on
> then I'm in trouble. About the only thing I can really think of to do is to
> Ghost a computer that is on. But I would really prefer to understand what
> is going on.
>
> Any ideas would be appreciated.
>
> Greg
>
>
>
>
- Next message: Erik Tamminga: "Re: Cannot connect to computer not joined to domain"
- Previous message: Phillip Windell: "Re: Service stops and freezes apps"
- In reply to: Greg: "Re: Cannot join the domain"
- Next in thread: Greg: "Re: Cannot join the domain"
- Reply: Greg: "Re: Cannot join the domain"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
