If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:SMB
BoxMatrix >> Lexicon >> Network-Protocols >> SMB | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
Computer | FRITZ | I18N | Telephony | Smarthome | Internet | Protocols | Multimedia | Formats | Hardware | Software | Research |
Protocol
Protocol: | SMB | Wiki | Freetz | IPPF | whmf | AVM | Web |
Short for: | Server Message Block | ||||||
Location: | Lexicon >> Network-Protocols | ||||||
Weblinks: | Wikipedia.int - Wikipedia.de - RFC-1001 - RFC-1002 | ||||||
Description: | Protocol for sharing files and printers |
Goto: FRITZ!OS - SMW-Browser
Details
SMB (Server Message Block
) is a protocol designed by Microsoft for sharing files and Printers in a Windows or MS-DOS
network. Since there are also third party solutions today SMB can now be accessed by pretty much every modern platfform.
There are 3 generations of the SMB protocol, with revisions each:
- SMB 1.0 -> CIFS
- SMB 2.0 -> 2.1
- SMB 3.0 -> 3.0.2 -> 3.1.1 (current)
While it could be run in other context SMB is mainly used on top of NetBIOS over TCP/IP (NBT)
, using these services:
NetBIOS Name Service
- Port-137-udpNetBIOS Datagram Service
- Port-138-udpNetBIOS Session Service
- Port-139-tcpSMB over TCP
- Port-445-tcp
Port-445-tcp permits to use SMB directly without NetBIOS.
The RFC links above cover the NetBIOS over TCP/IP (NBT) protocol, SMB itself is proprietary.
Even Microsoft does not really know which OSI layer SMB belongs to, they say "most say Application or Presentation layer"[1].
FRITZ!OS
FRITZ!OS uses 2 different solutions to proivide SMB support:
Samba
When SMB support was introduced AVM used the open source Samba package, which consists of:
- smbd - SMB / CIFS service - fw 4.28+
- nmbd - NetBIOS over TCP/IP Name Service - fw 5.01+
Due to limited ressources there was no name service in fw 4.x, so Fritzbox shares were not announced to the network.
In Windows shares had to be located by typing the UNC path \\fritz.box\<shared-folder>
into the Explorer address bar.
With the addition of nmbd Fritzbox shares could be found normally by browsing the network.
For licensing reasons AVM used an old Samba package, which is not GPLv3 yet but only supported SMB1.
This turned a problem for models up to gen. 7390 when Microsoft disabled SMB1 support in Windows for security reasons.
Windows could not access Fritzbox shares any more and AVM recommended to use FTP or the NAS instead[2].
For later models AVM had to implement a new solution:
YNQ
YNQ is a proprietary but highly portable, compact and modular SMB package developed by Visuality Systems in Israel[3].
It supports all SMB generations up to current 3.1.1. AVM licensed the embedded Linux server edition which consists of:
- nqcs - SMB / CIFS service - fw 7.08+
- nqnd - NetBIOS over TCP/IP Name Service - only in fw 7.08, later merged into nqcs
Visuality Systems officially licenses the SMB protocol from Microsoft, to keep their clients safe from any patent issues.
All in all a future proof and highly compact solution for the Fritzbox (approx. 400 kB max.). That's 10% of the Samba package.