Access SMB-Share on localhost under different name

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_SHAREFiles$). 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 \LOCALHOSTFiles$).

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 etchosts 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?

UPDATE:

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.

This is an old post but I encountered this problem during Covid season while trying to work from home.

I want to redirect SMB server calls for \SERVERNAME (or in the example above PROD_SHARE) to being the local SMB on the computer.

Method

1. Add “SERVERNAME” to etchosts file with IP Address 127.0.0.1

2. Local Windows Authentication will pop up and give error because the computer does not recognize “SERVERNAME”. So disable authentication check for loopback by editing/adding the following registry value:

   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa > DWORD > DisableLoopbackCheck=1

3. Restart “Workstation” under services.msc.

Source: https://support.microsoft.com/en-us/help/926642/error-message-when-you-try-to-access-a-server-locally-by-using-its-fqd

Other methods (unverified):

Edit/add registry key:

HKLMSYSTEMCurrentControlSetServiceslanmanserverparameters  DWORD      DisableStrictNameChecking=1

Other Sources: https://support.microsoft.com/en-us/help/926642/error-message-when-you-try-to-access-a-server-locally-by-using-its-fqd

I haven’t tried this, but maybe the LMHOSTS file would help?

It’s like /etc/hosts for SMB server names. You can find it at %SystemRoot%System32DriversEtc (maybe it doesn’t exist, but at least on Vista there is an lmhost.sam sample file).

If I understand right, you want a machine in your backup environment to respond to the name of a server computer that’s running in your production environment.

It’s possible, but you may have some difficulties if there’s NetBIOS communication between the backup environment and the production environment.

Here’s the basic procedure for adding an alias name to a Windows Server machine.

• On the backup server, add a REG_MULTI_SZ value named “OptionalNames” in the registry at HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServiceslanmanserverparameters. Put the name you’d like the backup server to respond to in that value.

• Add a REG_DWORD value to the same registry key named “DisableStrictNameChecking” and set it to “1”.

Bounce the “Server” service (or reboot the machine).

Where you may have a problem is that the backup server is going to try to register this alias name in WINS and will broadcast it using NetBIOS over TCP/IP. Since you already have a computer with the alias name running you may get “duplicate computer name” messages. If you can firewall your backup environment away from the production environment for NetBIOS then this will be a non-issue.

Also, be aware that there won’t be any way to do Microsoft File and Print Sharing connections between the server with the alias name set and the real server computer using the NetBIOS name. You’ll have to “connect” to the real server computer from the backup server by IP address if you need that functionality.

I’m not sure if I’ve misunderstood the question or not, but I was wondering if maybe Microsoft DFS could be used in this scenario at all?