RE: Issues with NT4 to SBS2K3 upgrade.

From: Robert McHenry (RobertMcHenry_at_discussions.microsoft.com)
Date: 09/03/04


Date: Fri, 3 Sep 2004 14:19:04 -0700

Thanks for the reply Rick. Think I needed a day to rest & get my mind back on
track. Was able to resolve after a good rest.

RM

""Ricky Morris [MSFT]"" wrote:

> Robert,
>
> What is the fully qualified name of the wo XP clients which are not able to join the domain? Open properties of My Computer, go to the
> Computer Name tab to see this.
>
> Please post the FQDN of one of the XP Pro clients which have been joined successfully to the domain for comparison.
>
> Are the two XP clients running any kind of firewall? Internet connection firewall, third party firewall? If so, disable it.
>
> Manually move the two XP pro clients which will not join the new domain into a workgroup. Test logging as the local administrator on each
> computer BEFORE moving the computer to a workgroup. Ensure that each client is pointing to the SBS 2003 server for DNS and WINS and
> no others.
>
> Once you have moved the two XP pro clients to a workgroup, delete their computer accounts from the Active Directory (you have to open
> Active Directory Users and Computers | MyBusiness | Computers | SBSComputers to find their accounts and be able to delete them. The
> Server Management Console will not allow you to delete the computers' accounts.)
>
> Create new computer accounts using the Server Management Console Add Computer wizard.
>
> Log on to the XP Pro computers in the workgroup as the local Administrator. Run http://server/connectcomputer from each of the 2 XP
> Pro machines. You should be able to join the new domain with these computers without difficulty.
>
> In your post, your indicated that the SBS 2003 domain name is dunbartonnh. I presume you meant the NetBIOS name of the domain is
> dunbartonnh AND that there is a domain suffix for the DNS name of the dunbartonnh domain which you did not mention. The FQDN of the
> computer joined to the domain will let us know what the domain suffix is.
>
>
> Best Regards,
>
> Ricky Morris
> Microsoft Small Business Server Support
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Newsgroups:
> SBS v4.x : microsoft.public.backoffice.smallbiz
> SBS 2000: microsoft.public.backoffice.smallbiz2000
> SBS 2003: microsoft.public.windows.server.sbs
>
>
> --------------------
> Thread-Topic: Issues with NT4 to SBS2K3 upgrade.
> thread-index: AcSGD4Cp2Gg+0q71Snybp5CXKAI+Ng==
> X-WBNR-Posting-Host: 66.194.216.4
> From: "=?Utf-8?B?Um9iZXJ0IE1jSGVucnk=?=" <RobertMcHenry@discussions.microsoft.com>
> Subject: Issues with NT4 to SBS2K3 upgrade.
> Date: Thu, 19 Aug 2004 10:11:01 -0700
> Lines: 30
> Message-ID: <328ADC48-850C-4820-95E1-3ECE2F282439@microsoft.com>
> 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.sbs
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.sbs:98438
> X-Tomcat-NG: microsoft.public.windows.server.sbs
>
> Pulled an all nighter upgrading a poorly planned NT4 server to SBS2003.
> Working with 5 Windows XP Pro Dell PC's that where originally on the NT4
> domain. Original server was running mirrored 40 gig drives with two
> partitions. I was able to break the mirror and install clean OS on a 40 gig
> partition. Connected the 2nd drive to the server so I can get to the data. So
> far so good.
>
> Into the wee hours of the morning I had the new server up & running so I
> decided to start joining the 5 clients to the domain. Original domain name
> was dunbarton. New domain is dunbartonnh. 3 of the 5 PC's joined w/o
> problems. The last 2 are giving me fits!
>
> When I try & add the original users to the new domain I'm unable to add them
> to the local admin group on the client. It should be dunbartonnh\username but
> the two PC's will only let me add them to the local client,
> e.g.[computername]\[username] instead of domainname\username.
>
> The users are not admins on the local box now. Also If I try & manage the PC
> from the server side I'm told the server is unable to communicate with the
> client. I can logon to the PC as admin & do everything BUT add the local user
> as an admin!
>
> I hope I have explained it clearly! I need to get this issue resolved so I
> can finish the install & fine tune the whole shootin match.
>
> Thanks All!
>
> Robert McHenry
> Concord, NH
>
>
>
>
>



Relevant Pages

  • RE: Users Cant Access Documents on Server
    ... Thanks for using the SBS newsgroup. ... As well as we know, if a workstation would not access network shares, then ... Leave the Default Gateway of the internal NIC blank of the server box. ... Clients That Require SMB Signing ...
    (microsoft.public.windows.server.sbs)
  • Re: Users Cant Access Documents on Server
    ... my computer to the network on the server. ... Connection Wizard none of the computers were listed. ... The Mac clients can not communicate with the server box. ... > Error Messages When You Open or Copy Network Files on Windows XP SP1 ...
    (microsoft.public.windows.server.sbs)
  • Re: [SLE] SMTP authentication
    ... So eventhough my local SMTP server dials up to the internet with a certain username and password, that same username and password would not be used as authentication between my local SMTP server and the ISP's one, should it be used as a relay? ... either defer all outgoing mails until you connect to the internet, then flush out all the mails in the queue. ... Your local server would use an external program like fetchmail to poll the mailserver of your ISP, download the mails and feed them to Postfix. ... The test does NOT say "All clients must be in mynetworks, ...
    (SuSE)
  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Users Cant Access Documents on Server
    ... > then add my computer to the network on the server. ... Did you not see the computers in the Server Management taskpad section? ... The Mac clients can not communicate with the server box. ... >> Error Messages When You Open or Copy Network Files on Windows XP SP1 ...
    (microsoft.public.windows.server.sbs)

Loading