It's possible, but you may have some difficulties if there's NetBIOS communication between the backup environment and the production environment. 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. Restart "Workstation" under services.msc.Įdit/add registry key: HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters DWORD DisableStrictNameChecking=1 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa > DWORD > DisableLoopbackCheck=1 So disable authentication check for loopback by editing/adding the following registry value: Local Windows Authentication will pop up and give error because the computer does not recognize "SERVERNAME". Add "SERVERNAME" to etc\hosts file with IP Address 127.0.0.1.I want to redirect SMB server calls for \\SERVERNAME\ (or in the example above PROD_SHARE) to being the local SMB on the computer. This is an old post but I encountered this problem during Covid season while trying to work from home. The production and backup environment are not in the same network/domain at all, so there shouldn't be any name conflicts. Be sure that your username and password are correct". The error ist "Windows is unable to log you on. 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). I want to be able to use \\PROD_SHARE instead of \\LOCALHOST (but the result should be the same) Thanks for your answers so far, I think my question was far too complicated - actually, my problem is as easy as (my bad, sorry): 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?). Problem is, that the share path in the backup environment is different (this time it's on localhost, so the path is \\LOCALHOST\Files$). Now we don't want to change this config file when copying it to the backup server. This path is specified in a configuration file. This works pretty good, with one exception: The production system has to access some files on a share (ie. 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 scenario may seem a little weird at first ) OS is Windows Server 2003.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |