Re: Can't Join SBS2003 Domain from XP Pro Client

From: billyw (b_at_brainless.net)
Date: 07/03/04 

Date: Sat, 3 Jul 2004 18:21:22 +0100

good information...
i've had no end of issues with various different XP pro's connecting to sbs.
win2k and win98 no problem... xp.. it's a coin toss if it will connect first
time

"N. Hughes" <quadrantcomputerNOSPAM@hotmail.com> wrote in message
news:uh9$5KNYEHA.3516@TK2MSFTNGP09.phx.gbl...
> Reed,
> Iif your scenario was an inplace upgrade, we experienced the exact same
> problem earlier in the year. After losing lots of
> sleep, and despite posting to this NG seeeking help, the answer (for us)
was
> found in a third-party NG. It involved resetting the local security
policy
> on the XP Pro machine
> back to default values. The steps we followed were:
>
> 1. Change the computer name to "whatever" and then join the PC to the
> workgroup "WORKGROUP"
> 2. Restart the computer and log on locally as the administrator
> 3. Make sure the OS has all the latest patches.
> 4. Start>Run>mmc> then add "Security Configuration and Analysis" and
> "Security Templates" snap-ins.
> 5. Click on the Security Configuration and Analysis node and follow the
> instructions on the right to "Create a new database."
> 6. Import the Setup Security Template
> 7. Apply the template, reboot
> 8. Now try to Join the PC to the new Domain
> 9. If you continue to get the error, restart the PC and rerun steps 4-8.
>
> If the PC was a member of an SBS2K domain, you don't need to
> run the "connectcomputer" wizard on the ws as suggested when creating new
> computer accounts; join the domain manually. Sure, your browser won't
> default to companyweb but, heck!
>
> HTH
>
> Norm Hughes
>
> "Reed" <reedone@comcast.net> wrote in message
> news:258c101c46090$dd8ba490$a401280a@phx.gbl...
> > I have an XP Pro client that can't join the domain. From
> > the client side, when I use the NetworkID wizard from My
> > Computer, I get an "Access Denied" error. When I try
> > using the ConnectComputer through IE, it leads me through
> > the process of selecting the user and the computer name
> > (both are defined on the server), but at the end, it just
> > says that an error was encountered.
> >
> > Other computers and servers in our office have joined the
> > domain.
> >
> > Any ideas?
> >
> > Thanks,
> >
> > Reed
>
>
>

Relevant Pages

  • Re: VFP 9: Help with sending/receiving XML via FTP
    ... Be prepared to answer the coming questions - I have seen too many setups where security was slapped on in a hurry. ... FTP server and the risks of someone connecting with FTP client, ... Technology in itself is so used that "administration" can be handled by almost anybody - less need for admin knowledge. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Security Update KB893066: Is it safe?
    ... At work, connecting via my ... corporate network, the exact same computer with the security patch installed ... >>> Transmission Control Protocol packets over raw Internet Protocol ...
    (microsoft.public.windowsupdate)
  • [NT] DoS Found in Ssdpsrv.exe (UPnP)
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... By connecting to a computer running Ssdpsrv you are able to crash the ...
    (Securiteam)
  • Re: Local Resources availablity
    ... I guess this is not considered to be a security risk, ... Anybody ever seen whether a bugbear infected host LAN or PC will spew paper ... So, for better or worse, the best indication about the port redirection is ... In that warning it says that connecting the ...
    (microsoft.public.windowsxp.work_remotely)