Maintaining a network share after logoff

[Guest]

Is there anyway to maintain a network share after log off? We have a web app
that needs access to a share on a LAN server. The web server is in the DMZ.
However, if the machine reboots the mapping would fail along with the app. I
have maintained credentials from DMZ to LAN- we can map ok. What is the best
way of doing this? The problem here is that we have pdf documents located on
the LAN which we cannot publish directly on the DMZ as they are required by
internal apps- but they require to be published in the public domain. I
appreciate the best way would be to have the documents on the web server but
this is not practical as there could be 500000 of them!

 

[Pegasus \(MVP\)]

Is there anyway to maintain a network share after log off? We have a web app
that needs access to a share on a LAN server. The web server is in the DMZ.
However, if the machine reboots the mapping would fail along with the app. I
have maintained credentials from DMZ to LAN- we can map ok. What is the best
way of doing this? The problem here is that we have pdf documents located on
the LAN which we cannot publish directly on the DMZ as they are required by
internal apps- but they require to be published in the public domain. I
appreciate the best way would be to have the documents on the web server but
this is not practical as there could be 500000 of them!

Your web application needs to map a connection to the
machine that hosts the share, either by drive letter or preferably
by a UNC connection. It has to supply suitable account
credentials when doing so, e.g.
net share \\SomePC\SomeShare /user:SomeDomain\SomeUser SomePassword

You could do this in batch file that launches the web
application as its second command. There are obvious
security risks involved in doing this. A better way might
be to use a scheduled task to push your files out to the
web server at regular intervals.