|  | 
| 
 Edumacate me on SMB One of NAVs died last year, so I brought out an old one. This is used at the house, but mostly for backup from the office. Apparently, the old NAV uses SMBv1 Windows 10 does not automatically support SMBv1 anymore, since it is supposed to be insecure. The NAS can do NFS and iSCSI, but I cannot seem to get Windows 10 to play with those... The NAS is EOL, so no more firmware updates... How risky is activating SMBv1 on Windows 10, if the only thing I connect is an internal NAS? | 
| 
 Properly hidden behind a firewall no issues. Or get a old desktop, a few drives, install Linux, set up software RAID-1 or -5, and use current versions of Samba/CIFS ... Also the possibility of installing OwnCloud and similar. | 
| 
 It’s a 30 year old protocol. It’s not what you connect via SMB, it’s what someone else can connect. SMB1 is highly vulnerable to man in the middle exploits. The question really is, what’s the sensitivity of the data you may be exposing? | 
| 
 Quote: 
 My real concern was activating SMBv1 on the Windows 10 machine. | 
| 
 Quote: 
 It’s depricated purely on security. | 
| 
 Quote: 
 | 
| 
 Quote: 
 | 
| 
 Or I can switch SMBv1 off when I'm outside | 
| 
 Quote: 
 Easier in my mind to leave enabled and just block it. | 
| All times are GMT -8. The time now is 12:52 PM. | 
	Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
	
Search Engine Optimization by vBSEO 3.6.0
	Copyright 2025 Pelican Parts, LLC - Posts may be archived for display on the Pelican Parts Website