(application server for ATN_TRNG is m38688, ip number is 152.2.190.190)

 There are special rules involved in authenticating from one
 Windows NT machine to another Windows NT machine when both machines are
 not in a common Windows NT Domain. Although you can use the "net use"
 command to authenticate to the IPC$ share on any Windows NT machine, this
 example will use mapping a drive to another Windows NT machine as the
 method of authentication. If you wish to map a drive to SHARE1 on
 SERVER1, which is a member of the AAA NT Domain, you need to authenticate
 to the AAA NT Domain with your AAA NT Domain username and password.

 From Windows NT, you need to right-click on the Network
 Neighborhood and select "Map network drive". Enter "\\SERVER1\SHARE1" as
 the path. If you are not configured to use the same WINS Servers as
 SERVER1 for NetBIOS->IP name resolution, you may need to specify the path
 as "\\XXX.XXX.XXX.XXX\SHARE1", where XXX.XXX.XXX.XXX is the numeric IP
 address of SERVER1. If your own Windows NT machine is configured to
 "Enable DNS for Windows Resolution" and you have entered SERVER1's DNS
 Domain Suffix in your "Domain Suffix Search Order", then you can still
 specify the path as "\\server1\SHARE1". For example, if SERVER1's DNS
 name is "server1.somedept.unc.edu", then its DNS Domain Suffix would be
 "somedept.unc.edu"). This explains why it is important for Windows NT
 machines to have NetBIOS names set the same as their DNS hostnames.
 Otherwise, you can specify the path with SERVER1's full DNS name such as
 "\\server1.somedept.unc.edu\SHARE1". Note that you cannot specify the
 path with a full DNS name under Win9x.

 Under the "Connect As" box, you should give "AAA\userID" with
 userID as your AAA NT Domain UserID. You will need to specify the NT
 Domain name before your username only if the Windows NT account you will
 be using to connect to SERVER1 is in the AAA Domain SAM database instead
 of in the local SAM database on SERVER1 itself. You will not need to
 specify an NT Domain if SERVER1 is a "stand-alone" server and not a member
 of an NT Domain.

Author:
* Jesse Aaron Safir, Chief NT Systems Engineer *
 * Network Consultants Group, AIS Distributed Computing