Windows Basics: Question About Opening a UNC Path

Posted by MikhailCompo@reddit | sysadmin | View on Reddit | 3 comments

UNC Paths are in the format \\\\**Server**\\*Share*\\Folder\\Folder etc. In some instances, our client machines can paste the full path into Run or Explorer and it opens fine. Other examples, pasting the full path produces an error and the user must open \\\\Server\\Share first and only after than can then then paste the full path into Run or Explorer to open it. Can anyone elaborate on A) What causes the different behaviour? (different OS version, different SMB version, different permissions?) B) How a client authenticates with the server hosting the share when using SMB?

3 Comments

[-]

Reo_Strong@reddit

I've seen similar, but not the same issue when share permissions are set in a way that conflicts with NTFS permissions on the file structure. The last time I looked, 10+ years ago, the MS recommendation was to set share permissions as Everyone gets full control, and then use NTFS to restrict control. This may no longer be the recommendation, but its what I use to minimize issues. u/HotPieFactory is correct regarding your second question (NTLM or Kerberos).

HotPieFactory@reddit

> The last time I looked, 10+ years ago, the MS recommendation was to set share permissions as Everyone gets full control, and then use NTFS to restrict control. This may no longer be the recommendation, but its what I use to minimize issues. This is still the recommendation. And you may be right that the double authentication issue described by OP stems from mismatching permissions on these two points. Good stuff! :)

I've not seen that behaviour once in 20 years. Without knowing what the error is, it is hard to explain the different behaviours.

Reply to Post

3 Comments