theniteowl
Programmer
We have a Win 2003 server that needs to copy files to a share on an old NT server.
Currently we log into the 2003 box and run the application and we have a drive mapping to the NT box using a local NT box account to establish the connect.
We are moving to running the application as a service and not having to log into the 2003 server.
My question is, how do we establish the connection to the NT share if we are not logged into the 2003 box?
Can a drive mapping be setup so that it is established when the 2003 server is booted up but not actually logged in?
Any way to avoid using a drive mapping? Our app uses the UNC path and the only reason for the drive mapping currently was to establish the connection and provide the credentials automatically.
The NT box is a vendor supported server so we cannot make changes other than setting up the local account. It is on an isolated network but using a second NIC to make a connection to our domain but it does not validate domain IDs which is why the local account is setup. We are using the same ID/Password on that box that we use for our domain account for the 2003 server.
At my age I still learn something new every day, but I forget two others.
Currently we log into the 2003 box and run the application and we have a drive mapping to the NT box using a local NT box account to establish the connect.
We are moving to running the application as a service and not having to log into the 2003 server.
My question is, how do we establish the connection to the NT share if we are not logged into the 2003 box?
Can a drive mapping be setup so that it is established when the 2003 server is booted up but not actually logged in?
Any way to avoid using a drive mapping? Our app uses the UNC path and the only reason for the drive mapping currently was to establish the connection and provide the credentials automatically.
The NT box is a vendor supported server so we cannot make changes other than setting up the local account. It is on an isolated network but using a second NIC to make a connection to our domain but it does not validate domain IDs which is why the local account is setup. We are using the same ID/Password on that box that we use for our domain account for the 2003 server.
At my age I still learn something new every day, but I forget two others.