Re: Problems joining network with /connectcomputer

From: Matthew Huynh \(MSFT\) (mhuynh_at_online.microsoft.com)
Date: 03/02/04 

Date: Tue, 2 Mar 2004 01:42:03 -0800

Hi Scott,

Can you try this and see if it solves your issue?

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=%23yHV7a%24IAHA.88%40cppssbbsa02.microsoft.com&rnum=2 

-- 
Matthew Huynh
This posting is provided "AS IS" with no warranties, and confers no rights.
"Scott D." <savvy@mac.com> wrote in message
news:882a9dcd.0403011415.212c1deb@posting.google.com...
> Thanks for your suggestions so far, but I have yet to nail down my
> problem with this machine.
>
> I have checked the Advanced Settings on both the server and this
> client machine and they both have TCP/IP bound to File and Print
> Sharing and Client for Microsoft network. I have removed all other
> protocols from the client machine as well.
>
> Note that while having these troubles I was able to use the
> connectcomputer setup utility to sucessfully configure a different
> machine running WinXP. On this machine that is unable to join the
> network, you are correct that it will not join the network manually
> either.
>
> Also, I am able to ping the server, mikenserver.mikentechnology.local,
> with no problems from the machine. I have checked through all the
> policies on the machine and do not see any that seem to be stopping me
> from joining.
>
> Through all of my changes the log files remain the same, showing a
> 1231 error whenever it attempts to connect to the IPC$ share. The
> interesting thing is if I from a command prompt do a 'net use
> \\mikenserver.mikentechnology.local\IPC$' it shows a 1231 error, but
> if I do 'net use \\mikenserver\IPC$' it comes back with an invalid
> password error. Remember that I can sucessfully ping
> mikenserver.mikentechnology.local with no problems. I'm sure this is
> the key to my problem, but its not leading me down the right path
> unfortunately.
>
> "Mike Stokke [MSFT]" <mstokke@online.microsoft.com> wrote in message
news:<#c2S3cw#DHA.4060@TK2MSFTNGP10.phx.gbl>...
> > The problem with the not able to access the IPC$ share is typically an
issue
> > with bindings to your network card.  If you have the IPC$ issue, then
> > a manual join from the client to the server should also fail.  To
correct
> > this problem, go to Start->control panel-> and open the network
connections.
> > On the Advanced Menu, select advanced settings.  Check your NIC and make
> > sure
> > that File and Print Sharing (with TCPIP), and Client for Microsoft
network
> > (with TCPIP) is enabled for this NIC.  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.  You may also check the local
> > policies on this client and see if there are any set that are preventing
you
> > from joining the network.
> >
> > -- 
> > Mike Stokke
> > -------------------
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> > "Scott D." <savvy@mac.com> wrote in message
> > news:882a9dcd.0402241043.24e432e2@posting.google.com...
> > > I checked the machine this morning, and I was able to successfully
> > > ping the server by the name. The machine is only configured with a
> > > single network connection, and I tried it again with all firewall and
> > > virus software disabled.
> > >
> > > This is a snippet from the netsetup.log, which is repeated for every
> > > attempt I make to configure the machine.
> > >
> > > 02/20
> >
 15:58:16 -----------------------------------------------------------------
> > > 02/20 15:58:16 NetpDoDomainJoin
> > > 02/20 15:58:16 NetpMachineValidToJoin: 'KENLAPTOP'
> > > 02/20 15:58:16 NetpGetLsaPrimaryDomain: status: 0x0
> > > 02/20 15:58:16 NetpMachineValidToJoin: status: 0x0
> > > 02/20 15:58:16 NetpJoinDomain
> > > 02/20 15:58:16 Machine: KENLAPTOP
> > > 02/20 15:58:16 Domain: MikenTechnology.local
> > > 02/20 15:58:16 MachineAccountOU:
> > > ou=sbscomputers,ou=computers,ou=mybusiness,dc=mikentechnology,dc=local
> > > 02/20 15:58:16 Account: MikenTechnology.local\sdenowh
> > > 02/20 15:58:16 Options: 0x67
> > > 02/20 15:58:16 OS Version: 5.0
> > > 02/20 15:58:16 Build number: 2195
> > > 02/20 15:58:16 ServicePack: Service Pack 4
> > > 02/20 15:58:16 NetpValidateName: checking to see if
> > > 'MikenTechnology.local' is valid as type 3 name
> > > 02/20 15:58:16 NetpValidateName: 'MikenTechnology.local' is not a
> > > valid NetBIOS domain name: 0x7b
> > > 02/20 15:58:16 NetpCheckDomainNameIsValid [ Exists ] for
> > > 'MikenTechnology.local' returned 0x0
> > > 02/20 15:58:16 NetpValidateName: name 'MikenTechnology.local' is valid
> > > for type 3
> > > 02/20 15:58:16 NetpDsGetDcName: trying to find DC in domain
> > > 'MikenTechnology.local', flags: 0x1020
> > > 02/20 15:58:16 NetpDsGetDcName: found DC
> > > '\\mikenserver.MikenTechnology.local' in the specified domain
> > > 02/20 15:58:16 NetUseAdd to \\mikenserver.MikenTechnology.local\IPC$
> > > returned 1231
> > > 02/20 15:58:16 NetpJoinDomain: status of connecting to dc
> > > '\\mikenserver.MikenTechnology.local': 0x4cf
> > > 02/20 15:58:16 NetpDoDomainJoin: status: 0x4cf
> > >
> > > Thanks for the advice, and if there is anything else I can provide
> > > that may help nail down the problem, just let me know.
> > >
> > > "Mike Stokke [MSFT]" <mstokke@online.microsoft.com> wrote in message
> >  news:<eCy8Gsj#DHA.3816@tk2msftngp13.phx.gbl>...
> > > > Can you send the netsetup.log from the %windir%\debug folder on the
> >  client?
> > > > It may contain some more detailed information as to the problem.
Next,
> >  can
> > > > you check to see if you can ping the server name, server netbios,
and
> >  the
> > > > domain name.  After that, check the advanced settings on your
network
> > > > adapter and make sure that TCP/IP and file and print sharing are
bound
> >  to
> > > > the NIC.  If you have multiple network connections, disable all but
the
> >  one
> > > > connected to the network.  Finally, try disabling any firewalls or
virus
> > > > scanners before you join the domain.
> > > >
> > > >
> > > > -- 
> > > > Mike Stokke
> > > > -------------------
> > > > This posting is provided "AS IS" with no warranties, and confers no
> >  rights.
> > > >
> > > >
> > > >
> > > > "Scott D." <savvy@mac.com> wrote in message
> > > > news:882a9dcd.0402201414.115734ea@posting.google.com...
> > > > > I have a new install of SBS2003, and have sucessfully setup 2
> > > > > machines, one WinXP and one Win2k with the
> > > > > http://servername/connectcomputer/ wizard. On the third machine I
am
> > > > > trying to setup, a Win2k ThinkPad, I cannot complete the wizard
> > > > > without getting a networking error. I am able to log in properly
and
> > > > > see the user and computer name, it only fails after the final
screen
> > > > > before it is supposed to reboot the machine and complete the
setup.
> > > > >
> > > > > Below is the SBSNetSetup.log that is showing my failed attempt to
> > > > > setup the machine. I see that NetJoinDomain() is failing and
returning
> > > > > 1231 as the error code, which according to MSDN is
> > > > > ERROR_NETWORK_UNREACHABLE. This machine is configured to be in a
> > > > > workgroup named WORKGROUP and was previously a member of a
> > > > > peer-to-peer Windows network. My SBS2003 server is acting as the
DHCP
> > > > > server, and that is working great, and I can verify it has the
same
> > > > > settings (other than IP of course) as the 2 prior machines that
setup
> > > > > flawlessly.
> > > > >
> > > > > Any thoughts as to where I am going wrong, and what I could try to
fix
> > > > > this problem? I would very much like to not lose this profile on
the
> > > > > laptop.
> > > > >
> > > > > -- Starting SBS Net Setup --
> > > > > found [64] keys
> > > > > CProfileList::CProfileList() - added [1000, C:\Documents and
> > > > > Settings\Kenneth Brudzinski] to the profile dir map
> > > > > CProfileList::CProfileList() - added [500, C:\Documents and
> > > > > Settings\Administrator.KENLAPTOP] to the profile dir map
> > > > > CProfileList::CProfileList() - added [1137, C:\Documents and
> > > > > Settings\KenBrudzinski] to the profile dir map
> > > > > CProfileList::CProfileList() - added [Administrator, C:\Documents
and
> > > > > Settings\Administrator.KENLAPTOP] to the profile dir map
> > > > > CProfileList::CProfileList() - added [Kenneth Brudzinski,
C:\Documents
> > > > > and Settings\Kenneth Brudzinski] to the profile dir map
> > > > > CAuthPage::OnNotify() - PSN_WIZNEXT - User Name: sdenowh
> > > > > CAuthPage::GetUsersAndComputers() - ADsOpenObject(
> > > > >
LDAP://MIKENSERVER.MikenTechnology.local/DC=MikenTechnology,DC=local,
> > > > > sdenowh, [PW] )
> > > > > CAuthPage::GetUsersAndComputers() - ADsOpenObject(
> > > > >
LDAP://MIKENSERVER.MikenTechnology.local/DC=MikenTechnology,DC=local,
> > > > > sdenowh, [PW] )
> > > > > CAuthPage::OnNotify() - PSN_SETACTIVE - our computer name IS in
the AD
> > > > > GetXMLNode() - DOMDocument::selectSingleNode(
> > > > > root/mapping[@user='sdenowh'] ) failed [1]
> > > > > LoadMappingInfo() - find [root/mapping[@user='sdenowh']] failed,
user
> > > > > not mapped
> > > > > CProfileList::IsPrivateProfile( Kenneth Brudzinski )
> > > > > CProfileList::IsPrivateProfile() - starting the search
[C:\Documents
> > > > > and Settings\Kenneth Brudzinski]
> > > > > CWizard::PrepAutoLogon()
> > > > > CWizard::PrepAutoLogon() - runonce key set
> > > > > CWizard::PrepAutoLogon() - account existed, deleting
> > > > > CWizard::PrepAutoLogon() - setting DefaultDomainName_PostMigrate
to
> > > > > [MIKENTECHNOLOGY], [0]
> > > > > FinishNetworkingSetup()
> > > > > CWizard::FinishNetworkingSetup() - outputting XML file
> > > > > FinishNetworkingSetup() -- calling NetJoinDomain( NULL,
> > > > > MikenTechnology.local,
> > > > >
> >  ou=sbscomputers,ou=computers,ou=mybusiness,dc=mikentechnology,dc=local,
> > > > > MikenTechnology.local\sdenowh, [pw], 103 )
> > > > > FinishNetworkingSetup() -- NetJoinDomain() failed [1231],
returning
> > > > > FinishNetworkingSetup() failed -- hr == [-2147467259]
> > > > > Deleted sbsmig out of runonce key.

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)