Windows 10: Sharing TO W10 from W7 and most Linux distros SOLVED

Hi there.

This affects sharing TO W10 from other machines -- NOT FROM W10 TO other machines which seems to work just fine.

Ms has changed some security aspects of file sharing over networks in W10. The changes only affect W7 and earlier Windows OS'es and most Linux distros using SAMBA.

You need to BLOCK INBOUND port 139 on your WINDOWS 10 machine if you use something like NetBIOS to access your shared machines on a network. If you use an LMHOSTS file (I don't as I don't want fixed IP addresses on a network) or actual IP addresses to access your shares then you don't need to do anything.

(The two ports in question here are 139 and 445 - only block TCP port 139).

Note - you need to block the INCOMING port on the WINDOWS 10 Machine. If you don't have the firewall enabled then you will still get problems sharing via hostname - so enable the firewall (Windows).

What apparently is happening is that Windows 10 is only listening for PORT 445. SAMBA / W7 machines check Port 139 first -- wait for an acknowledgement (or other response) - and then if negative send out port 445. On W10 port 139 doesn't return any acknowledgment so on Linux SAMBA times our while Windows issues the message Cannot access .... etc.

This fix might not work in the final W10 release but it's still working even in build 9879.

Remember the problem is sharing TO Windows 10 -- NOT FROM WINDOWS 10 and only from Linux (samba) or Windows releases 7 and earlier.

(For those using Storage spaces - you have to share at FOLDER / DIRECTORY level as there's no "Physical Volumes of course).

If you are using CENTOS 7 as a Host you may still find that you can SEE the shares FROM Windows but can't access them -- for some reason you need to set wins = yes in the samba conf file if you are using a typical home LAN (not domains etc).

Cheers
jimbo

:)

 

Is it possible to install Linux in a Windows virtual Machine?

Absolutely possible (in fact easy) to Install most Linux distro's in Hyper-v. I have Ubuntu and OPEsuse running on this PC. BTW Hyper-v and most linux distro's are free.

 

Windows 10 unable to join homegroup with Windows 7

All of mine share the same login and password...That did not solve the problem. I still have a brand new desktop that shipped with W7/Pro, and laptop that I stupidly upgraded to W10, and the W10 laptop STILL cannot see the HomeGroup on the primary W7 system.

Is Microsoft EVER going to solve this problem?

 

W10TP b9926 won't connect to any other machines in our house (they appear in the Network window in File Explorer).
I didn't have this trouble with the other builds.

I'll try your suggestion out.

 

Local Area Networking is totally broken in my b9926.

I tried:

• Blocking port 139 everywhere I could find it - no effect
• Turning the Firewall off - totally disables my network
• Disabling NETBIOS - totally disables my network

I don't know how MS expects ordinary users to be able to deal with this.

 

I have the same issue.

Can see the other computers (all running W7), just cant get data from them. Error message \PC is not accessible. You might not have permission blah, blah, blah. The account is not authorised to log in from this station.

They can connect to the W10 machine.

All was working fine in b9789

 

Hi there

apparently (different error from what I've been getting (solved on my LAN) there's a registry fix for this. I never got the message "not authorised..." etc so that's a different problem -- suppose it depends on how your LAN is set up.

I can't find the link but it's on the Forum. People who have made the registry fix says it solves their problem.

Cheers
jimbo

 

I used the registry fix, worked straight away.

 

I used the registry fix, worked straight away. Can you please post the link or thread title? *Smile

 

I used the registry fix, worked straight away. Can you please post the link or thread title? *Smile I think it is in

Build 9226 - cant connect to shares?



Message # 13 has it.

 

Thanks labeeman. *Smile

I was wondering if it was related to "Lanman" settings.

In W7, I have to edit "Lsa" & "LanmanServer" to allow my media box to connect.

 

As an experiment, I just copied my b9879 VM and then performed an "upgrade" to b9926 on it.
The Network was broken after the "upgrade".

I've tried two clean installs & an "upgrade" and the Network was broken in all of them.
*Doh