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!

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!

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@newsgroup

> 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!

>
>

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/l...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@newsgroup
>

>> 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!

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@newsgroup

> 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/l...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@newsgroup
>>

>>> 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!

>
>

Hello Gregg Hill" greggmhill at please do not spam me at yahoo dot com,

Now i am a bit confused, as in the first posting you wrote about a single
label domain name and now it isn't according to (It
had a "dot domain")?

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

> 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!
> 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@newsgroup
>

>> 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/l...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\Parameter
>>> s\ 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@newsgroup
>>>> 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!

No, it had a "dot domain" in DNS in addition to its single label domain name
AND it is a single label domain AND it had the ISP's DNS servers instead of
its own IP address in the NIC properties. The dot domain has been deleted
and proper DNS for the NIC is fixed, but it is still a single label domain.

Triple play! Strike three, I am OUT!

Gregg



--
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:6cb2911dd7c48cc7b26686bc821@newsgroup

> Hello Gregg Hill" greggmhill at please do not spam me at yahoo dot com,
>
> Now i am a bit confused, as in the first posting you wrote about a single
> label domain name and now it isn't according to (It had a "dot domain")?
>
> 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
>

>> 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!
>> 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@newsgroup
>>

>>> 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/l...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\Parameter
>>>> s\ 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@newsgroup
>>>>> 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!

>
>

When I first ran dcdiag and netdiag, there were too many errors to even
bother checking, as I knew most likely were caused by the ISP's DNS servers
being used and the dot domain (properly called the "root zone" per
http://support.microsoft.com/kb/298148). It had no root hints, forwarders
were grayed out and empty, etc. I now have a completely error-free dcdiag
and netdiag output.

However, as you can see from the start of the netdiag command, the domain
has no suffix, hence it being a single label domain name.

D:\Program Files\Support Tools>netdiag /q
......................................

Computer Name: RKSERVER1
DNS Host Name: RKSERVER1.rknet1
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 6 Model 11 Stepping 1, GenuineIntel
List of installed hotfixes :

Here is the ipconfig output:

D:\Program Files\Support Tools>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : RKSERVER1
Primary DNS Suffix . . . . . . . : rknet1
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : rknet1

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Network
Connect
ion
Physical Address. . . . . . . . . : 00-C0-9F-90-A2-BB
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.254.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.254.1
DNS Servers . . . . . . . . . . . : 192.168.254.200


When I do that on my SBS 2003 server or a client's SBS 2000 server (yikes!),
I see a domain with a suffix.


C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : sbs2003
Primary Dns Suffix . . . . . . . : hillservices.internal
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : hillservices.internal

Ethernet adapter Server LAN Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 GT Desktop Adapter
Physical Address. . . . . . . . . : 00-0E-0C-A0-F5-52
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.4
DNS Servers . . . . . . . . . . . : 192.168.16.10
Primary WINS Server . . . . . . . : 192.168.16.10


I now need to research to see if I can create a trust between the two
servers. My only other option is to take all the workstations (14 of them)
off of the old domain, join the new domain, demote the Win 2000 to a
stand-alone, and then join it to the 2008 domain as a member server so that
they can still use some law apps that are not yet 64-bit compatible.

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:6cb2911dd7c48cc7b26686bc821@newsgroup

> Hello Gregg Hill" greggmhill at please do not spam me at yahoo dot com,
>
> Now i am a bit confused, as in the first posting you wrote about a single
> label domain name and now it isn't according to (It had a "dot domain")?
>
> 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
>

>> 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!
>> 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@newsgroup
>>

>>> 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/l...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\Parameter
>>>> s\ 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@newsgroup
>>>>> 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!

>
>

Regarding the trust relationship, I first tried it (after the DNS fixes)
from the Win 2000 server and it kept failing. So, I tried from the 2008
server with its wizard, and it took less than a minute to create. It says
that it confirmed it in both directions, and the settings show up on both
servers. I will go back on Monday to check how it is working, then start in
on new workstations.

So far, things look good!

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:6cb2911dd7c48cc7b26686bc821@newsgroup

> Hello Gregg Hill" greggmhill at please do not spam me at yahoo dot com,
>
> Now i am a bit confused, as in the first posting you wrote about a single
> label domain name and now it isn't according to (It had a "dot domain")?
>
> 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
>

>> 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!
>> 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@newsgroup
>>

>>> 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/l...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\Parameter
>>>> s\ 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@newsgroup
>>>>> 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!

>
>

Hello Gregg Hill" greggmhill at please do not spam me at yahoo dot com,

I was just confused from your description.

Using the ip address of the ISPs DNS server on the NIC, especially on a DC
will create problems. You should always use only the domain DNS server on
the NIC and configure the FORWARDERS on the DNS server properties in the
DNS management console. To configure the Forwarders the root (.) has to be
deleted first in the DNS management console, as you stated in your postings
also.

As you mentioned SBS versions in your postings, hopefully the Windows server
2000 or Windows server 2008 are NOT SBS versions. A SBS server isn't able
to create a trust to another forest/domain, one of it's limitations.

To create a trust between the normal versions make sure there is no firewall
activated, default on Windows server 2008. Also see this article, if you
scroll down Windows server 2000 is also mentioned:
http://support.microsoft.com/kb/942564

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

> No, it had a "dot domain" in DNS in addition to its single label
> domain name AND it is a single label domain AND it had the ISP's DNS
> servers instead of its own IP address in the NIC properties. The dot
> domain has been deleted and proper DNS for the NIC is fixed, but it is
> still a single label domain.
>
> Triple play! Strike three, I am OUT!
>
> Gregg
>
> 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:6cb2911dd7c48cc7b26686bc821@newsgroup
>

>> Hello Gregg Hill" greggmhill at please do not spam me at yahoo dot
>> com,
>>
>> Now i am a bit confused, as in the first posting you wrote about a
>> single label domain name and now it isn't according to (It had a "dot
>> domain")?
>>
>> 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

>>> 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!
>>> 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@newsgroup
>>>> 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/l...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\Paramet
>>>>> er s\ 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@newsgroup
>>>>>> 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!