I have a 'what should be an easy issue to resolve' networking/share access question for you guys.
Does anyone have any issues with accessing folder shares NOT using the Homegroup/Wizard method, but rather the 'advanced' or 'let me' set up sharing manually method - as in right clicking on a folder/drive and go to sharing and selecting the share name and permissions manually ?
Below is what I can do and cannot do since the last three Win10 IP builds. Thirty years in the IT/PC/COMMS field as an RF Engineer and I cannot figure out why this is an issue. Now bear in mine I have NOT done much on-line research yet, so perhaps I am overlooking something that is new within these latest builds, however, I don't see that being the case.
Can someone (the more the better) try setting up a Win10 IP (last 3 builds) share and then try to access it (via their MS Log-In account) from a Linux or BSD box via SMB/CIFS using 1/2/3 a protocol and let me know what happens?
Can/Cannot Do
|
Any Linux Box |
Accessing a share in |
|
Last 3 IP builds - others OK
|
NO |
|
Any Linux Box |
Accessing a share in |
|
Any non-IP box
|
OK |
|
(Last 3 IP builds) |
Accessing a share in |
|
Any non-IP box |
OK |
|
Win10 box (IP and non IP) |
Accessing a share in |
|
Any Linux box |
OK |
Note: IP refers to Insider Preview in this case.
Here is what I DO know:
- This is NOT an issue with respect to SAMBA/CIFS or versions thereof - the protocol in itself or on the Linux end.
- This is NOT a Linux networking or authentication issue.
- This is NOT an issue when trying to access a box with an active 'Local Windows user account' vs. an MS account.
- This is NOT a mis-configured services option on my end.
Thus, I conclude (without diving into anything yet) that it has to deal with:
- Win10 (at least the last 3 IP versions - for myself) and/or
- Authentication (on the Windows side) and/or
- Incoming requests only - as outgoing requests or attempts to access shares on other boxes work just fine.
To access ANY Win10 box with a local user account from Linux, you merely need to enter:
smb:\\IP addy or win box host name\share - e.g. smb:\\voip\archive or smb:\\192.168.0.x\archive - Providing all machines are using the same workgroup.
To access ANY Win10 box (earlier IP builds or non IP builds) with an active Microsoft Log-in Account from Linux, you need to enter:
smb:\\IP addy or win box host name\your user account@\share name - 'your user account@' does not (at least in previous cases) need the full IP address. The '@' after your user name should suffice, however, I found that using it in previous builds would work whereas not work without it.
There are different methods of the above protocol when accessing a MS Account Win10 box depending on authentication options and other Domain settings if one is being used.
From my iPod 6, I had no problems accessing the Win10 IP box with earlier IP builds using:
\\WORKGROUP\<user name> - That's it. This was from the app 'FileExplorer' and it filled in the host name upon auto-discovery of any box I had turned on. In my case, WIN10IP was the host name of the IP box.
The error I get from my iPod: Socket Connection Error
The error I get from any Linux box: Timeout on server - 192.168.0.7 (The IP of the Win10 IP Build 16232 box)
Okay....Thanks guys.
Feel free to move this post into the most appropriate forum.
Tim
ARS N9NU