domain rename problem

Hello,

I had to go through a domain rename procedure due to the fact that the name
of the local domain was COMPANY.COM. This was not really acceptable so I
changed it to MYDOMAIN.LOCAL. I made a mistake and changed the netbios name
to MYDOMAIN and then the control server had the same netbios name as the
domain. (MYDOMAIN.COMPANY.COM). So I couldn't log in as a domain admin.
Nevertheless I was able to go through the rename procedure by copying all the
files to a workstation and to DC itself.

The network contains just two servers (windows 2003; DC and a terminal
server, which I used as a "control center") and two XP workstations. DC is
also running Oracle and IIS.

I made a second mistake when I decided to drop the control center from the
domain and rename it. Now I can't join the domain but the situation now is as
follows:

Domain name is MYDOMAIN.LOCAL
The XP workstations are now still SOMETHING.COMPANY.COM, although the
preferred DNS suffix is MYDOMAIN.LOCAL.

DC is also still called DC.COMPANY.COM, preferred DNS suffix is also
COMPANY.COM. If I change it to MYDOMAIN.LOCAL I get userenv error:
"The file must be present at the locatio
<\\mydomain.local\sysvol\mydomain.local\Policies\{ 31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>"

I tried to rename the DC to DC.MYDOMAIN.LOCAL with netdom according to the
instructions
http://www.microsoft.com/technet/pro...081ce62be.mspx

The first step goes well: with Adsiedit.msc I see DC.MYDOMAIN.LOCAL in
msDS-AdditionalDnsHostName
When I make it primary I cannot launch adsiedit anymore = I get errors and
empty fields

Question 1. Should the workstation already have a name
SOMETHING.MYDOMAIN.LOCAL, as it is also there preferred DNS suffix? Should I
add a setting somehow to the DC to allow this or is the problem somewhere
else?

Question 2: How can I change the name of the domain controller? Is there a
similar setting that has to be on eg. allow different name, for the renaming
to work.

Question 3: How can I add the teminal server to the domain? MYDOMAIN.LOCAL
is not reqognized and for COMPANY.COM it says it can locate only the domain.

I'm not very experienced in the windows networking and hence I would
appreciate any advice.

Thank you,

~L~

"~L~" <~L~@discussions.microsoft.com> wrote in message
news:74BB4486-5A0C-421D-A15F-(E-Mail Removed)...
> I had to go through a domain rename procedure due to the fact that the
name
> of the local domain was COMPANY.COM. This was not really acceptable so I
> changed it to MYDOMAIN.LOCAL. I made a mistake and changed the netbios
name

I don't know what to tell you about the main problem,...but this name will
not be accepable if you ever have Macintosh machines. They won't accept a
Top Level Domain Name (last part of the name) that is more than three
letters. I'm not sure if Linux/Unix machines will have the same problem or
not. You should have chosen:

MYDOMAIN.LOC


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

> You should have chosen:
>
> MYDOMAIN.LOC
>

Ahh. Well I guess I'm not going to have any macs there then. I thought
..local was the recommended as it is not registered on the internet:

http://support.microsoft.com/default...296250&GSSNB=1
"Make the name a private domain name that is used for name resolution on the
internal Small Business Server network. This name is usually configured with
the first-level domain of .local. At the present time, the .local domain name
is not registered on the Internet."

But next time I'm renaming a domain ... hopefully never... I will take that
into account

"~L~" <(E-Mail Removed)> wrote in message
news:9F049797-F70D-4250-A1C1-(E-Mail Removed)...
> > You should have chosen:
> >
> > MYDOMAIN.LOC
> >
>
> Ahh. Well I guess I'm not going to have any macs there then. I thought
> .local was the recommended as it is not registered on the internet:

Some of MS products "suggest" it to you, but why would they care of Macs can
use it or not? The reason it is suggested is because it is not registered
on the Internet as you said,...but the same is true for LOC,...and it
follows the Standard of having three letters,...so they really should stop
suggesting Local and start suggesting LOC instead, or at least warn you that
using Local will have compatibility problems.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

The problem was in the DNS. Yeah - I can not follow the instructions ....

I made a new DNS zone for MYDOMAIN.LOCAL and now I was able to join the
domain.
All the computers still believe their names are something.company.com, but
when I can change the name of the DC, I assume it will change. (Machine is
used so I can't do it right now.) AD works ok, so I think I will live after
this.

fingers crossed

I think you can delete the old Zone that doesn't apply anymore. Also with
AD, you just can't do anything fast,...you have to wait for replication to
catch up all the time with new changes.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


"~L~" <(E-Mail Removed)> wrote in message
news:6017C05B-7795-4707-993F-(E-Mail Removed)...
> The problem was in the DNS. Yeah - I can not follow the instructions ....
>
> I made a new DNS zone for MYDOMAIN.LOCAL and now I was able to join the
> domain.
> All the computers still believe their names are something.company.com, but
> when I can change the name of the DC, I assume it will change. (Machine is
> used so I can't do it right now.) AD works ok, so I think I will live
after
> this.
>
> fingers crossed