Since its introduction in 1999, SFU plays a key position that supports heterogeneous networks like Windows and UNIX systems to functionally integrate. SFU has kept up with the changing times, it has extended and substantially improved the tools and bi-directional integration of the solution and improved functional performance.
The SFU toolset enables businesses to build solutions to manage the interoperation of both Windows and UNIX computing assets across the enterprise. By providing interoperability tools and protocol support to unify these systems, SFU makes the achievement of this goal as simple and straightforward as possible.
Consequently integrating Microsoft Windows and Linux solutions is achieved by the use of a file sharing protocal called Samba. This makes it possible for the configuration of Linux Servers that they appear on the network and PC users like Windows based server. SMB can be traced back in the days of DOS time when IBM used SMB to communicate with the original network cards. IBM moved SMB token ring and then to Ethernet. It is until the turn into the new Millenium that SMB was integrated into the NetBIOS.
With the release of version 3.0 in May 2002, Microsoft replaced the utility and shell emulation layer of previous versions with Interix technology. Interix is a full application execution subsystem running beside the Win32 subsystem that lets you compile and natively run UNIX programs and scripts on Windows operating systems. It might always help during negotiations with Microsoft that your organization is at least experimenting with alternatives.
Integrating Windows and Linux.
The best way to start integrating Microsoft Windows and Linux solutions is to start with the servers. Many server functions can be replaced without disruption to the enterprise. It is possible to configure Linux Servers so that they appear to the network and PC Users like a Windows based server. Samba The Server Message Block (SMB) is the most common file sharing protocol as it ships with every single copy of Microsoft Windows. SMB is also found in PDAs running Windows CE. SMB can be traced back to the old days of DOS. Time when IBM used SMB to communicate with the original network cards.
IBM moved SMB to token ring and then to Ethernet. SMB was adopted by several vendors and moved on to other protocols. Up until Windows 2000, SMB was tied to Net BIOS. Win2000 introduced SMB packet transport over TCP/IP. SMB was encompassed into Common Internet File System (CIFS). The underpinnings of CIFS are hodgepodges of documented and undocumented protocols. While the underlying protocols are ugly, what is presented to the users is a slick interface known as Network Neighborhood. The upgraded version of SMB that now runs on top of TCP/IP gets rid of legacy name resolutions known as WINS.
Instead, CIFS now uses the open Dynamic DNS and Kerberos for authenticating. Microsoft now uses Active Directory, which is similar but different than LDAP. The native files sharing used in the Unix world is NFS. NFS was developed by Sun Microsystems. Sun had made NFS available for Microsoft systems for years, but it has always been a commercial product. The most popular
way to allow Unix and