Re: Logon script problems logging onto another domain in forest

From: ptwilliams (ptw2001_at_hotmail.com.donotspam)
Date: 12/15/04 

Date: Wed, 15 Dec 2004 05:53:04 -0800

Yes, I wasn't very clear in my post. I meant authenticating with a DC in a
different domain.

The point I was trying to make is that SYSVOL, and therefore netlogon, is
domain-specific, and you may be calling the netlogon share of the trusted/
trusting domain.

You did, however say that you were logging onto b with an account from a, so
I apologise.

In your scenario you are accessing a Dfs link - so you are being referred to
a share by the Dfs client. The user account stipulates that this script
resides in the netlogon folder. The netlogon folder is accessed by the Dfs
client based on the DNS/IP locator call to DNS. I'm unsure whether or not
the Dfs client uses the \\domaina\netlogon (because your account resides in
this domain), or \\domainb\netlogon (because you are authenticating with a
domainb DC and domainb is closest).

When you logon to the Brussells domain, and this works, is there a copy of
this script in the \\domainc\netlogon folder?

If there is, you should copy this script to the \\domainb\netlogon folder.

If there isn't, then you may get a good idea of what's going on by following
this using Network Monitor... 

--
Paul Williams
http://www.msresource.net/
http://forums.msresource.net/
"bushgeeza@yahoo.co.uk" wrote:
> I don't believe that is the case.  From a terminology point of view,
> lets just clarify what logging on to a domain actually entails:
> 
> It is possible for a user from domaina to authenticate to resources in
> domainb, however it is not possible for a user in domaina to actually
> "log on" to domainb (because their account does not exist in that
> domain).  Therefore whenever domaina user logs on to a server from
> domainb, they are actually logging onto domaina and gaining access to
> the server in domainb, and must get the logon script details from
> domaina.
> 
> I have done a test where the user is logging onto a server in domainc
> (Brussels) and the script executes successfully, which proves this.
> However, I still do not have a solution to my original problem.
> 
>

Relevant Pages

  • Re: log into a system
    ... You can do this with a DOS or WSH script. ... You can leave the password off, and you will be prompted for it when the script is ran. ... oWS.PopUp "Connection to one or more shares failed!", 3, "ERROR: Authenticating", vbExclamation ...
    (microsoft.public.win2000.cmdprompt.admin)
  • Re: Login Script
    ... Some are authenticating over a LAN and others are authenticating over a WAN. ... in the script seems like it is not running. ... If Not oFSO.FileExists (strshortcut) Then ...
    (microsoft.public.scripting.vbscript)
  • Re: Startup script
    ... the netlogon folder so that I can run sysocmgr.exe and install SNMP. ... The part of the cmd script ... Every file copy lists as "0 files copied" in the log file. ... permissions of the computer object elsewhere in the domain. ...
    (microsoft.public.windows.server.general)
  • Re: Creating Logon script?
    ... If the scripts are in the NetLogon folder, you only need to specify the ... If the client is Win9x or NT, the logon script should be a batch ... I've specified the path in the users profiles. ...
    (microsoft.public.windows.server.scripting)
  • RE: Logon Script Placement
    ... You'll place the logon script within the Netlogon Folder. ... Solution for a Small/Medium-Sized Business - MCP 70-282 ... Microsoft Online Support: http://support.microsoft.com ...
    (microsoft.public.windows.server.sbs)