I tried to find an answer to my issue but haven't been successful so far. Maybe I couldn't find the right search terms, so please apologize, if the question has already been answered and I was just not able to find it.
In our windows domain network the server (DNS, AD, Files) failed, and is currently not available. However, I have access to the data stored on the server, for instance via a USB memory stick. On the local machine an application is usally used which accesses its program files on the network drive. But the app won't start anymore due to the missing network drive. My idea was to somehow mimic the network drive with the memory stick attached. However, it fails as authentication from the domain controller is required.
Here the bullet points:
- The server SRV provides a network share at \SRV\Appdata
- On the local machine (PCNAME) the user USR starts the application which looks for the data stored in \SRV\Appdata. The user provides his credentials to get access.
Now, since the server is down, i tried the following:
- Mount the usb device which contains Appdata at the root level
- share "Appdata" via network, such that it is accessable via \PCNAME\Appdata
- Create an entry in the
hosts
file with:
127.0.0.1 SRV
- After reboot, \SRV\Appdata seems available. But I have to enter credentials, and they cannot be validated due to the missing domain controller. Is there a way to circumvent this? I mean, I have the data, I just have to tell the app to look somewhere else for Appdata.
A short remark, I'm logged in on the local machine with a domain account. But the credentials are already cached. Other domain accounts which are not cached, are not able to log in.
System details:
- SRV: Windows Server 2019
- PCNAME: Windows 10 20H2