***HELP***Joining a "Windows server 2003" domain...WTF!?!?

Ok, I hope some of the guys I was talking about this with a little over a
week ago are still around. I was talking about switching the network here
from workgroup to a domain. Anyways, I've set up a test server and
workstation(running xp pro), I created a domain, both machines can ping each
other and share files, on the workstation I entered in the domain's ip for
its dns server, but when I go to join the domain I get the message "A domain
controller for the domain allpriser.test could not be contacted. Ensure that
the domain name is typed correctly." What am I missing here?

"CoolerThanYou" wrote in message
...
Ok, I hope some of the guys I was talking about this with a little over a
week ago are still around. I was talking about switching the network here
from workgroup to a domain. Anyways, I've set up a test server and
workstation(running xp pro), I created a domain, both machines can ping
each
other and share files, on the workstation I entered in the domain's ip for
its dns server, but when I go to join the domain I get the message "A
domain
controller for the domain allpriser.test could not be contacted. Ensure
that
the domain name is typed correctly." What am I missing here?


Almost certainly DNS.
You need to ensure the DNS zones for the domain are set for Dynamic Update,
and contain the domain's records.

On the domain controller, run DCDIAG.
I'll bet it will throw a wobbly about being unable to find anything.

Now go to a client.

Do an ipconfig /all and see what DNS servers are listed.
It should only be the internal DNS servers which host the
domain's records, not an external ISP's DNS server.

Then test the DNS lookup like this:

Go to a command prompt.
Type "nslookup".
Then type "set type=all"
Then type "_ldap._tcp.dc._msdcs.domainname
(where domainname is the name of your domain).

Nslookup returns one or more SRV service location records in the following
format:

hostname.domainname internet address = ipaddress

where 'hostname' is the host name of a domain controller, 'domainname' is
the
domain to which the domain controller belongs, and ipaddress is the domain
controller's Internet Protocol (IP) address.

Then 'exit' will quit you out of nslookup.

Here's a screen-dump of me doing this on an XP machine joined to my domain,
"homenet.local.":

C:\Documents and Settings\Ron.HOMENETnslookup
Default Server: homenetdc01.homenet.local --- check this
Address: 81.187.191.78 --- check this

( Check that the IP address of the DNS server being queried is correct.
You may get a warning if it can't reverse lookup the name of the default
server, this is sloppy but non-fatal. )

set type=all
_ldap._tcp.dc._msdcs.homenet.local.
Server: homenetdc01.homenet.local
Address: 81.187.191.78

_ldap._tcp.dc._msdcs.homenet.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = homenetdc01.homenet.local
homenetdc01.homenet.local internet address = 81.187.191.78
exit

Do you get the same?

--
Best Regards,
Ron Lowe
MS-MVP Windows Networking

I would suspect a DNS issue. If the server is acting as both the domain
controller and the DNS server, from the server, open a command prompt and
type ipconfig /flushdns. When it finishes, type ipconfig /registerdns. Try
and join the domain again. Do you have active directory running?

"CoolerThanYou" wrote:

Ok, I hope some of the guys I was talking about this with a little over a
week ago are still around. I was talking about switching the network here
from workgroup to a domain. Anyways, I've set up a test server and
workstation(running xp pro), I created a domain, both machines can ping each
other and share files, on the workstation I entered in the domain's ip for
its dns server, but when I go to join the domain I get the message "A domain
controller for the domain allpriser.test could not be contacted. Ensure that
the domain name is typed correctly." What am I missing here?

Ok guys, I got it going, unfortunately I made a couple rookie mistakes, but
thats what test labs are for right? It was because I had forgotten to
first add/authorize the DHCP server...that would certainly cause a few
problems eh? Anyways, I just wanted to really thank you guys for your time
and help, its good to know that there are people out there that are willing
to put in some of their own time to help a complete stranger and post
something as long and detailed as Ron Lowe did. I'm sure I'll be posting here
again, now its back to reading "mastering windows 2000 server" bye.