New
#11
Make sure that Guest account is enabled.
Networking issues since upgrading to Win 10 1903. Public settings.
-
-
New #12
-
-
New #14
Yes I just managed to get them all working. All 3 PC's networked together visable and with full access. All I had to do was enable SMB1. So with Windows 10 1903 anyone whose running it won't be able to network shared folders at all unless then know to enable smb1? Shame on MS for doing this and breaking everyone's network who upgraded to 1903.
-
New #15
They are doing it because of the risk associated with SMB1.
This way they know the client turned it on and when the brown stuff hits the fan they can say not me.
clam1952 said how he is working around it, I do backup to my NAS with specific IP addresses, others map.
It would be nice if they could get explorer to work with a higher level of SMB that does not have the exposure.
I'm glad it is working.
-
New #16
My windows 10 Computer that has had no issues with this (version 1903, 18362.239) but, yesterday the onboard NIC died.
Of course, it ruined my network and since then I have not been able to view either my NAS or 2 WD My book live units in the
Network. I have done all the enable of SMB 1, I went into the options and enabled ALL the SMB 1 protocols and the SMB direct,
made PowerShell changes and I even have a HOSTS file that has all the IP address for my network and STILL, NOTHING.
Does anyone have an Idea please?
-
New #17
Hi there
Presumably you either replaced the NIC or added a USB type device.
I'd power the whole kybosh down including router and any phones / smart TV's etc. Wait 10 mins and then start things up again.
If you have any LINUX type NAS systems then in the samba file for older Linux distros sill reliant on SMB1 you need to change in the smaba.conf file the line (or add it if it isn't there) to maxprotocol = Nt1 as shown below :
[global]
# ----------------------- Network-Related Options -------------------------
#
# hosts deny = the hosts not allowed to connect. This option can also be used on
# a per-share basis.
#
workgroup = WORKGROUP <================Your network name
server string = Samba Server Version %v
smb ports = 139 445 <========== optional -- I set these as I have these enabled in Router firewall
netbios name = REFUR <=============== Computer name
max protocol = NT1 <================== This line
............
This is assuming you have Samba v4 and above on your NAS
For Non Linux type of NAS's that don't use SAMBA or pure Windows just ignore the above SAMBA adjustments required.
Cheers
jimbo
-
New #18
Thanks for the reply. I did as you suggested but STILL no joy. As to the samba file, where do I find it?
I did ask the people at Buffalo but I got nowhere with that. I asked how to make the NAS work with SMB2 or 3 but?
Any more help you could give would be very much appreciated.
-
-
New #19
-
New #20
Hi folks
@Pendaws
Note on Windows you said you enabled ALL the SMB1 stuff --you need to UNCHECK the automatic removal SMB1 box. Why that option is even there when dealing with SMB1 I don't know -- just causes extra obfuscation.
That might fix your stuff without having to mess around with SAMBA but if you do have to fiddle with SAMBA :
The samba file is usually found on Linux NAS type systems under /etc/samba and the file itself is /etc/samba.conf.
Start searching with a file manager starting at top level root which is '/'
if you have a graphical file manager ("explorer") on your box then you should see something like this - and the samba directory is easily "findable". I'm running the KDE plasma GUI on a Linux Arch distro on this box with Dolphin as the standard file explorer -- those running a GNOME (another popular desktop GUI on Linux systems like UBUNTU etc) then there's the almost identical Nautilus -- other GUI's will have very similar graphical file managers / browsers.
If you don't have a graphical file manager then as root cd / then ls then cd to the /etc/samba and its a hideous pain but you'll have to use a command line editor such as vi or nano to edit the file --good luck with that one !!!!!!! It's hideous if in an emergency you ever have to use it !!!!.
After editing it test the file for correctness with the testparm command.
For getting SMB2/3 working - that depends on your hardware and the OS running in the NAS - some of the older network cards - especially if connecting to network via older wired cards won't support anything higher than the old SMB1 protocol (for some strange reason in later versions of samba you need to set to NT1). Ensure any Windows systems you have also have SMB1 enabled.
editing the samba file you need to be root (su) or sudo.
Cheers
jimboLast edited by jimbo45; 10 Sep 2019 at 06:48. Reason: Uncheck SMB1 automatic removal box too
Quote
Related Discussions
