Logon Script does'nt run when logon from a PC of another Domain 1

[WernerBlasius]

Hi,
when I try to logon at a PC with an Computerccount in DomainA with a useraccount from DomainB, the Logon Script won't run. Everything is fine when PC and Useraccount are in the same domain.
When the User is loged on and W2KPro is started, I can run the script manually from \\DC-DomainB\netlogon and it runs.
We have two W2K Domains and we have added a twoway trust between these Domains.
I've searched through this Froum, without a solution

Does anyone have a solution for me ?

thanks

 

[vbrocks]

Try logging on like this ....
At domaina computer

username: Mike@domainb.com

 

[WernerBlasius]

Sorry, I did not understand what you mean ...

Werner

 

[Jpoandl]

Make sure that your logon scripts are available on all domain controllers (Domain A and Domain B). It kinda of sounds like you are being authenticated properly but the logon script does not run. Make sure that on every DC your have the exact same logon scripts (\\servername\netlogon).

Also check each user account for the logon script configuration. It sounds like each user can logon to either domainA or DomainB...using the same user account name. Because you have duplicated user accounts on both domains, you have a lot more administration. You have to configure a logon script for "jsmith" on domainA and a logon script for "jsmith" on domainB. If the logon script is only configured on DomainA for "JSmith", when JSMITH logs onto domainB, he will not get a logon script.

-hope this helps...



Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[Rearview]

I have a similar (the same?) question. I have a trust between DomainA and DomainB. When a user with an account in DomainB tries to log onto a computer in DomainA, the logon script does not run. It works fine when the user logs onto a computer in DomainB (where his account is). Does anyone know a solution for this problem?

 

[vbrocks]

I tried to say before to logon like this...

username: Mike@domainwherethescriptis

username: Mike@domainA
or
username: Mike@domainB

 

[Rearview]

I fail to see how that would make any difference, vbrocks. You still chose your domain in the drop down list when you log on.

I did solve my own problem. Two things:

First, I needed to change the Group Policy setting described here:

http://support.microsoft.com/?kbid=823862

Then, I had to append my FQDN to the workstations I want to log into in the "append these DNS suffixes" DNS properties of the TCP/IP properties (I did this through group policy). I guess the computers were not recognizing the name of the server from which they needed to run their logon scripts.

 

[vbrocks]

Thanks for sharing that with us Rearview...
Here is a star for that one....