Re: Problems joining network with /connectcomputer
From: Matthew Huynh \(MSFT\) (mhuynh_at_online.microsoft.com)
Date: 03/04/04
- Next message: Steven Banks [SBS MVP]: "Exchange Relay errors solved by re-running CEICW"
- Previous message: Jéjé: "port 4125 closed on my server ?"
- In reply to: Scott D.: "Re: Problems joining network with /connectcomputer"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 3 Mar 2004 16:18:55 -0800
Looks like netdiag skipped the dc discovery test.
Could you run:
netdiag /l /v /test:dsgetdc
Another thing to try is to add an entry to the LMHost file of that client:
1.2.3.4 Servername #PRE #DOM:domainname.local
You said it was funny that it didn't like this client was using DNS to find
the DC, maybe this will help.
--
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.0403030728.7dfb2856@posting.google.com...
> Thanks for the link Matthew. I feel that I'm making some headway, but
> I'm still not getting this machine to join my domain. I've tried what
> is suggested as far as I can tell it applies, and am still getting
> that 1231 error when trying to join the domain. I am seeing some
> errors in my NetDiag.log that may be helpful, but I'm unsure of what
> exactly they mean. I'm posting my log file here:
>
>
>
>
> Computer Name: KENLAPTOP
> DNS Host Name: kenlaptop
> System info : Windows 2000 Professional (Build 2195)
> Processor : x86 Family 6 Model 8 Stepping 3, GenuineIntel
> List of installed hotfixes :
> KB329115
> KB820888
> KB822831
> KB823182
> KB823559
> KB823980
> KB824105
> KB824141
> KB824146
> KB825119
> KB826232
> KB828028
> KB828035
> KB828749
> Q147222
> Q816093
> Q818043
> Q828026
>
>
> Netcard queries test . . . . . . . : Passed
>
>
>
> Per interface results:
>
> Adapter : Local Area Connection
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : kenlaptop.MikenTechnology.local
> IP Address . . . . . . . . : 192.168.1.105
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 192.168.1.1
> Primary WINS Server. . . . : 192.168.1.1
> Dns Servers. . . . . . . . : 192.168.1.1
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
>
> WINS service test. . . . . : Passed
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
> Dns domain name is not specified.
> Dns forest name is not specified.
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{5E1D7A01-9F1D-4292-8720-481DFF94A5EA}
> 1 NetBt transport currently configured.
>
>
> Autonet address test . . . . . . . : Passed
>
>
> IP loopback ping test. . . . . . . : Passed
>
>
> Default gateway test . . . . . . . : Passed
>
>
> NetBT name test. . . . . . . . . . : Passed
>
>
> Winsock test . . . . . . . . . . . : Passed
>
>
> DNS test . . . . . . . . . . . . . : Passed
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{5E1D7A01-9F1D-4292-8720-481DFF94A5EA}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{5E1D7A01-9F1D-4292-8720-481DFF94A5EA}
> The browser is bound to 1 NetBt transport.
>
>
> DC discovery test. . . . . . . . . : Skipped
>
>
> DC list test . . . . . . . . . . . : Skipped
>
>
> Trust relationship test. . . . . . : Skipped
>
>
> Kerberos test. . . . . . . . . . . : Skipped
>
>
> LDAP test. . . . . . . . . . . . . : Skipped
>
>
> Bindings test. . . . . . . . . . . : Passed
>
>
> WAN configuration test . . . . . . : Skipped
> No active remote access connections.
>
>
> Modem diagnostics test . . . . . . : Passed
>
> IP Security test . . . . . . . . . : Skipped
> The IPSec Policy Agent service is not started.
>
>
> The command completed successfully
>
> My thinking is that these lines:
> Domain membership test . . . . . . : Passed
> Dns domain name is not specified.
> Dns forest name is not specified.
>
> Are my problem, and that I need to take care of these Dns problems.
> The problem I'm having is that I can't figure out what settings to
> change in order for those problems to go away. If I run ipconfig /all
> on the machine that won't join, it shows its Primary DNS Suffix as
> blank, but on a machine that joined sucessfully it shows that as
> MikenTechnology.local. Both of these machines are accessing the same
> DHCP server though, and I released and renewed both several times with
> the same results.
>
> Any further thoughts?
>
>
> "Matthew Huynh \(MSFT\)" <mhuynh@online.microsoft.com> wrote in message
news:<#zNnfqDAEHA.1224@TK2MSFTNGP11.phx.gbl>...
> > 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.
- Next message: Steven Banks [SBS MVP]: "Exchange Relay errors solved by re-running CEICW"
- Previous message: Jéjé: "port 4125 closed on my server ?"
- In reply to: Scott D.: "Re: Problems joining network with /connectcomputer"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
