![]() ![]() Now all the machines can ping one another and network accesses in the IP realm are right. ![]() Much hilarity ensued, but I finally tracked down and got all of the IP addresses modified. I had a router die, and took this as the opportunity to put in a DD-WRT based one. I'm currently chasing down why none of my machines can see my FreeNAS box any more. :( Well, it's probably so, but not for my network. Within the local Group Policy Editor, select “Administrative Templates”ĭouble click “Enable Insecure guest logons” option Right click the Windows Icon at the bottom left of the task bar, or select the windows key + r You can change this setting within your group policy settings. Within the latest “Windows 10 Fall Creators Update” the Guest access in SMB2 is disabled by default. Prior to version 1709 everything still works. In Windows 10 version 1709 guest access in SMB2 is disabled by default. My FreeNAS shares using SMB and forces guest access. I don't think my setup is unique so hopefully this will help someone. It has taken me two days to get to the bottom of the problem. ![]() I used to be able to access FreeNAS shares using Windows 10, then two days ago I stopped getting access with a generic can't access this share type error. ![]() I recently changed to Windows 10 because my new system is a Ryzen 5. This is not really a thread asking for help, hopefully this can help some others. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |