Posted by arlene

Windows operating systems now support many protocols and utilities that were originally created for the Unix Environment. The first that comes to mind, and perhaps the most important, is the TCP/IP protocol suite. This includes not just the TCP/IP protocols, but other associated protocols and utilities.

Many of the technologies that began in the Unix world have evolved into standards that have been implemented on other platforms over the years. For an example, see the 1pr / lpd printing system and TCP/IP stream printing. Both of these started out on Unix platforms and are now supported not only by Windows, OpenVMS, and other operating systems, but also by printers from Hewlett-Packard (and most other major printer vendors) and print server appliances made by a number of other vendors. When adding Windows computers to a network that consists mainly of Unix or Linux servers, printing can be the least of a network administrator’s worries. It’s a simple matter to configure Windows Server operating systems to direct printer output to a Unix system that manages print queues. It’s also a simple task to configure clients to use a printer that understands the 1p r / 1pd protocols or TCP/IP stream method. And, of course, you can also configure Windows 2000 Server and Windows Server 2003 to operate as a print server using these protocols.

Other technologies that were either first developed in or adopted by the Unix world, which Windows and Linux also support, include the following, among others:

• The TCP/IP networking protocol suite, including the standard utilities and troubleshooting tools
• BOOTP and the Dynamic Host Configuration Protocol (DHCP)
• Support for the Network Information System (NIS), developed by Sun Microsystems, and adopted by many other Unix/Linux vendors.
• The Domain Name System (DNS)

TCP/IP

When Windows NT 3.5x was first brought to the market, the default network protocol was IPX/SPX. Basic TCP/IP protocols and utilities were there if you wanted to use them, but at that time Microsoft perceived its main competitor in the client/server market to be Novell’s NetWare. When NT 4.0 was released, the default networking protocol had been changed to TCP/IP. Because the Internet had begun to take on a higher degree of importance during the time frame in which NT 4.0 was being marketed, this was a natural path for the operating system to take. TCP/IP is the network protocol suite that’s used throughout the Internet to connect computers from a wide range of manufacturers running many different operating systems. For example, you can find TCP/IP on every Unix or Linux variant currently on the market as well on most every operating system from IBM, from OS/2 to mainframes, along with any other major operating system vendor. Of course, by the time Windows 2000 was released, TCP/IP had become the de facto standard networking protocol for all Microsoft products. It’s included with Windows Server, the Windows client operating systems, Me and XP, as well as the client version for Windows NT and Windows 2000.

Note

Novell’s Open Enterprise Server combines NetWare 6.5 and SUSE Linux Enterprise Server. This provides backward compatibility for existing customers who cannot at this time upgrade to a Linux-based version of NetWare, as well as offer new functionality to NetWare, because Linux is a fast-rising star in the operating system community.

In a network that consists of Unix servers, TCP/IP can be used by Windows clients to access resources on these servers. The most common method provided by the TCP/IP suite of applications for executing commands on another computer is Telnet. For exchanging files, use the FTP utility. Other applications, such as the SSH (Secure Shell) utilities, can be incorporated into the network to allow for additional security.

More about: Windows Server Support for Unix Protocols and Utilities

• Why Use Unix or Linux?
• Key Differences Between Unix/Linux and NetWare
• E-NEWSLETTERS - DEFINING AND REFINING Part 5
• Managing on Windows 2000 Server Telnet Server
• Using the Client Network Utility to Resolve Connection Problems
• The Dynamic Host Configuration Protocol and BOOTP
• Password Synchronization
• New Telnet Server and Client
• Key Differences Between Unix/Linux and NetWare (Applications)
• The Dynamic Host Configuration Protocol and BOOTP continue...

• Managing Telnet on Windows Server 2003 - Internet and Web 2.0 Tech
• Account Management Service - Internet and Web 2.0 Tech
• The Active Directory Service and Windows Server 2003 - Internet ...
• Windows Com | Homeowners Blog
• Microsoft Windows Services for Unix 3.5 - Internet and Web 2.0 Tech
• Funders Receive Hundreds - Funds Investing
• New Telnet Server and Client - Internet and Web 2.0 Tech
• Size Chart - Internet and Web 2.0 Tech
• Cd Label Maker - Internet and Web 2.0 Tech
• Window Blinds | Homeowners Blog