mercoledì 27 febbraio 2013 10:27
we could not get access to a server using the DNS alias in Windows Explorer but pinging that name or using it to get a website via HTTP from the IIS on the server or connecting to SQL Server on that server worked properly. After using the following registry hack, it worked also for UNC paths in Windows Explorer:
I found out that it also works with Windows Server 2008 (R2):
- Value name: DisableStrictNameChecking
- Data type: REG_DWORD
- Radix: Decimal
- Value: 1
Are there any known problems or disadvantages if I use that trick?
Thanks & regards,
Tutte le risposte
venerdì 1 marzo 2013 06:13Moderatore
Wrong information provided. Please refer to the other reply.
venerdì 1 marzo 2013 06:18
Thank you for your reply.
I know that it works with Win2k8 R2.
I wanted to know if there are and what are the disadvantages if I use that registry hack.
mercoledì 6 marzo 2013 07:32Moderatore
As it is listed as a resolution of the issue, it is an accepted way to fix the issue.
- Modificato Shaon ShanMicrosoft Contingent Staff, Moderator giovedì 7 marzo 2013 09:10
mercoledì 6 marzo 2013 07:42
are you sure that your article targets the same problem?!
In your article it says you can access the server by using its FQDN or its CNAME alias from another computer in the network and just locally it does not work.
It's also another registry key.
But in my case i can not access the server by using the CNAME alias from another and from the local computer.
So maybe that's another issue?!
giovedì 7 marzo 2013 06:23Moderatore
It's my fault about my previous replies...Sorry for the confusion.
Here is a (correct) link about apply the fix on a Windows 2008 R2 system:
And in the article you provided, actually it also mentioned to apply the fix on Windows 2008 and Windows 2008 R2 systems when trying to communicate through SMB1.0.
As both articles provided the same solution with no warning, it should be fine to be applied.
Again sorry for my previous reply. I will edit my first reply incase it cause more confusion...