search for: smb6

...ns our Samba file servers carry a lot of aliases. Now that they have become AD Members I did set a lot of CNAMEs in the AD DNS (using the Windows DNS Tool). Most of the aliases do work, but not the CNAMEs which carry the name of server which did previuosly exit. E.g. we used to have a server named smb6. I rsync'd the content to a new server named smb8, shut down the old server and set a CNAME smb6 pointing to smb8. Using Windows 7 no problem to access the server with \\smb6. Using Windows 10 I can't access it. \\smb8 and other CNAMEs do work. Then I deleted the smb6 computer account i...

...carry a lot of aliases. > Now that they have become AD Members I did set a lot of CNAMEs in the AD > DNS (using the Windows DNS Tool). Most of the aliases do work, but not > the CNAMEs which carry the name of server which did previuosly exit. > > E.g. we used to have a server named smb6. I rsync'd the content to a > new server named smb8, shut down the old server and set a CNAME smb6 > pointing to smb8. > > Using Windows 7 no problem to access the server with \\smb6. > > Using Windows 10 I can't access it. \\smb8 and other CNAMEs do work. > > Th...

...w that they have become AD Members I did set a lot of > CNAMEs in the AD > > DNS (using the Windows DNS Tool). Most of the aliases do > work, but not > > the CNAMEs which carry the name of server which did previuosly exit. > > > > E.g. we used to have a server named smb6. I rsync'd the content to a > > new server named smb8, shut down the old server and set a > CNAME smb6 > > pointing to smb8. > > > > Using Windows 7 no problem to access the server with \\smb6. > > > > Using Windows 10 I can't access it. \\smb8 and...