|
|
|||||||
Normally our PCs map drives using the following script: USE u: "\\SERVERNAME\data1\users\" + @userid USE p: "\\SERVERNAME\data1\projects" USE o: "\\SERVERNAME\data1\open" SELECT CASE InGroup("IT Dept") USE w: "\\SERVERNAME\data1\workgroup\it" CASE InGroup("Accounting Dept") USE w: "\\SERVERNAME\data1\workgroup\accounting" ENDSELECT The u: and w: drives depend on the active directory user id and group membership. This works great on our local network. In order for users to connect to our file server remotely, they must use VPN, which doesn't use windows authentication. Once the VPN connection is established, I can go to start, run, then type \\SERVERNAME\data1\... , I'm prompted for the AD ID and password and if I enter them correctly I can access the file server. If I run the above script, only o: and p: map while u: and w: fail. How can I get the user id and group membership passed to the login script so u: and w: map? Thanks! |
||||||||
|
|
|||||||
sounds like the workstations are not authenticating to the AD. can you try ingroup('\\DC\groupname') perhaps? |
||||||||
|
|
|||||||
not knowing your type of vpn or network settings, but one thing to try without knowing those, try to connect with FQDN. depending on your vpn/firewall setup, you might need to allow some additional traffic in the filters... |
||||||||
|
|
|||||||
Thank you for the replies. Perhaps more background info will help. The workstations connecting remotely are not part of the domain. They are employees' personal computers from home. Only certain IP subnets can access the domain, so remote users must use VPN. Once the VPN is established, the remote workstation is on a subnet that can access the domain. The VPN ID and Password are independent of the domain. This works correctly, as I can authenticate and access our file server once the VPN is established. However I can not get the login script to map drives based on the domain userid and group membership. It will map drives with static paths using the USE command only. Thanks again for your help! |
||||||||
|
|
|||||||
you will need to RUNAS the script file |
||||||||
|
|
|||||||
uhm. not really needing runas... change the vpn user script to ask for user info. once you know the username and password, you can use: use \\server\ipc$ /user:username passwd |
||||||||
|
|
|||||||
Thanks again for the replies. Lonkero, regarding the VPN user script, are you referring to a kixtart script that can be initiated after the VPN is established (my VPN doesn't use the active directory domain ID and password)? If so, would you please explain how to make a kixtart scipt ask for user info? An example would be great, or anything to point me in the right direction (I'm definately not a kix master guru). I appreciate everyone's help on this! |
||||||||
|
|
|||||||
There are three common ways of doing it:
If you use the KiXtart built-ins for a console solution then search the UDF forum for an alternative to GetS for the password prompt. |