Re: Cannot join the domain
From: Greg (gregb-nospam_at_hal-pc.org)
Date: 06/30/04
- Next message: Jeff Strubberg: "RE: Documents on network open as read only"
- Previous message: serverguy: "Re: Windows Update (2000 server XP Pro clients)"
- Next in thread: Steven L Umbach: "Re: Cannot join the domain"
- Reply: Steven L Umbach: "Re: Cannot join the domain"
- Reply: Fran: "Re: Cannot join the domain"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 30 Jun 2004 10:40:20 -0500
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: Jeff Strubberg: "RE: Documents on network open as read only"
- Previous message: serverguy: "Re: Windows Update (2000 server XP Pro clients)"
- Next in thread: Steven L Umbach: "Re: Cannot join the domain"
- Reply: Steven L Umbach: "Re: Cannot join the domain"
- Reply: Fran: "Re: Cannot join the domain"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|