Interconnecting Network Operating Systems

1. Interconnecting Network Operating Systems Chapter 18

2. Contents • Describe the issues involved with interconnecting Windows 9x, NT, 2000, XP, and 2003 with other network operating systems • Define the issues involved with interconnecting NetWare with other network operating systems • Explain the interconnection issues of Macintosh with other network operating systems • Describe the issues involved with interconnecting UNIX/Linux with other network operating systems

3. Introduction

4. Historical • In the early years of networking, Novell, Apple, and Microsoft had no desire to provide interoperability • One client or server would not work with another’s • The makers of UNIX and later Linux used TCP/IP at their core, so all versions would work with each other • Other developers like Novell and Microsoft began to use some of the TCP/IP protocols • Microsoft and Novell began to realize that potential purchasers wanted their existing machines to work with anything new – so interoperability began

5. Connecting to Windows

6. Connecting to Windows • The easiest way for a non-Windows operating system like Macintosh or UNIX/Linux to connect to a Windows computer is to make it look like another Windows computer • Run the same protocol • Use the same naming convention • Work with the Windows security functions

7. Connecting Macintosh to Windows 9x Shared Resources • Macintosh’s OS X operating system is basically a specialized UNIX system that uses the same basic tools and methods to connect to Windows as UNIX/Linux • We’ll cover this in the UNIX/Linux section later • Pre OS X Macintosh operating systems used AppleTalk – Windows 9x use NetBEUI or TCP/IP • Since newer Macintosh OSs support TCP/IP, third-party vendors sell excellent programs to enable connectivity

8. PC MACLAN Allows a Mac to connect to Windows shared folders and printers

9. Connecting UNIX/Linux Systems to Windows 9x Systems • Samba makes the UNIX/Linux box look like a Windows 9x box to a Windows server • Samba is also used to connect Windows machines to UNIX/Linux or Macintosh OS X servers • Configuration is stored in text files such as smb.conf • Configuring Samba is challenging, but third-party tools such as SWAT can help

10. A Glance at smb.conf [global] workgroup = mhteched server string = mikeslinux printcap name = /etc/printcap load printers = yes printing = cups log file = /var/log/samba/%m.log max log size = 0 security = user encrypt passwords = yes smb passwd file = /etc/samba/private/smbpasswd

11. SWAT running on Linux

12. UNIX/Linux Connections to Windows • Shared Windows folders look like drives in UNIX/Linux that must be mounted using a tool such as smbmount

13. More Uses for Samba • Macintosh computers running OS X also use Samba

14. Connecting to Windows Workstations (NT/2000/XP) • Use the same tools already discussed, but you’ll need a local account on the Windows workstation

15. Connecting to Windows Server Systems • Windows NT Server, Windows 2000 Server, and Windows Server 2003 all support Macintosh and UNIX/Linux systems natively • That is, the Windows server will act like the Macintosh or UNIX/Linux machine • However, Macintosh and UNIX/Linux clients cannot join Active Directory and are treated as separate entities

16. Connecting Macintosh to a Windows Server • Windows NT, 2000, and 2003 Server come with AppleTalk, File Services for Macintosh (FSM), and Print Services for Macintosh (PSM) • Install as services in the Windows Components section of Add/Remove Programs • This provides seamless connectivity for pre-OS X • When creating a share on the Windows server, specify it is to be shared with Macintosh clients • All the Macintosh systems must have valid user accounts on the Windows server

17. Connecting Macintosh to a Windows Server Installing File Services for Macintosh in Windows 2000 Creating a new share for Macintosh systems on a Windows server

18. Connecting UNIX/Linux Systems to a Windows Server Resources • Samba is the tool to connect a UNIX/Linux system to a Windows Server • Microsoft has provided Services for UNIX (SFU) for years as an add-on for a fee as another option SFU in Windows 2000 NFS client configuration in SFU

19. Connecting to NetWare

20. Connecting to NetWare • NetWare is strictly a server NOS • There is no NetWare client operating system • Novell has created excellent client software for Windows, Macintosh, and UNIX/Linux

21. Connecting Windows to NetWare • Client32 was the first client written for Windows 95 • Client32 is now a common term for any Windows NetWare client • Client32 provides complete control over the entire network if you have admin rights

22. Connecting Windows to NetWare • Microsoft wrote its own client for NetWare called • Microsoft Client for NetWare Networks in Windows 9x • Client Service for NetWare (CSNW) in NT, 2000, XP • Neither of these are as strong as the NetWare products • Neither product supports TCP/IP – only IPX/SPX • Gateway Services for NetWare (GSNW) enables a single Windows server system to act as a gateway to a NetWare network • But it’s slow, prone to lockups, and not available for Server 2003 – comes with NT and 2000

23. CSNW & GSNW

24. Connecting Macintosh to NetWare • Macintosh Client for NetWare provides full access to NetWare resources • ProSoft (www.prosoft.com) now makes the client for a fee • Windows and UNIX/Linux clients are free from Novell

25. NetWare Client Software • The NetWare client for Windows, Macintosh, and UNIX/Linux all support both IPX and IP networks • NetWare File Access is a series of programs that run on NetWare servers that provide access to files and folders without a client

26. Connecting to Macintosh

27. Connecting to Macintosh • OS X runs Samba by default, so Windows systems automatically see Macs • UNIX/Linux systems use Samba or TCP/IP applications like FTP or NFS

28. Connecting Windows to Macintosh Servers • AppleShare IP runs on a Macintosh server to provide file and print sharing for Windows and UNIX/Linux clients for a price • DAVE from Thursby Software enables Windows systems to access Macintosh services • DAVE also enables Macintosh clients to access Windows shared folders • Check out www.macwindows.com for more Mac/Windows interconnectivity tools

29. DAVE & Macintosh A DAVE-shared Macintosh named Imac as seen by Windows

30. Connecting UNIX/Linux to Macintosh Servers • Before Mac OS X, Macs used an NFS server program that worked moderately well • With UNIX-based OS X, NFS works well • CUPS or the older LPR/LPD are used to share printers

31. Connecting to UNIX/Linux

32. Connecting to UNIX/Linux • Samba or NFS is used by Windows systems to connect to UNIX/Linux servers • Microsoft Windows Services for UNIX (MWSU) is an add-on product for NT or 2000 systems that makes configuration easier • Windows 9x systems need a third-party NFS client program such as OMNI from Xlink Technology • OMNI also allows any NT/2000 Server to act as a gateway between a Windows network and UNIX/Linux servers • Clients do not need to run client software

33. OMNI NFS Client

34. Connecting Macintosh to UNIX/Linux Servers • Mac OS X has full NFS support for file sharing and LPD/LPR support for printers • Netatalk creates AppleTalk-compliant folder and printer shares on UNIX/Linux systems

35. AppleTalk Configurator

36. Terminal Emulation - Citrix • Citrix made Winframe/MetaFrame products as early terminal emulation products

37. Terminal Emulation • Windows 2000 Terminal Services is a built-in emulator that works only with Windows systems

38. VNC • Virtual Network Computing (VNC) allows you to take over the other computer • VNC is free!