I am currently testing migration scenarios to replace 2 standalone W2K3 File Servers into 1 W2K8R2 Failover Cluster.
Everything went very well, shares are well accessible as long as I use the new File Server names, but...
... when I try to use DNS aliases (of the old servers), It is getting a nightmare!
First, each time I tried to to connect to the shares using the alias name \\tempsf\ I got an error message prompting for Duplicate name on the network.
I solved this first issue by applying the DisableStrictNameCheckingreg key (see below). The Duplicate name error message disappeared and I was able to access to the \\tempsf\ folder but it was empty however I have 2 shares well displayed when accessing it through the real file server name. Moreover, I confirm that :
- ping tempsf resolves correctly the real file server name and IP
- nslookup tempsf do the same
- net view \\realfileserver displays my 2 shares
- net view \\tempsf doesn't display anything :-(
Then, I almost tried everything currently documented :
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Add a new DWORD value called DisableStrictNameChecking and set to 1.
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Add a new Multi-String value called OptionalNames. Enter one or more aliases, one per line.
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Add a new DWORD value called DisableLoopBackCheck and set to 1.
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 Add a new Multi-String Value BackConnectionHostNames. Enter one or more aliases, one per line.
And also the SETSPN:
- setspn -A host/<your_ALIAS_name> <ServerrName>
- setspn -A host/<your_ALIAS_name.domain.com> <ServerNname>
But still nothing... Launch date is approaching, I am feeling so desperate...
Any idea? please... Thanks in advance,
Max
PS : Ahh yes, one more thing, we are using a third-party DNS here (Infoblox) but I don't think it could be the issue.