Connection to a domain from a client in workgroup

Hi,
my situation is:
- Windows domain 2003 R2 with few clients XP Prof Sp2
- few clients XP Prof SP2 in workgroup

I need to create a vbs script that it is able to connect to the domain from
a client that resides in the workgruop. So, I suppose that the script must
contain the necessary information to connect to the specific domain. And when
the connection is established, the script must read some user properties and
the make some operation in the client.
How can achieve this goal?
Thanks.
Fr.

TDM
Tue May 06 09:45:17 CDT 2008


"framm07" <framm07@discussions.microsoft.com> wrote in message
news:42E6F1BD-6D5F-4E4E-B1F7-2C3184D4E0C0@microsoft.com...
> Hi,
> my situation is:
> - Windows domain 2003 R2 with few clients XP Prof Sp2
> - few clients XP Prof SP2 in workgroup
>
> I need to create a vbs script that it is able to connect to the domain
> from
> a client that resides in the workgruop. So, I suppose that the script must
> contain the necessary information to connect to the specific domain. And
> when
> the connection is established, the script must read some user properties
> and
> the make some operation in the client.
> How can achieve this goal?
> Thanks.
> Fr.

One possible solution that does not involve any
special scripting is to set up User accounts on
your server that have the same username and password
for the user logins on the client systems. You dont
mention what you want to connect to on the
DC, but if it is simply shared resources, then you
can run your script as is with no special need
for authentication if you set up the accounts
on the server. The only gotcha here is if the
user changes the password on the client system,
you will need to do the same on the server.

This leads to a debatable question, is this
a bug in Windows or not ? I personally
see this as a bug, but this continues to work
even in Vista. If there is a DC, with a user
account of "user1", and there is a client
that has NOT joined the DC, and is still
in "WORKGROUP", and the client account
is "user1", and the password is the same for
both the "user1" in the Domain, and "user1"
on the client system in "WORKGROUP", then
you have an open door on the DC, you do not
get prompted for any authentication. You are
still limitted on the DC by the permissions set
for the "user1" account on the DC, but it would
seem to me that some form of authentication
should take place due to the domain versus
workgroup. But, Windows seems to think
that if the User and PW match, let em in.
This also works client to client as well.
Any thoughts from the MVP's on this one ?


TDM