Wrong AD Domain Config.

Hi ned2

As above, the .local namespace is generally only used for domains that do not serve web content. Our domain is a .local domain, and this extension is recommended during the installation of Active Directory by setup. Therefore, if you do not host a web site you can use the .local extension.

As for DNS, if you wish to join the networked computers to the domain and access the internet, then you must have DNS enabled. You can safely run the DNS wizard from Start>Administartive Tools>DNS.

I don't want to teach you how to suck eggs, but don't worry if you get the DNS setup wrong, you can stop, restart and reconfigure DNS without rebooting the server (well, you can on ours and it's the same as yours).

Good luck

I feel like the broken record now, but everyone is correct about the .local namespace. Here is why:

Lets say your company was named... well... MyCompany.

and your hosted internet PUBLIC web site domain name was mycompany.com handled by the hosting companies DNS.

Now, you name your INTERNAL PRIVATE domain mycompany.com.

When you tried to view your own website at the hosted site, you would get your internal servers. While that can be worked around, being private and internal means you are not really in the "." or ".com" etc namespace. Those are actual namespaces managed and propegated through the internet. There are other reasons, but I find the best anolgy to be: "Why do you use a 192.168.0.x or 10.10.y.z ip subnet instead of 66.215.5.x?"

Because one is for public and one is for private networks.

On the DNS I am confused. You say the namespace is .local and that AD is setup. Other leaned towards it not being installed but I would guess it is. So, what do you mean by not configured? Is it non-existant or no zones or what?

I would leave the Mixed Mode if there are any NT servers and I have know those that wait until there are only NT based clients meaning no 9x or ME.

Good Luck,

razz