RE: after in-place upgrade sql need to re-join domain
- From: "Gaston Durand" <GastonDurand@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 31 May 2005 05:15:17 -0700
Thank you Amanda, I added responses to your questions.
"Amanda Wang [MSFT]" wrote:
> Hello,
>
> Thanks for your post.
>
> I understand the issue is that after in-place upgrade from WinNT to Win2k3,
> SQL need to re-join domain.
>
> First, please help me confirm the issue so that we can isolate the issue
> more efficient:
>
> 1. Do you mean the error of duplicate users found appears when you add a
> user in SQL server, or on the machine which running SQL Server?
When you add the user on the computer, if you add the user to a local group.
SQL users are fine.
> 2. Does the machine a DC which running SQL Server?
the SQL servers are member servers only.
> Based on your post, it seems that the NT domain Netbios name is domain.com,
the initial domain name was not perioded, but I'm wondering if it was
possible the FQDN was used in the Netbios domain name in the Wizard of the
DCPromo during the upgrade. since the Wins now has a perioded domain entry
and the servers are seing duplicate users.
Also when users acces web applications across the trust now they must
specify \domain\user, which was not requiered prior to the upgrade.
> this is not a qualified name and will cause many problems after upgrading
> to Win2k3 Server.
>
> 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 two 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.
>
> We suggest you use the second method: before the upgrade, rename the
> existing NT "domain.com" NetBIOS domain name to get rid of .com.
>
> For your references:
>
> 288443 Cannot Use Same NetBIOS Name When You Upgrade a Windows NT 4.0
> Domain to
> http://support.microsoft.com/?id=288443
>
> How to Rename a Domain
> http://support.microsoft.com/default.aspx?scid=kb;en-us;169741
>
> If the issue still persists after renaming the Netbios name, please help me
> take a screen shot of the detailed error you encountered and directly send
> to me at v-amanwa@xxxxxxxxxxxxxx
>
> 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: after in-place upgrade sql need to re-join domain
> >thread-index: AcVlM7YopBjo9lhcS6mF4NkGKaeywA==
> >X-WBNR-Posting-Host: 69.159.240.95
> >From: "=?Utf-8?B?R2FzdG9uIER1cmFuZA==?="
> <GastonDurand@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Subject: after in-place upgrade sql need to re-join domain
> >Date: Mon, 30 May 2005 09:22:02 -0700
> >Lines: 13
> >Message-ID: <2DDEB0A5-B6E8-48D2-9C43-DEC2AE821D93@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!TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10441
> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >
> >NT 4 upgraded to a existing forest in mixed mode W2K3, from tech support
> >everything went fine. Question: in Wins there is now a Netbios.com entry
> for
> >00h (domain) entry. all cients seem to be running fine only prob the
> SQL2000
> >servers W2K o/s(authenticate to BDC viewed from set in DOS) when you try
> to
> >add a user to a group the users are found in netbiosname and
> >ad.netbios.com/users with an error of duplicate users found. when you
> rejoin
> >the ad.netbiosname.com domain and reboot everything is fine after problem
> >disapears. is there a way of avoid production sql from rejoinning the
> domain?
> >could during the upgrade and error have been made to input the fqdn
> instead
> >of the netbios name in the netbios domain name? would this have worked
> since
> >NT domain can have a period (.) name,if so anyways to clean this up?
> >
> >thank you
> >
>
>
.
- References:
- after in-place upgrade sql need to re-join domain
- From: Gaston Durand
- RE: after in-place upgrade sql need to re-join domain
- From: Amanda Wang [MSFT]
- after in-place upgrade sql need to re-join domain
- Prev by Date: RE: w2k domain prep done 4 w2k3
- Previous by thread: RE: after in-place upgrade sql need to re-join domain
- Next by thread: Authoritative Restore
- Index(es):
Relevant Pages
|
