Re: XP join SBS 2003

From: Mike Stokke [MSFT] (mstokke_at_online.microsoft.com)
Date: 02/10/04 

Date: Tue, 10 Feb 2004 11:06:38 -0800

The problem with the not able to access the IPC$ share is typically an issue
with server bindings to your network card. If you have the IPC$ issue, then
a manual join from the client to the server should also fail. Sometimes
this problem is also visible by trying to open up the WINS snapin on the
server and this fails. To correct this problem, go to Start->control
panel-> and open the network connections. On the Advanced Menu, select
advanced settings. Check your server local area connection and make sure
that File and Print Sharing (with TCPIP), and Client for Microsoft network
(with TCPIP) is enabled for this NIC. If you only have 1 nic, then make
sure the previous settings exist. Also, make sure that the nic connected to
your network has these bindings. If another client was able to join the
domain, then check these settings on the client box as well. If the client
has 2 nics, then try disabling one of the nics and making sure that the nic
connected to the local network is highest in the search order. Finally from
the client, ping the server name and the server DNS name. Now try to rejoin
the network. 

-- 
Mike Stokke
-------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
"Greg Hoeft" <Anonymous> wrote in message
news:%23NLzS1$7DHA.2416@TK2MSFTNGP10.phx.gbl...
> 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: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • 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: Small business thinking about backing up data, having a server and 2-3 users - is SBS200
    ... is networked to the Master with a crossover network cable. ... Master on the Master PC and Client on the Slave pc. ... Since this machine is a server is should handle the requests ok ... Most real firewall appliances have HTTP and SMTP proxy services that allow ...
    (microsoft.public.windows.server.sbs)
  • RE: Private addresses on public network
    ... anybody accesses those computers from an external network," -- even when the ... JavaScript delivered to the client that causes the client to retrieve ... the attacker, the request results in another JavaScript response that tells ... Moving beyond a single server ...
    (Security-Basics)
Loading