The world – leading commercial SMB file sharing solution
YNQ is the Visuality Systems SMB Server and Client solution developed for non-Windows systems to allow interoperability with Windows-based machines. Written in ANSI C and being hardware independent, YNQ is highly portable to different platforms and can run on any processor. With YNQ incorporated, a system can write, edit, copy, delete and update over the network without transferring the entire file to the local disk. While offers excellent performance YNQ only requires a small resource footprint, which makes it ideal for embedded and IoT systems.
Reasons to choose YNQ
Want to learn more?
YNQ Products and Components
Being a modular library, the YNQ is composed of four separate products:
Full SMB client functionality.
Full SMB client functionality with the ability to register the machine to the corporate Active Directory.
Full SMB server functionality.
Full SMB server functionality with the ability to register the server to the corporate Active Directory and the pass-through authentication ability.
YNQ may be seen as an SMB Server, an SMB Client or a NetBios Daemon.
Porting or integration?
Porting is needed when you use YNQ on a new platform (Operating System, CPU, ROTS). Porting YNQ involves implementing its low layer utilizing the most common platform services. This process is seamless and requires minimum effort.
On the other hand, integration is available for selected platforms, such as Linux/UNIX, VxWorks, Nucleus, iOS, and Windows. Integration occurs when you incorporate YNQ into a new solution on a ported platform.
Usually, the integration is flawless
There is a distinction between Project-Dependent or User-Defined (UD) and System-Dependent (SY) layers. SY corresponds to porting, while UD corresponds with the process of integration.
YNQ has three levels of modularity, which allows for multiple ways of incorporating YNQ into your solutions.
The first level is high in the stack and delivers the API/Protocol level capabilities. These are the APIs (NQ), the SMB Server, the SMB client, and the NetBios daemon. Integration requires minimal effort and is independent of the OS you choose. The second level delivers the services needed to integrate into an SMB environment. These are authentication, common, and network services.
The third level is the OS-level components. These are system, user-defined, and driver. Modify these as needed for your OS during porting or integration.
Going forward with
by your team
support & guidance
maintenance & support
What sets Visuality Systems apart?
Collaborating with Visuality Systems
Other Visuality Systems Solutions
Implementation For all storage systems
client library The only commercial Java solution providing full SMB3 support