From: "Gregg Hill" greggmhill at please do not spam me at yahoo dot on
Hello!

I have a new client who had a Win 2000 server set up years ago and it was
set up with a "single label" domain having no domain suffix, a "dot" domain,
and DNS pointing to the ISP's DNS servers. I ran into one of these YEARS ago
and found a script that corrected the single label domain issue. I then
fixed the rest of it. At least, I think that is how it went...MANY moons
ago.

For the life of me (I've been Googling for hours), I cannot find an article
on how to FIX a single label domain. There are a ton of articles regarding
doing workarounds to clients, but that is not my goal. I want to fix it so
that AD works properly. I thought it had something to do with changing a
registry setting and then running a VB script, possibly the one listed here
http://support.microsoft.com/kb/257623.

This is a single server domain, just Windows 2000 Server Standard without
Exchange. After I fix it, I will add a Windows 2008 R2 server.

Any ideas?

Thank you!

Gregg Hill


--
Gregg's pet peeves:

First of all, what does a peeve look like, and why would anyone want one as
a pet?

Peeve #1: Apostrophes: when in doubt, leave them out! You will be correct
more often than not.

Its = Belonging to it. For example, "Look at the sky. Its color is blue."
It's = It is. For example, "It's hot today."
It's = It has. For example, "It's been nice talking to you."
Its' = completely incorrect usage. Stop it!


Peeve #2: Your vs. You're
"Your" means belonging to you, as in, "It's your truck."
"You're" means "You are." Example, you're probably about ready to throttle
me for this peeve!

From: Meinolf Weber [MVP-DS] on
Hello Gregg Hill,

Maybe this helps you further:
http://support.microsoft.com/kb/300684

Basically you cannot really fix it without renaming the domain, which isn't
possible within windows server 2000. So i would think about using ADMT to
migrate to Windows server 2008 with the correct name, that way it will be
safe for the future.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello!
>
> I have a new client who had a Win 2000 server set up years ago and it
> was set up with a "single label" domain having no domain suffix, a
> "dot" domain, and DNS pointing to the ISP's DNS servers. I ran into
> one of these YEARS ago and found a script that corrected the single
> label domain issue. I then fixed the rest of it. At least, I think
> that is how it went...MANY moons ago.
>
> For the life of me (I've been Googling for hours), I cannot find an
> article on how to FIX a single label domain. There are a ton of
> articles regarding doing workarounds to clients, but that is not my
> goal. I want to fix it so that AD works properly. I thought it had
> something to do with changing a registry setting and then running a VB
> script, possibly the one listed here
> http://support.microsoft.com/kb/257623.
>
> This is a single server domain, just Windows 2000 Server Standard
> without Exchange. After I fix it, I will add a Windows 2008 R2 server.
>
> Any ideas?
>
> Thank you!
>
> Gregg Hill
>
> First of all, what does a peeve look like, and why would anyone want
> one as a pet?
>
> Peeve #1: Apostrophes: when in doubt, leave them out! You will be
> correct more often than not.
>
> Its = Belonging to it. For example, "Look at the sky. Its color is
> blue."
> It's = It is. For example, "It's hot today."
> It's = It has. For example, "It's been nice talking to you."
> Its' = completely incorrect usage. Stop it!
> Peeve #2: Your vs. You're
> "Your" means belonging to you, as in, "It's your truck."
> "You're" means "You are." Example, you're probably about ready to
> throttle
> me for this peeve!


From: "Gregg Hill" greggmhill at please do not spam me at yahoo dot on
Meinolf,

That is one of the articles to which I was referring when I mentioned that
they say how to make a client workaround.

I am going back today to make sure it is not just a DNS problem. When I look
at the computer properties on the Network Identification tab, it shows the
"Full computer name" as

rkserver.rknet1.

where it should be

rkserver.rknet1.local or some other suffix.

In this case, there is NO suffix.

An ipconfig /all shows

Primary Dns Suffix . . . . . . . : rknet1

without a suffix. Because it is a domain controller, I cannot get to the
normal spot to change the DNS suffix, i.e., the "Change primary DNS suffix
when domain membership changes" check box, but it can be done in the
registry (at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\NV
Domain), which I believe is what I did many years ago on another botched Win
2000 setup.

Ultimately, I want to add a Windows Server 2008 R2 server and make it the
DC, move all data, and then format and make the Win 2000 a terminal server
(as a member server). They also want to get 14 new Windows 7 workstations,
but not all at once, so I have to keep the old Windows 2000 Pro workstations
on line.

At first, I thought I could create a whole new properly-configured domain on
the 2008 server, create a trust between the two, and be on my way. However,
the botched DNS and the (possible) single label domain name are preventing
the trust. Running dcdiag and netdiag have them throwing up all over
themselves, due at least to the "dot" domain and the DNS pointing to their
ISP's DNS servers. Dumping the "dot" domain and fixing the DNS to point to
itself is no big deal and I will do that today, but I need to get the domain
to show a suffix in DNS, too. This problem MAY just be that DNS is screwed
up and not showing the suffix. I have to take a closer look today.

Gregg Hill


--
Gregg's pet peeves:

First of all, what does a peeve look like, and why would anyone want one as
a pet?

Peeve #1: Apostrophes: when in doubt, leave them out! You will be correct
more often than not.

Its = Belonging to it. For example, "Look at the sky. Its color is blue."
It's = It is. For example, "It's hot today."
It's = It has. For example, "It's been nice talking to you."
Its' = completely incorrect usage. Stop it!


Peeve #2: Your vs. You're
"Your" means belonging to you, as in, "It's your truck."
"You're" means "You are." Example, you're probably about ready to throttle
me for this peeve!

"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
news:6cb2911dd7828cc7a9dc799863c(a)msnews.microsoft.com...
> Hello Gregg Hill,
>
> Maybe this helps you further:
> http://support.microsoft.com/kb/300684
>
> Basically you cannot really fix it without renaming the domain, which
> isn't possible within windows server 2000. So i would think about using
> ADMT to migrate to Windows server 2008 with the correct name, that way it
> will be safe for the future.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Hello!
>>
>> I have a new client who had a Win 2000 server set up years ago and it
>> was set up with a "single label" domain having no domain suffix, a
>> "dot" domain, and DNS pointing to the ISP's DNS servers. I ran into
>> one of these YEARS ago and found a script that corrected the single
>> label domain issue. I then fixed the rest of it. At least, I think
>> that is how it went...MANY moons ago.
>>
>> For the life of me (I've been Googling for hours), I cannot find an
>> article on how to FIX a single label domain. There are a ton of
>> articles regarding doing workarounds to clients, but that is not my
>> goal. I want to fix it so that AD works properly. I thought it had
>> something to do with changing a registry setting and then running a VB
>> script, possibly the one listed here
>> http://support.microsoft.com/kb/257623.
>>
>> This is a single server domain, just Windows 2000 Server Standard
>> without Exchange. After I fix it, I will add a Windows 2008 R2 server.
>>
>> Any ideas?
>>
>> Thank you!
>>
>> Gregg Hill
>>
>> First of all, what does a peeve look like, and why would anyone want
>> one as a pet?
>>
>> Peeve #1: Apostrophes: when in doubt, leave them out! You will be
>> correct more often than not.
>>
>> Its = Belonging to it. For example, "Look at the sky. Its color is
>> blue."
>> It's = It is. For example, "It's hot today."
>> It's = It has. For example, "It's been nice talking to you."
>> Its' = completely incorrect usage. Stop it!
>> Peeve #2: Your vs. You're
>> "Your" means belonging to you, as in, "It's your truck."
>> "You're" means "You are." Example, you're probably about ready to
>> throttle
>> me for this peeve!
>
>
From: Meinolf Weber [MVP-DS] on
Hello Gregg Hill" greggmhill at please do not spam me at yahoo dot com,

I have never heard about fixing the single label domain name problem with
a registry key for the DC/domain itself. Maybe you are mixing the disjoint
namespace problem with this? That can be solved with a change in the registry
keys.
http://technet.microsoft.com/en-us/library/aa998420(EXCHG.80).aspx

The only way i know is domain renaming and following the article i already
posted for the domain members.

The trust can only be created if the domain names are different, is that
the case? Please post an unedited ipconfig /all from both DCs so we can also
check this ones.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Meinolf,
>
> That is one of the articles to which I was referring when I mentioned
> that they say how to make a client workaround.
>
> I am going back today to make sure it is not just a DNS problem. When
> I look at the computer properties on the Network Identification tab,
> it shows the "Full computer name" as
>
> rkserver.rknet1.
>
> where it should be
>
> rkserver.rknet1.local or some other suffix.
>
> In this case, there is NO suffix.
>
> An ipconfig /all shows
>
> Primary Dns Suffix . . . . . . . : rknet1
>
> without a suffix. Because it is a domain controller, I cannot get to
> the normal spot to change the DNS suffix, i.e., the "Change primary
> DNS suffix when domain membership changes" check box, but it can be
> done in the registry (at
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
> NV Domain), which I believe is what I did many years ago on another
> botched Win 2000 setup.
>
> Ultimately, I want to add a Windows Server 2008 R2 server and make it
> the DC, move all data, and then format and make the Win 2000 a
> terminal server (as a member server). They also want to get 14 new
> Windows 7 workstations, but not all at once, so I have to keep the old
> Windows 2000 Pro workstations on line.
>
> At first, I thought I could create a whole new properly-configured
> domain on the 2008 server, create a trust between the two, and be on
> my way. However, the botched DNS and the (possible) single label
> domain name are preventing the trust. Running dcdiag and netdiag have
> them throwing up all over themselves, due at least to the "dot" domain
> and the DNS pointing to their ISP's DNS servers. Dumping the "dot"
> domain and fixing the DNS to point to itself is no big deal and I will
> do that today, but I need to get the domain to show a suffix in DNS,
> too. This problem MAY just be that DNS is screwed up and not showing
> the suffix. I have to take a closer look today.
>
> Gregg Hill
>
> First of all, what does a peeve look like, and why would anyone want
> one as a pet?
>
> Peeve #1: Apostrophes: when in doubt, leave them out! You will be
> correct more often than not.
>
> Its = Belonging to it. For example, "Look at the sky. Its color is
> blue."
> It's = It is. For example, "It's hot today."
> It's = It has. For example, "It's been nice talking to you."
> Its' = completely incorrect usage. Stop it!
> Peeve #2: Your vs. You're
> "Your" means belonging to you, as in, "It's your truck."
> "You're" means "You are." Example, you're probably about ready to
> throttle
> me for this peeve!
> "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
> news:6cb2911dd7828cc7a9dc799863c(a)msnews.microsoft.com...
>
>> Hello Gregg Hill,
>>
>> Maybe this helps you further:
>> http://support.microsoft.com/kb/300684
>> Basically you cannot really fix it without renaming the domain, which
>> isn't possible within windows server 2000. So i would think about
>> using ADMT to migrate to Windows server 2008 with the correct name,
>> that way it will be safe for the future.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Hello!
>>>
>>> I have a new client who had a Win 2000 server set up years ago and
>>> it was set up with a "single label" domain having no domain suffix,
>>> a "dot" domain, and DNS pointing to the ISP's DNS servers. I ran
>>> into one of these YEARS ago and found a script that corrected the
>>> single label domain issue. I then fixed the rest of it. At least, I
>>> think that is how it went...MANY moons ago.
>>>
>>> For the life of me (I've been Googling for hours), I cannot find an
>>> article on how to FIX a single label domain. There are a ton of
>>> articles regarding doing workarounds to clients, but that is not my
>>> goal. I want to fix it so that AD works properly. I thought it had
>>> something to do with changing a registry setting and then running a
>>> VB script, possibly the one listed here
>>> http://support.microsoft.com/kb/257623.
>>>
>>> This is a single server domain, just Windows 2000 Server Standard
>>> without Exchange. After I fix it, I will add a Windows 2008 R2
>>> server.
>>>
>>> Any ideas?
>>>
>>> Thank you!
>>>
>>> Gregg Hill
>>>
>>> First of all, what does a peeve look like, and why would anyone want
>>> one as a pet?
>>>
>>> Peeve #1: Apostrophes: when in doubt, leave them out! You will be
>>> correct more often than not.
>>>
>>> Its = Belonging to it. For example, "Look at the sky. Its color is
>>> blue."
>>> It's = It is. For example, "It's hot today."
>>> It's = It has. For example, "It's been nice talking to you."
>>> Its' = completely incorrect usage. Stop it!
>>> Peeve #2: Your vs. You're
>>> "Your" means belonging to you, as in, "It's your truck."
>>> "You're" means "You are." Example, you're probably about ready to
>>> throttle
>>> me for this peeve!


From: "Gregg Hill" greggmhill at please do not spam me at yahoo dot on
This is a single server domain and was set up by an old school NT guy. It
had a
"dot domain" and it was pointing to the ISP's DNS servers, and both of those
errors have been corrected today. I now have only one error in either dcdiag
or
netdiag, and that is a warning that the File Replication Service is not
running.

In ADUC, instead of showing a domain with a suffix, such as rknet1.lan, it
only
shows "rknet1" as the domain name. Same thing for AD Domains and Trusts.

There are DNS resolution issues still, as I can ping by NetBIOS name from
the
old "rkserver1" to the new server's "dc01" name or by IP, but not by the new
server's FQDN of dc01.office.lan.

It is an AD integrated server, but the server name is listed as on the SOA
and Name Servers tabs as "rkserver1.rknet1." instead of having an FQDN such
as
"rkserver1.rknet1.lan" for the name. It's missing the domain suffix.

I am setting up LogMeIn Rescue so I can work remotely...it's time for lunch
and play
with wife time!

I will look at fixing the missing DNS suffix and hope that it will work in
spite of being a single label domain. I have a few articles that show how to
do it.

http://support.microsoft.com/kb/888048

This one may have something to do with it as well:
http://support.microsoft.com/kb/257623



Once I get the name resolution, I'll try to set up a trust. If that fails,
I'll
be forced to punt!


--
Gregg's pet peeves:

First of all, what does a peeve look like, and why would anyone want one as
a pet?

Peeve #1: Apostrophes: when in doubt, leave them out! You will be correct
more often than not.

Its = Belonging to it. For example, "Look at the sky. Its color is blue."
It's = It is. For example, "It's hot today."
It's = It has. For example, "It's been nice talking to you."
Its' = completely incorrect usage. Stop it!


Peeve #2: Your vs. You're
"Your" means belonging to you, as in, "It's your truck."
"You're" means "You are." Example, you're probably about ready to throttle
me for this peeve!

"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
news:6cb2911dd7ab8cc7af91127b453(a)msnews.microsoft.com...
> Hello Gregg Hill" greggmhill at please do not spam me at yahoo dot com,
>
> I have never heard about fixing the single label domain name problem with
> a registry key for the DC/domain itself. Maybe you are mixing the disjoint
> namespace problem with this? That can be solved with a change in the
> registry keys.
> http://technet.microsoft.com/en-us/library/aa998420(EXCHG.80).aspx
>
> The only way i know is domain renaming and following the article i already
> posted for the domain members.
>
> The trust can only be created if the domain names are different, is that
> the case? Please post an unedited ipconfig /all from both DCs so we can
> also check this ones.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Meinolf,
>>
>> That is one of the articles to which I was referring when I mentioned
>> that they say how to make a client workaround.
>>
>> I am going back today to make sure it is not just a DNS problem. When
>> I look at the computer properties on the Network Identification tab,
>> it shows the "Full computer name" as
>>
>> rkserver.rknet1.
>>
>> where it should be
>>
>> rkserver.rknet1.local or some other suffix.
>>
>> In this case, there is NO suffix.
>>
>> An ipconfig /all shows
>>
>> Primary Dns Suffix . . . . . . . : rknet1
>>
>> without a suffix. Because it is a domain controller, I cannot get to
>> the normal spot to change the DNS suffix, i.e., the "Change primary
>> DNS suffix when domain membership changes" check box, but it can be
>> done in the registry (at
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
>> NV Domain), which I believe is what I did many years ago on another
>> botched Win 2000 setup.
>>
>> Ultimately, I want to add a Windows Server 2008 R2 server and make it
>> the DC, move all data, and then format and make the Win 2000 a
>> terminal server (as a member server). They also want to get 14 new
>> Windows 7 workstations, but not all at once, so I have to keep the old
>> Windows 2000 Pro workstations on line.
>>
>> At first, I thought I could create a whole new properly-configured
>> domain on the 2008 server, create a trust between the two, and be on
>> my way. However, the botched DNS and the (possible) single label
>> domain name are preventing the trust. Running dcdiag and netdiag have
>> them throwing up all over themselves, due at least to the "dot" domain
>> and the DNS pointing to their ISP's DNS servers. Dumping the "dot"
>> domain and fixing the DNS to point to itself is no big deal and I will
>> do that today, but I need to get the domain to show a suffix in DNS,
>> too. This problem MAY just be that DNS is screwed up and not showing
>> the suffix. I have to take a closer look today.
>>
>> Gregg Hill
>>
>> First of all, what does a peeve look like, and why would anyone want
>> one as a pet?
>>
>> Peeve #1: Apostrophes: when in doubt, leave them out! You will be
>> correct more often than not.
>>
>> Its = Belonging to it. For example, "Look at the sky. Its color is
>> blue."
>> It's = It is. For example, "It's hot today."
>> It's = It has. For example, "It's been nice talking to you."
>> Its' = completely incorrect usage. Stop it!
>> Peeve #2: Your vs. You're
>> "Your" means belonging to you, as in, "It's your truck."
>> "You're" means "You are." Example, you're probably about ready to
>> throttle
>> me for this peeve!
>> "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
>> news:6cb2911dd7828cc7a9dc799863c(a)msnews.microsoft.com...
>>
>>> Hello Gregg Hill,
>>>
>>> Maybe this helps you further:
>>> http://support.microsoft.com/kb/300684
>>> Basically you cannot really fix it without renaming the domain, which
>>> isn't possible within windows server 2000. So i would think about
>>> using ADMT to migrate to Windows server 2008 with the correct name,
>>> that way it will be safe for the future.
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> Hello!
>>>>
>>>> I have a new client who had a Win 2000 server set up years ago and
>>>> it was set up with a "single label" domain having no domain suffix,
>>>> a "dot" domain, and DNS pointing to the ISP's DNS servers. I ran
>>>> into one of these YEARS ago and found a script that corrected the
>>>> single label domain issue. I then fixed the rest of it. At least, I
>>>> think that is how it went...MANY moons ago.
>>>>
>>>> For the life of me (I've been Googling for hours), I cannot find an
>>>> article on how to FIX a single label domain. There are a ton of
>>>> articles regarding doing workarounds to clients, but that is not my
>>>> goal. I want to fix it so that AD works properly. I thought it had
>>>> something to do with changing a registry setting and then running a
>>>> VB script, possibly the one listed here
>>>> http://support.microsoft.com/kb/257623.
>>>>
>>>> This is a single server domain, just Windows 2000 Server Standard
>>>> without Exchange. After I fix it, I will add a Windows 2008 R2
>>>> server.
>>>>
>>>> Any ideas?
>>>>
>>>> Thank you!
>>>>
>>>> Gregg Hill
>>>>
>>>> First of all, what does a peeve look like, and why would anyone want
>>>> one as a pet?
>>>>
>>>> Peeve #1: Apostrophes: when in doubt, leave them out! You will be
>>>> correct more often than not.
>>>>
>>>> Its = Belonging to it. For example, "Look at the sky. Its color is
>>>> blue."
>>>> It's = It is. For example, "It's hot today."
>>>> It's = It has. For example, "It's been nice talking to you."
>>>> Its' = completely incorrect usage. Stop it!
>>>> Peeve #2: Your vs. You're
>>>> "Your" means belonging to you, as in, "It's your truck."
>>>> "You're" means "You are." Example, you're probably about ready to
>>>> throttle
>>>> me for this peeve!
>
>