I've gotten around this by simply making a username in the AD that matches
the User Account on the XP Home machine. The XP Home machine doesn't
officially 'log into' the AD, but it's user account will still be recognized
by the Domain Controller.
The domains I'e worked with aren't super-secure, so maybe that has a lot to
do with it. I'm sure someone will be able to explain the nuts and bolts of
it, but I've been successfuly doing this.
The AD is simply an easier way to store massive amounts of information about
User Accounts, Computers, Printers, Shared Folders and other network
resources. The AD allows you tyo centralize all that info. Computers that
log into that domain then have access to browsing the information through
AD.
If your WorkGroup name is the same as your Domian name, all the resources
available on the network will show up in "Network Places" (in a perfect
world that is) but when you try to access them the AD Controller basically
asks "Who the hell are you?". If you've logged onto that AD then that
question has already been answered. If you're not logged in, it should ask
you that same question via a Username and Password Prompt.
You can either manually enter this info in, or write a small batch file that
runs on startup (i.e. "net use \\server\resource password /user:Username) or
do like I said initially and just create an account in AD that matches your
XP Home machine's login creditrials (no blank passwords, please).
----- Original Message -----
From: "Scott" <
[email protected]>
Newsgroups: microsoft.public.win2000.printing
Sent: Wednesday, October 08, 2003 12:41 PM
Subject: Re: Workgroup PC to Print to a Domain Printer