RE: NT to 2K3 migration - Problem with existing NetBios NT domain
- From: "Hank Townsend" <HankTownsend@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 12 May 2005 05:06:02 -0700
Actually, Amanda, my current NT NetBios domain name is "mgtamer.com". I was
attempting to make my 2003 DNS domain name "corp.mgtamer.com". The 2003
upgrade of a PDC does not allow me to modify the NetBios name.
In your reference to "2. Rename the existing NT "domain.com" NetBIOS domain
name before the upgrade.", is there a way to do this without having to go to
each workstation to rejoin the domain?
Hank
--
Hank Townsend
"Amanda Wang [MSFT]" wrote:
> Hello,
>
> Thanks for your post.
>
> I understand that you use mgtamer.com Netbios name in NT and after
> upgrading to Server 2003, DNS will not resolve to outside names. If I have
> misunderstood, please feel free to let me know.
>
> Based on my research, for NT has ".com" netbios name, that means the same
> NetBIOS and DNS names, we call this issue as "Perioded Windows NT Domain
> Name" issue.
>
> If you use a perioded domain name (for example, domain.com) as the NETBIOS
> domain name for Windows NT, he may encounter the following problem during
> the in-place upgrade of the Windows NT domain:
>
> "The name "domain.com" is already in use on this network. Type a name that
> is not in use."
>
> Generally speaking, it is a bit difficult to resolve this problem and may
> have many side effects in the long run. We can try only two following
> possible solutions:
>
> 1. Upgrade using a new DNS domain name. (Should work but is not a good
> solution in the long run.)
> 2. Rename the existing NT "domain.com" NetBIOS domain name before the
> upgrade.
>
> For your reference:
>
> 288443 Cannot Use Same NetBIOS Name When You Upgrade a Windows NT 4.0
> Domain to
> http://support.microsoft.com/?id=288443
>
> HTH!
>
> Thanks & Regards
>
> Amanda Wang [MSFT]
>
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> ====================================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================================
>
> --------------------
> >Thread-Topic: NT to 2K3 migration - Problem with existing NetBios NT
> domain Name
> >thread-index: AcVWJFM0eqejBoPYTo+gkc42BCOGKQ==
> >X-WBNR-Posting-Host: 199.44.118.77
> >From: "=?Utf-8?B?SGFuayBUb3duc2VuZA==?="
> <HankTownsend@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Subject: NT to 2K3 migration - Problem with existing NetBios NT domain Name
> >Date: Wed, 11 May 2005 05:24:06 -0700
> >Lines: 28
> >Message-ID: <35197DC1-ACFD-4E38-83BB-193CD4FEF168@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.migration
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10112
> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >
> >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
- From: Amanda Wang [MSFT]
- RE: NT to 2K3 migration - Problem with existing NetBios NT domain
- References:
- NT to 2K3 migration - Problem with existing NetBios NT domain Name
- From: Hank Townsend
- RE: NT to 2K3 migration - Problem with existing NetBios NT domain Name
- From: Amanda Wang [MSFT]
- NT to 2K3 migration - Problem with existing NetBios NT domain Name
- Prev by Date: Move Terminal Services Licensing to new hardware
- Next by Date: Security Translation - Add Mode
- Previous by thread: RE: NT to 2K3 migration - Problem with existing NetBios NT domain Name
- Next by thread: RE: NT to 2K3 migration - Problem with existing NetBios NT domain
- Index(es):
Relevant Pages
|
