vpn and mapped drive

[Alberto Brivio]

Dear ALL,

I have an application that should be able to upload data on a mapped drive
through a vpn and this environment must be ready at machine startup so
without any user logon.

I have defined a startup file in group policy, so vpn can start
automatically (by rasdial as suggested on this newsgroup) and for mapped
drive I 've flagged "reconnet on logon" but when I try to open the mapped
drive "access denied" is returned as error: so I have to disconnet and
reconnect the drive manually and then I can open the remote content (the
same behaviour using "net use" command)

Please, anyone can give me any ideas ?




Regards


Alberto Brivio

 

[Pegasus \(MVP\)]

Dear ALL,

I have an application that should be able to upload data on a mapped drive
through a vpn and this environment must be ready at machine startup so
without any user logon.

I have defined a startup file in group policy, so vpn can start
automatically (by rasdial as suggested on this newsgroup) and for mapped
drive I 've flagged "reconnet on logon" but when I try to open the mapped
drive "access denied" is returned as error: so I have to disconnet and
reconnect the drive manually and then I can open the remote content (the
same behaviour using "net use" command)

Please, anyone can give me any ideas ?




Regards


Alberto Brivio

You should not rely on mapped drives for background applications -
use UNC coding instead.

 

[Kurt]

You should not rely on mapped drives for background applications -
use UNC coding instead.

Even so, when you connect to the mapped drive manually are you prompted
for a username/password? If so, you may have a simple permissions
problem. Also remember that a startup script configured on the LOCAL
computer runs under LOCAL administrative credentials. If you want domain
admin credentials, you need to configure the startup script via a GPO.

....kurt

 

[Pegasus \(MVP\)]

Even so, when you connect to the mapped drive manually are you prompted
for a username/password? If so, you may have a simple permissions
problem. Also remember that a startup script configured on the LOCAL
computer runs under LOCAL administrative credentials. If you want domain
admin credentials, you need to configure the startup script via a GPO.

...kurt

Instead of putting your code into the startup script, put it into
a separate batch file that you invoke with the Task Scheduler
at logon time. You will then have the opportunity to specify
a suitable domain account.