Re: Very frustrated with MS Server 2003 SBS

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Is there a .log file called SBSNetSetup.log? or is this it? (in c:\program
files\microsoft windows small business server\clients) on the workstation.

It seems the computer is joined to a domain called Allied? And you SBS
domain is alliedmetal.local. Correct?

And, you can't disjoin the workstation from the 'Allied' domain?

Is the NT server still running, and on the same network as the SBS?

Is this SBS server remotely accessible?

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !


"Alan Chwick" <Alan.Chwick@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ueCc70JjFHA.3608@xxxxxxxxxxxxxxxxxxxxxxx
> The computer names are unique, don't start with a number and are not the
> same as workgroup or domain names (or user names).
>
> The Netsetup.Log file is:
>
> 07/18
> 14:05:42 -----------------------------------------------------------------
> 07/18 14:05:42 NetpDoDomainJoin
> 07/18 14:05:42 NetpMachineValidToJoin: 'JOSE2K'
> 07/18 14:05:42 NetpGetLsaPrimaryDomain: status: 0x0
> 07/18 14:05:42 NetpMachineValidToJoin: the specified machine is already
> joined to 'ALLIED'! - > [But it isn't. AJC]
> 07/18 14:05:42 NetpMachineValidToJoin: status: 0xa83
> 07/18 14:05:42 NetpJoinDomain
> 07/18 14:05:42 Machine: JOSE2K
> 07/18 14:05:42 Domain: alliedmetal.local
> 07/18 14:05:42 MachineAccountOU:
> ou=sbscomputers,ou=computers,ou=mybusiness,dc=alliedmetal,dc=local
> 07/18 14:05:42 Account: alliedmetal.local\administrator
> 07/18 14:05:42 Options: 0x67
> 07/18 14:05:42 OS Version: 5.0
> 07/18 14:05:42 Build number: 2195
> 07/18 14:05:42 ServicePack: Service Pack 4
> 07/18 14:05:42 NetpValidateName: checking to see if 'alliedmetal.local'
> valid as type 3 name
> 07/18 14:05:42 NetpValidateName: 'alliedmetal.local' is not a valid
> NetBIOS domain name: 0x7b
> 07/18 14:05:42 NetpCheckDomainNameIsValid [ Exists ] for
> 'alliedmetal.local' returned 0x0
> 07/18 14:05:42 NetpValidateName: name 'alliedmetal.local' is valid for
> type 3
> 07/18 14:05:42 NetpDsGetDcName: trying to find DC in domain
> 'alliedmetal.local', flags: 0x1020
> 07/18 14:05:42 NetpDsGetDcName: found DC '\\ALLIED-S001.alliedmetal.local'
> in the specified domain
> 07/18 14:05:42 NetpJoinDomain: status of connecting to dc
> '\\ALLIED-S001.alliedmetal.local': 0x0
> 07/18 14:05:42 NetpGetLsaPrimaryDomain: status: 0x0
> 07/18 14:05:42 NetpLsaOpenSecret: status: 0x0
> 07/18 14:05:42 NetpGetLsaPrimaryDomain: status: 0x0
> 07/18 14:05:42 NetpLsaOpenSecret: status: 0x0
> 07/18 14:05:43 NetpCreateComputerObjectInOU: Account already exists
> 07/18 14:05:43 ldap_unbind status: 0x0
> 07/18 14:05:43 NetpJoinDomain: status of creating account in OU: 0x0
> 07/18 14:05:43 NetpJoinDomain: status of setting netlogon cache: 0x0
> 07/18 14:05:43 NetpGetLsaPrimaryDomain: status: 0x0
> 07/18 14:05:44 NetpSetLsaPrimaryDomain: for 'alliedmetal' status: 0x0
> 07/18 14:05:44 NetpJoinDomain: status of setting LSA pri. domain: 0x0
> 07/18 14:05:45 NetpJoinDomain: status of managing local groups: 0x0
> 07/18 14:05:45 NetpJoinDomain: status of setting
> ComputerNamePhysicalDnsDomain to 'alliedmetal.local': 0x0
> 07/18 14:05:45 NetpControlServices: open service 'NETLOGON' failed: 0x424
> 07/18 14:05:46 NetpJoinDomain: status of enabling Netlogon: 0x424
> 07/18 14:05:46 NetpJoinDomain: initiaing a rollback due to earlier errors
> 07/18 14:05:46 NetpJoinDomain: rollback: local group management: 0x0
> 07/18 14:05:47 NetpSetLsaPrimaryDomain: for 'ALLIED' status: 0x0
> 07/18 14:05:47 NetpJoinDomain: rollback: status of setting NULL domain
> sid: 0x0
> 07/18 14:05:47 ldap_unbind status: 0x0
> 07/18 14:05:47 NetpJoinDomain: rollback: status of deleting the computer
> account from OU: 0x0
> 07/18 14:05:47 NetpLsaOpenSecret: status: 0x0
> 07/18 14:05:48 NetpJoinDomain: rollback: status of restoring secret: 0x0
> 07/18 14:05:48 NetpJoinDomain: status of disconnecting from
> '\\ALLIED-S001.alliedmetal.local': 0x0
> 07/18 14:05:48 NetpDoDomainJoin: status: 0x424
>
>
>
> Kathy wrote:
>
>> Make sure that all computer names are unique, don't begin with a number
>> and
>> are not the same as workgroup or domain names (or user names) and that
>> the
>> workstation and netbios helper services are running on the PCs. A quick
>> look
>> in the system log might give clue as to exactly which service isn't
>> running.
>>
>> Kathy
>>
>> "Alan Chwick" <Alan.Chwick@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:%23APoL7HjFHA.1464@xxxxxxxxxxxxxxxxxxxxxxx
>>
>>>Les,
>>>
>>>I have tried your idea, but to no avail.
>>>
>>>First, to summarize:
>>>
>>>I am trying to add several computers to a new 2003 SBS server with a new
>>>domain.
>>>
>>>The client workstations are currently under an NT server with a domain.
>>>
>>>I added the computers to AD and went to
>>>http:\\servername\connectcomputers via the client workstation.
>>>
>>>The first computer went up AOK. No errors.
>>>
>>>The remaining three got the message,"The specified service does not
>>>exist as an installed service." And the procedure failed.
>>>
>>>
>>>What I tried:
>>>
>>>As suggested, I am to disjoin the problem computers from their domain
>>>and join them to a workgroup. Then, add the client computers to AD and
>>>then do http:\\servername\connectcomputers at the client workstations
>>
>> again.
>>
>>>Problem - The client workstation will not let me disjoin the client
>>>computer from its current domain and add them to a workgroup. They all
>>>get the same message when I try to do this. They get the message, "The
>>>specified service does not exist as an installed service." This message
>>>seems to be a very generic message.
>>>
>>>Any idea as to what is going on here?
>>>
>>>Very frustrated in NY,
>>>
>>>Alan
>>>
>>>Les Connor [SBS Community Member - SBS MVP] wrote:
>>>
>>>>Hi Alan,
>>>>
>>>>1. Disjoin the problem clients computers from the domain, and join a
>>>>workgroup. This is done from My Computer | Properties on the
>>
>> workstation.
>>
>>>>Also, ensure the workstations are set as DHCP clients - restart the
>>>>workstation (don't log on yet).
>>>>
>>>>2. In AD on the SBS, delete the computer accounts you previously
>>
>> created.
>>
>>>>3. On the SBS, in Server Management | Standard Management | Client
>>>>Computers, click the link 'Set up Client Computers' to run the Add
>>
>> Computer
>>
>>>>Wizard.
>>>>
>>>>4. Log onto the workstation with local administrative rights, and run >
>>>>http://<servername>/connectcomputer.
>>>>
>>>>If you join the computer to the domain any other way you'll get a sore
>>
>> head,
>>
>>>>as many of the SBS features will throw a brick when you try and use
>>
>> them.
>>
>>

.

Relevant Pages

  • Re: Clocks dont match error
    ... Quit one workstation from the domain and join it back to workgroup refer ... Setup the client computer by running Setup Client Computer wizard to ... Note: Please ensure you have added the SBS Site in trusted ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sudden Issues with DHCP & Remote Access
    ... Suitehelp.dll problem after SBS SP1 install. ... But, if I do a Rebuild Server List in RRAS, the workstation where I ...
    (microsoft.public.windows.server.sbs)
  • RE: Slow Logon related to groups
    ... Open Server Management console on SBS ... Ensure the problematic user has permission to access its home folder on ... After the problematic user logon workstation, ...
    (microsoft.public.windows.server.sbs)
  • Re: Sudden Issues with DHCP & Remote Access
    ... Is the SBS second NIC disabled in the BIOS? ... After assigning IP Addresses to the workstation I could rejoin the domain ... Broadcom Netxtrem Gigabit on Server. ... Suitehelp.dll problem after SBS SP1 install. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sudden Issues with DHCP & Remote Access
    ... But, if I do a Rebuild Server List in RRAS, the workstation where I disabled ... How to install Service Pack 1 for SBS 2003 ... Small Business Server Service Pack) ...
    (microsoft.public.windows.server.sbs)