Re: XP join SBS 2003

From: Tony Benson (anonymous_at_discussions.microsoft.com)
Date: 02/10/04


Date: Tue, 10 Feb 2004 10:44:21 -0800

I seem to have fixed this......

stumbled across this but in the local security settings
of the pc not enable to join the domain, change the do
not allow anonymous enumeration of SAM accounts to
disable and run again....

this got me working again, however maybe someone from MS
could let me know if this is bad idea...

Tony

>-----Original Message-----
>Any update on this??
>
>Is this a good thing, "NetUseAdd to
\\sbs2003.NAMEOFDOMAIN.local\IPC$
>returned 51"
>
>Is an event 51 an issue, and what can I look at
concerning the IPC$ share???
>
>Please Help.... TIA
>
>Greg
>
>
>"Greg Hoeft" <test> wrote in message
>news:uPP7Hz27DHA.2560@TK2MSFTNGP09.phx.gbl...
>> Mike,
>>
>>
>> Just to supply more details:
>> I've created both the users and client machine via Add
User Wizard. I can
>> ping and talk to the server from the client. When I
use the utility
>> http://Nameofserver/ConnectComputer/ it asks me for
the username and
>> password, then it pulls up the list of id's within AD,
and I choose the
>ids
>> that need access to the client workstation, the next
screen I can choose
>the
>> name of the workstation, then click finish. A few
seconds later it comes
>> back and says, "An error occured when configuring
networking settings.
>See
>> your network administrator".
>>
>> In the netsetup.log it shows that it is negotiating
with the DC
>> successfully, it shows:
>> 02/09
>> 16:01:45 ----------------------------------------------
-------------------
>> 02/09 16:01:45 NetpDoDomainJoin
>> 02/09 16:01:45 NetpMachineValidToJoin: 'TOSHLAP'
>> 02/09 16:01:45 NetpGetLsaPrimaryDomain: status: 0x0
>> 02/09 16:01:45 NetpMachineValidToJoin: status: 0x0
>> 02/09 16:01:45 NetpJoinDomain
>> 02/09 16:01:45 Machine: TOSHLAP
>> 02/09 16:01:45 Domain: NAMEOFDOMAIN.local
>> 02/09 16:01:45 MachineAccountOU:
>>
ou=sbscomputers,ou=computers,ou=mybusiness,dc=NAMEOFDOMAIN
,dc=local
>> 02/09 16:01:45 Account: NAMEOFDOMAIN.local\greg.hoeft
>> 02/09 16:01:45 Options: 0x167
>> 02/09 16:01:45 OS Version: 5.1
>> 02/09 16:01:45 Build number: 2600
>> 02/09 16:01:45 ServicePack: Service Pack 1
>> 02/09 16:01:45 NetpValidateName: checking to see
if 'NAMEOFDOMAIN.local'
>is
>> valid as type 3 name
>> 02/09 16:01:45 NetpCheckDomainNameIsValid [ Exists ]
for
>> 'NAMEOFDOMAIN.local' returned 0x0
>> 02/09 16:01:45 NetpValidateName:
name 'NAMEOFDOMAIN.local' is valid for
>type
>> 3
>> 02/09 16:01:45 NetpDsGetDcName: trying to find DC in
domain
>> 'NAMEOFDOMAIN.local', flags: 0x1020
>> 02/09 16:01:45 NetpDsGetDcName: found
DC '\\sbs2003.NAMEOFDOMAIN.local' in
>> the specified domain
>> 02/09 16:01:46 NetUseAdd to
\\sbs2003.NAMEOFDOMAIN.local\IPC$ returned 51
>> 02/09 16:01:46 NetpJoinDomain: status of connecting to
dc
>> '\\sbs2003.NAMEOFDOMAIN.local': 0x33
>> 02/09 16:01:46 NetpDoDomainJoin: status: 0x33
>>
>> Everything else on the server seems to be functioning
perfect, except this
>> issue.
>>
>> There are a few others on this newsgroup that appear
to be having a
>similar
>> issue. These two within this thread and another bunch
of folks starting
>on
>> 12/31 with the message title, "Error when trying to
join sbs2003 domain
>with
>> xp pro workstation".
>>
>> I also didn't modify the server network card. I've
completed about a
>dozen
>> fresh installs due to the Nov 24 issue and
Sharepoint. The workstation
>nic
>> also has file and print sharing enabled.
>>
>> Please Help.... Thanks!!
>> Greg
>>
>> "Mike Stokke [MSFT]" <mstokke@online.microsoft.com>
wrote in message
>> news:#v9MfW27DHA.3380@tk2msftngp13.phx.gbl...
>> > Go to the client and look in the %windir%\debug
folder and send the
>> > netsetup.log. For the accounts that you are using
to join on, were they
>> > created through the Add User Wizard? Did you create
computer accounts
>as
>> > well? From the client machine, can you ping both
the server name and
>the
>> > server's NetBIOS? If all of that seems correct, did
you modify the
>> network
>> > card on the server that you are using for the
internal network? If so,
>> > check the bindings of services to this NIC and make
sure that they allow
>> > file and print sharing to this NIC.
>> >
>> >
>> > --
>> > Mike Stokke
>> > -------------------
>> > This posting is provided "AS IS" with no warranties,
and confers no
>> rights.
>> >
>> > "Greg Hoeft" <test> wrote in message
>> > news:uJxUJL17DHA.2480@TK2MSFTNGP10.phx.gbl...
>> > > Is anyone from Microsoft on?
>> > >
>> > > Help!
>> > >
>> > > This is a criticle issue.
>> > >
>> > > Thanks,
>> > > Greg
>> > > <anonymous@discussions.microsoft.com> wrote in
message
>> > > news:d89701c3ef4a$1c8d8180$a601280a@phx.gbl...
>> > > > one guess - and it's strictly a guess - is that
maybe the
>> > > > XP computer accounts aren't being created?
>> > > >
>> > > > -Bruce Diamond
>> > > >
>> > > >
>> > > > >-----Original Message-----
>> > > > >help!
>> > > > >
>> > > > >have a problem with a new installation of SBS
2003; DNS,
>> > > > >DHCP etc are all working fine and I can join
W2k Machines
>> > > > >to the SBS domain but I cant join XP
machines.......
>> > > > >
>> > > > >if you run the connect computer method, it
comes back
>> > > > with
>> > > > >network configuration error, if you try to do
it manually
>> > > > >from control panel - system says access is
denied.
>> > > > >
>> > > > >I know the user rights are
correct...............
>> > > > >
>> > > > >any clues?
>> > > > >
>> > > > >Ta
>> > > > >tony
>> > > > >
>> > > > >.
>> > > > >
>> > >
>> > >
>> >
>> >
>>
>>
>
>
>.
>



Relevant Pages

  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Strange Connection Issues with Win2003 Server & XP Client
    ... System Error 53 Has Occured - The network path was not found - this was ... I can ping the server, I can "net view" & "net view server" the server ... shares, but not the actual shares, I get the same messages as above. ... workstation on the same network, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Logon Failures from unknown workstation
    ... possibility is that someone had an unauthorized computer on the network such ... server's properties in the rras console. ... was recorded in the "system" log of the VPN server. ... > There is no workstation in our forest named AFREEMAN; ...
    (microsoft.public.security)