Natively, Windows will not do SMB over any ports other than 445 or 139 (its choice), and I'm sick of playing whack-a-mole with workarounds for the various Bad Things that Microsoft keeps adding to Windows to fsck up tunnelling SMB over SSH port forwarding. What I have in mind is a little command line app that would let me do something like
Securing Windows SMB and NetBios/NetBT Services – … It uses the following TCP and UDP ports: - UDP port 137 (name services) - UDP port 138 (datagram services) - TCP port 139 (session services) NetBIOS over TCP/IP (NBT) is installed and enabled by default for backwards compatibility with old systems (or SMB implementations); however Microsoft SMB Protocol can be used without Microsoft NetBIOS. SAMBA Configuration Within SAMBAs smb.conf this can be controlled by: disable netbios = yes smb ports = 445 If you want to support both use: disable netbios = no smb ports = 139 445 The big question now is: How does a Microsoft Client handle all this? Windows 2000 and later systems setup two connections simultaniously to a server one on port 445 and one on port 139. [SOLVED] Ricoh Aficio MP C3002 scan not working - Printers
Windows 10 cannot access shared folder, do not use port
Mar 12, 2013
Ports 139 and 445 open - Linksys Community
SMB Ports 139 and 445 Submitted by gma on Sat, 12/21/2019 - 04:52 The SMB protocol enables “inter-process communication,” which is the protocol that allows applications and services on networked computers to talk to each other – you might say SMB is one … GRC | Port Authority, for Internet Port 137 UDP NetBIOS name query packets are sent to this port, usually of Windows machines but also of any other system running Samba (SMB), to ask the receiving machine to disclose and return its current set of NetBIOS names. Related Ports: 138, 139, 445 Ports used for connections - Configuration Manager By default, the HTTP port that's used for client-to-site system communication is port 80, and the default HTTPS port is 443. Ports for client-to-site system communication over HTTP or HTTPS can be changed during setup or in the site properties for your Configuration Manager site. CIFS - NetApp CIFS uses UDP ports 137 and 138, and TCP ports 139 and 445. Your storage system sends and receives data on these ports while providing CIFS service. If it is a member of an Active Directory domain, your storage system must also make outbound connections destined for DNS and Kerberos.. Starting with Data ONTAP 7.3.1, CIFS over IPv6 is supported. CIFS over IPv6 uses only port 445.