Folder shares-Win10IP-Linux-Authentication Issue-MS acct- Etc.

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 - All my Linux boxes will not even 'SEE' this Win10IP box since 3 builds ago. It's not just a matter of the share, but the entire hostname.

	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 (in the Win10 IP Box) 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

You are a colourful character (you should blog ... after 30 yrs, a good pension supplement?)

Networking is a secondary Windows feature (IMHO).. hence Linux rules that 'domain' .... and with IP still in development, perhaps that aspect has not even been specc'd yet...

Although currently totally unnecessary for Internet access and local networks, Windows 10 seems to increasingly and preferentially use IPv6 over IPv4. So much so that it appears to ignore IPv4 altogether in some cases, and does not advertise itself over the legacy IPv4 network protocols, Master browser polling, etc.


Less than 18% of the Internet runs IPv6 alongside IPv4.

6to4 Tunneling protocols convert IPv4 addresses to IPv6, and add another layer of unnecessary complexity.

It is required for homegroups, LLDP, Link Layer Topology Discovery (network discovery), and so on,which are probably irrelevant for normal local networking. Your router probably doesn't handle IPv6 properly, and your ISP probably doesn't handle it either.

Remember Windows 7 used to provide a map of your network connections that didn't ever work properly - that was the topology bit, and the map hasn't survived to Windows 10.

Private networks can use IP addresses anywhere in the following ranges: 192.168.0.0 - 192.168.255.255 (65,536 IP addresses) 172.16.0.0 - 172.31.255.255 (1,048,576 IP addresses) 10.0.0.0 - 10.255.255.255 (16,777,216 IP addresses) - if you are using these, then only IPv4 is necessary. After all the rationale for IPv6 is protecting the future when IPv4 addresses will run out - Private IP addresses will not run out unless your local network is extremely large!

IPv6 can be turned off in the network adapter properties.

Microsoft offer Wizards to disable IPv6 properly,so that there are no side effects:

https://support.microsoft.com/en-us/...nts-in-windows

It may not help with your problem, but I'd be interested if it does!

@Fafhrd

Hi....yeah IPV6 is supported. I have a 1 GBit FTTH connection from a .gov provider w/ Mikrotik hardware. I have a block of 25 statics and while I do not personally use IPV6 for much myself, I do use it for my work here when remotely connect to Fermilab and Argonne National Labs. Both of which are operated by the Dept. Of Energy (DOE).

The fact that before the last three builds it working just fine tells me it's something in either my Win10 IP PC or within the IP release(s) themselves.

I am going to go through gpedit, etc. to see if something got messed up. Remember, I can connect to my Linux boxes (outbound), thus I have ruled certain things out.

I can't disable IPV6 for what I do for work when I am home and this issue really isn't a big deal as it only affects the one IP machine with inbound requests via the Linux machines. I did manage to get all the Windows 10 machines (non IP ones) to connect to the IP box, however, there is a 40 second delay when bringing up the credential/log-in box.

I will dive into it later today.

Tnx for the input though. I appreciate it.

@Superfly

I agree...heh. I only use them for gaming. PERIOD. Ya need networking if you wanna play online as you know. Linux is by far my favorite OS and started back in 95 if I recall... LOL
Tim

Superfly said:

Networking is a secondary Windows feature (IMHO).. hence Linux rules that 'domain'

Hahhah, so very true. Has been like this for the last 20+ years. Networking run smoothly on Unix based systems, but on Windows there is ALWAYS some problems.

With 10 100% identical Windows boxes, Windows version, hardware and software configurations, during networking, at least 2 of those boxes can either not connect properly to the other boxes, or the other 8 boxes can not connect to the other 2.

I have concluded long time ago that running a successful Windows networking environment is more about luck than skill configuring the right parameters.