SMB without port 445

Question

I have a samba share, and the network my devices are on blocks communication over port 445 (the standard SMB TCP port). Linux devices and Macs can connect to this device because they can communicate with the server using port 139 (NBT over IP), which is not blocked Windows devices, however, seem to insist they communicate over port 445.

Is there any way for me to tell Windows 10 to use port 139 without relying on port 445?

Solution

I got this working by disabling SMBv2/v3 on Windows 10:

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled

then Restart the computer. To reverse this change and re-enable SMBv3 run the following commands at at the elevated command prompt

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto

UPDATE: I've renabled SMBv2 on Windows 10 and tried all the protocols limits on the server. NT1 works. So you can just add the following line to the server main smb.conf file instead of the above. I prefer this method because it will affect all my Windows 10 machines centrally:

server max protocol = NT1

Comments

[PythonNut]

Don't you mean server max protocol?

[Paperino]

Correct. I might have tried client and it didn't work.

[Curious]

ISP screwed up in not blocking ports 137-139...or they are intentionally trying to kill off machines of people too ***** to update to something less vulnerable.

[I say Reinstate Monica]

This needs to come with a big warning label: SMB v1 IS EXTREMELY VULNERABLE AND CONTINUED USE CAN RESULT IN DEATH OR SERIOUS INJURY

[Geordie]

Yup, in fact trying to use older SMB versions is detrimental to everyone since the reason these ports are so widely blocks is because 1/2 have a lot of security holes. 3 is apparently internet safe but it's legacy still haunts it