Re: XP Home Client on Windows Standard 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Diane McCorkle (diane.mccorkle)
Date: 12/22/04 

Date: Wed, 22 Dec 2004 10:16:43 -0500

"wizard's dad" <wizardsdad@discussions.microsoft.com> wrote in message
news:A7515187-ABB4-45E0-A1BD-77A36F2DEAE3@microsoft.com...
> We have a mix of XP Pro and Xp home on a Standard 2003 server using a
> workgroup (no domain). The XP Pro machines connect without a problem but
> the
> XO Home machines require the user to enter a username/password to connect
> to
> a shared folder on the server. The XP Pro machines allowed the password
> to
> be saved but the XP Home don't have the "Save Password" checkbox on sign
> in.
> I upgraded one XP Home machine to XP Pro to see if that would solve the
> problem but no luck. Any suggestions? The users don't want to have to
> put
> in the username/password each time.
> --
> wizard's dad

Cached credentials are one of the features specifically not in XP home. This
was done to help keep them out of the business domain model networks since
it's cheaper then XP Pro.

Actually a pretty brilliant way MS came up with when they merged the NT4 and
98 sales base and kept a $100 difference between the business and home OS
prices.

XP Home machines are not meant to go on a domain, and you're finding out
exactly why.

Diane

Relevant Pages

  • Re: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
    ... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ...
    (microsoft.public.windows.server.sbs)
  • Re: Two XP Questions for new XP Pro User
    ... > Hello - I have just upgraded two of my Home LAN machines to XP Pro from ... > I've done this after having sucessfully upgrading my PDC from NT4 Server ...
    (microsoft.public.windowsxp.basics)
  • Re: XP Home Edition
    ... > XP Home can connect to Server 2003 provided the ... Upgrading to XP Pro is an option, but at almost $200 per copy it may not ... be worth the price if the machines will be replaced anyhow. ...
    (microsoft.public.windows.server.sbs)
  • "Could not connect to the printer..." error on W2K Pro
    ... I have an NT 4.0 server which hosts several shared printers. ... two of my W2K Pro SP4 users complained that they cannot ... * both users are administrators on their machines ...
    (microsoft.public.win2000.general)
  • EnterpriseService Component: problem enlisting in a distributed transaction
    ... developing that is responsible for writing data to an SQL Server. ... The problem host machines are running Windows 2000 Pro, ... The ES Component is set to Require transactions. ...
    (microsoft.public.dotnet.languages.csharp)