Vista Business Joining a Domain

reaser · Post by **reaser** » Sun Apr 05, 2009 10:51 pm

I keep getting an error message when trying to join the domain. I have about 8 computers running XP Pro SP3 with no issues. Now I have to add a Vista Business machine and it won't join the domain.

I get this error message.

I've googled this and I have disabled the IPv6. I have also double checked the Primary DNS address is correct. Again, I have no issues joining the domain with Windows XP Pro. Vista firewall is disabled.

Any suggestions? This is driving me nuts.

Post by **YeOldeStonecat** » Mon Apr 06, 2009 6:16 am

I've only seen that when the DNS is incorrect. can try typing in the FQDN as well as the netbios name of the domain.

reaser · Post by **reaser** » Mon Apr 06, 2009 9:17 am

The issue was with DNS as I've had problems with DNS entries for some time. I had a conflict where the extension was .net and it should have been .local.

I deleted that zone and created the .local and it worked fine.

Could you possible point me in the direction of good DNS configuration documentation.

Thanks

Post by **YeOldeStonecat** » Tue Apr 07, 2009 12:42 pm

reaser wrote:The issue was with DNS as I've had problems with DNS entries for some time. I had a conflict where the extension was .net and it should have been .local.

I deleted that zone and created the .local and it worked fine.

Could you possible point me in the direction of good DNS configuration documentation.

Thanks

What is the FQDN on this domain? You had a similar thread about this I think around a year ago, stemming from either a website or email, right?

bilbus · Post by **bilbus** » Tue Apr 07, 2009 3:51 pm

99% of the time this is caused by somone having public dns in their tcp-ip config.

Note, there is nothing wrong with having your domain being a .com or .net

Post by **YeOldeStonecat** » Tue Apr 07, 2009 4:54 pm

bilbus wrote:
Note, there is nothing wrong with having your domain being a .com or .net

But it can lead to complications in such that he had before..like e-mail not functioning when it's hosted on POP3 internet servers, or website on a public website not resolving. Then steps should be made to create proper WWW and mail records on the internal DNS. I think some odd stuff was done instead though, like deleting the zone and creating a new .local zone...in which case AD would be tanked if AD was built in .com or .net and not .local. Can't just go nilly willy whacking DNS with a hacksaw like that.

bilbus · Post by **bilbus** » Wed Apr 08, 2009 7:06 pm

If he ran in to complications, he did not set it up correctly.

you can rename your domain just fine in a 2003 native mode domain.

Either way, there is no reason to change to or from .local.

But yes, he may have done something stupid like deleting his zone file.

Post by **YeOldeStonecat** » Thu Apr 09, 2009 6:23 am

Renaming 2003 AD works..but it gets squirrely with SBS..Exchange is involved..and other tightly integrated things.