This scenario may seem a little weird at first ;) OS is Windows Server 2003.
We make a daily backup from our production servers and just copy the entire application to our backup servers, where we want an exact duplicate from the production environment (more or less).
This works pretty good, with one exception: The production system has to access some files on a share (ie. \\PROD_SHARE\Files$). This path is specified in a configuration file.
Now we don't want to change this config file when copying it to the backup server. Problem is, that the share path in the backup environment is different (this time it's on localhost, so the path is \\LOCALHOST\Files$).
Is it possible (on the backup server) to somehow "redirect" all requests to PROD_SHARE to LOCALHOST, so we can use the exact same config files as on the production environment? We tried it using the etc\hosts file, but it doesn't work (connection seems to work, but a login dialog appears and we can't login - maybe this is just some policy problem?).
Does anyone have an idea?
Thanks for your answers so far, I think my question was far too complicated - actually, my problem is as easy as (my bad, sorry):
I want to be able to use \\PROD_SHARE instead of \\LOCALHOST (but the result should be the same)
I tried the answer with the alias name as well as with the LMHOSTS - both hat the same result as my first try with the HOSTS file: I can ping localhost using the different name, but when I try to open the SMB Share \\PROD_SHARE I get a login dialog (so the connection seems to work) where I can't login - even with the user credentials I just used to boot windows (Domain Admin). The error ist "Windows is unable to log you on. Be sure that your username and password are correct".
The production and backup environment are not in the same network/domain at all, so there shouldn't be any name conflicts.