Problem: one XP PRO and two Domains

  • Thread starter Thread starter robert
  • Start date Start date
R

robert

Problem: one XP PRO and two Domains-

I have a PC running XP PRO. The PC is on network (A) in Domain (A) running
on W2000AD using User Name & Password (A). I want this PC to also be able to
connect to Network (B) in Domain (B) running W2000AD using User Name &
Password (B). The connection is via the internet using VPN. In order to
access the network in Domain (B), I have to change the XP PRO PC System
Properties from Domain (A) to any Workgroup and then join Domain (B). Is
there anyway of doing this without all the configuration changes?

Appreciate any ideas, suggestions.



robert
 
It would probably be easier to not even have your computer as a member
of either domain.. You can still access resources using UNC path and
your domain username in password. The drawback is that you do not get
the manageability of the network (group policy, etc...)

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Thanks for your help. I believe the group policy manageability is the
problem. I was given a .NET application on domain (B) that I need to allow a
remote XP PRO computer user to run from the other domain (A). The only way I
have been able to get the application to run remotely is by having the XP
PRO computer belong to domain (B) where the application resides, and using
"RUN AS" under an authorized user of domain (B) credentials. I was not able
to get the application to run if the XP PRO PC was made part of a Workgroup,
although I did have access to the network. Is there a way of running an
application on the remote domain (B) using, "RUN AS", with the authorized
user's credentials (B), but not having the XP PRO computer a member of the
domain (B)?

Appreciate any and all suggestions,



robert
 
Actually good question.. I have never had this type of issue come
up... I can access any network resources while in workgroup mode with
a domain un/pw... It appears that this application may try to open
up a connection to a server (maybe SQL or some other type of
connection) that requires domain authentication... The only way I
know to make this work easily is to set your domain username and
password information in the "Manage my Network Passwords" option under
User Accounts.. I set this up as a default for *.mydomainname.com
with my domain username and password... Now whenever I try to access
domain resources (like printers), I automatically get logged on.

You might want to try this on a setup on your network to see if this
would work with your particular application.

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Thanks I will give it a try. By the way, would using W2000 RAS or W2003 RAS
on the domain (B) solve this problem without having to make changes on the
XP Pro client?

Again thanks, appreciate all your help and suggestions.

robert
 
It wouldn't make any difference, I believe... Try the Manage my
Network Passwords just to see what happens...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
I added the username@domain(B) and password(B) in, "Manage my Network
Passwords", while the XP Pro was a member of domain(A). Connected to domain
(B) via internet and VPN. Was able to access domain(B) resources without
having to give username@domain(B) and password(B). Attempted to start .NET
application on domain (B). The following is how the .NET application
authentication progressed before it failed:



Name: domain(A)\ username

Is Authenticated: True

Authentication Type: NTLM

Is In domain(B)\ Net Application Users*: False



*( W2000 AD Global Security Group authorized to use the .Net Application)

Also was not able to run the application using "Run As" a known authorized
username@domain(B).



When the XP Pro PC is then made a member of domain (B), here is the .NET
application authentication progress and it run successfully:



Name: domain(B)\ username

Is Authenticated: True

Authentication Type: NTLM

Is In domain(B)\ Net Application Users*: True

Also am able to "Run As" with any other authorized username@domain(B)

Any Ideas? Have a happy holiday in case we don't touch base for a while.
Robert



Jeffrey Randow (MVP) said:
It wouldn't make any difference, I believe... Try the Manage my
Network Passwords just to see what happens...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

Thanks I will give it a try. By the way, would using W2000 RAS or W2003 RAS
on the domain (B) solve this problem without having to make changes on the
XP Pro client?

Again thanks, appreciate all your help and suggestions.

robert

in message news:[email protected]...
Actually good question.. I have never had this type of issue come
up... I can access any network resources while in workgroup mode with
a domain un/pw... It appears that this application may try to open
up a connection to a server (maybe SQL or some other type of
connection) that requires domain authentication... The only way I
know to make this work easily is to set your domain username and
password information in the "Manage my Network Passwords" option under
User Accounts.. I set this up as a default for *.mydomainname.com
with my domain username and password... Now whenever I try to access
domain resources (like printers), I automatically get logged on.

You might want to try this on a setup on your network to see if this
would work with your particular application.

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone


Thanks for your help. I believe the group policy manageability is the
problem. I was given a .NET application on domain (B) that I need to allow a
remote XP PRO computer user to run from the other domain (A). The only way I
have been able to get the application to run remotely is by having the XP
PRO computer belong to domain (B) where the application resides, and using
"RUN AS" under an authorized user of domain (B) credentials. I was not able
to get the application to run if the XP PRO PC was made part of a Workgroup,
although I did have access to the network. Is there a way of running an
application on the remote domain (B) using, "RUN AS", with the authorized
user's credentials (B), but not having the XP PRO computer a member of the
domain (B)?

Appreciate any and all suggestions,



robert

in message It would probably be easier to not even have your computer as a member
of either domain.. You can still access resources using UNC path and
your domain username in password. The drawback is that you do not get
the manageability of the network (group policy, etc...)

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
Click to expand...
Click to expand...
Click to expand...
 
OK, it is still trying to auth with the original username/password....

You might want to escalate this to a .NET dev group.....

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

I added the username@domain(B) and password(B) in, "Manage my Network
Passwords", while the XP Pro was a member of domain(A). Connected to domain
(B) via internet and VPN. Was able to access domain(B) resources without
having to give username@domain(B) and password(B). Attempted to start .NET
application on domain (B). The following is how the .NET application
authentication progressed before it failed:



Name: domain(A)\ username

Is Authenticated: True

Authentication Type: NTLM

Is In domain(B)\ Net Application Users*: False



*( W2000 AD Global Security Group authorized to use the .Net Application)

Also was not able to run the application using "Run As" a known authorized
username@domain(B).



When the XP Pro PC is then made a member of domain (B), here is the .NET
application authentication progress and it run successfully:



Name: domain(B)\ username

Is Authenticated: True

Authentication Type: NTLM

Is In domain(B)\ Net Application Users*: True

Also am able to "Run As" with any other authorized username@domain(B)

Any Ideas? Have a happy holiday in case we don't touch base for a while.
Robert



Jeffrey Randow (MVP) said:
It wouldn't make any difference, I believe... Try the Manage my
Network Passwords just to see what happens...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
Click to expand...
Click to expand...
 
Jeffrey,

Can you suggest one? I have not been able to get an answer from the groups I
tried.

Appreciate your help,

Robert

Jeffrey Randow (MVP) said:
OK, it is still trying to auth with the original username/password....

You might want to escalate this to a .NET dev group.....

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

I added the username@domain(B) and password(B) in, "Manage my Network
Passwords", while the XP Pro was a member of domain(A). Connected to domain
(B) via internet and VPN. Was able to access domain(B) resources without
having to give username@domain(B) and password(B). Attempted to start ..NET
application on domain (B). The following is how the .NET application
authentication progressed before it failed:



Name: domain(A)\ username

Is Authenticated: True

Authentication Type: NTLM

Is In domain(B)\ Net Application Users*: False



*( W2000 AD Global Security Group authorized to use the .Net Application)

Also was not able to run the application using "Run As" a known authorized
username@domain(B).



When the XP Pro PC is then made a member of domain (B), here is the .NET
application authentication progress and it run successfully:



Name: domain(B)\ username

Is Authenticated: True

Authentication Type: NTLM

Is In domain(B)\ Net Application Users*: True

Also am able to "Run As" with any other authorized username@domain(B)

Any Ideas? Have a happy holiday in case we don't touch base for a while.
Robert



in message news:p[email protected]...
It wouldn't make any difference, I believe... Try the Manage my
Network Passwords just to see what happens...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone


Thanks I will give it a try. By the way, would using W2000 RAS or
Click to expand...
W2003
RAS
on the domain (B) solve this problem without having to make changes on the
XP Pro client?

Again thanks, appreciate all your help and suggestions.

robert

in message Actually good question.. I have never had this type of issue come
up... I can access any network resources while in workgroup mode with
a domain un/pw... It appears that this application may try to open
up a connection to a server (maybe SQL or some other type of
connection) that requires domain authentication... The only way I
know to make this work easily is to set your domain username and
password information in the "Manage my Network Passwords" option under
User Accounts.. I set this up as a default for *.mydomainname.com
with my domain username and password... Now whenever I try to access
domain resources (like printers), I automatically get logged on.

You might want to try this on a setup on your network to see if this
would work with your particular application.

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

Click to expand...
Click to expand...
Click to expand...
 
Back
Top