NT to 2K3 migration - Problem with existing NetBios NT domain Name
- From: "Hank Townsend" <HankTownsend@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 May 2005 05:24:06 -0700
Problem with existing NetBios NT domain Name
Situation:
Eight years ago before receiving any training on Windoes NT server, I setup
the first company primary domain controller running Windows NT 4.0.
Unfortunately, I gave the domain a name of "mgtamer.com" (notice the dot in
the NetBios name). NT allowed this NetBios name.
Problem:
I am now planning to upgrade mgtamer.com from NT to Server 2003. I would
prefer an upgrade to minimize the impact on users. The problem is that 2003
will not accept the "dot" in the NetBios name. The upgrade will appear to
work perfectly (including installing DNS and AD) except that DNS will not
resolve to outside names plus I cannot build a new 2003 server from scratch
and join it to the domain. Resolving internal DNS does work. I have created a
test domain without the dot in the name, run an upgrade and everything works
so I know that the dot in the name is causing the problem.
Need:
I need a work around solution where I can keep the dot in the domain name
but have DNS resolving to the outside and have the ability to add new servers
to the domain.
--
Hank Townsend
.
- Follow-Ups:
- RE: NT to 2K3 migration - Problem with existing NetBios NT domain Name
- From: Amanda Wang [MSFT]
- RE: NT to 2K3 migration - Problem with existing NetBios NT domain Name
- Prev by Date: RE: Trust Relationships problem nt4->2003
- Next by Date: Is it possible to have two separate independent domains on one network?
- Previous by thread: NT4 password migration to WIN 2003
- Next by thread: RE: NT to 2K3 migration - Problem with existing NetBios NT domain Name
- Index(es):
Relevant Pages
|
Loading