Posted by arlene

SFU also includes a Telnet server for Windows servers, and a character-cell—style client application that greatly improves on the simple GUI Telnet client that comes with the standard Windows client operating systems. That makes it easy to use Telnet to log in to Windows server computers to perform system administration tasks or run character-cell—based user applications.

However, if you’re using Windows Server computers, this new Telnet client is already on your computer. It’s now the standard client for Windows 2000 computers. Simply use the telnet command at the Command Prompt. Alternatively, click Start, Run, enter telnet, and click OK. If you use the telnet command at the Command Prompt, you can specify a target computer on which you want to establish a session.

Note:

After you use the open command to start a Telnet session with a remote computer, you can use the Ctrl+] key sequence to escape to console mode. This can be useful if you need to use the display command to show your current configuration, such as the terminal emulation type. Suppose that you open a session and find that certain keys don’t seem to work as you expect. You can escape to console mode, check your current settings (using the display command), and then use the set command to change to a different terminal type. Then simply use the close command to close the session you started, and use the open command to re-establish a session with the remote system. The terminal types that you can emulate using the set command are ANSI, VT100, VT52, and VTNT.

Some users who are accustomed to using the GUI Telnet client might not appreciate you giving them a simple character cell type of Telnet client. However, the new version is actually faster than the older GUI client and offers more features than its predecessor.

Although Windows server operating systems come with an excellent Telnet server, SFU also provides a Telnet server that will run on Windows servers. The new server also supports logging to the Windows event log or to a separate log file, and you can choose which events you want to store in the log file. Instead of using the Internet Services Manager to manage and configure the Telnet server, you can load the SFU snap-in for the Microsoft Management Console (MMC) or you can use a command-line utility, tnadmin. Both methods enable you to configure the standard options. This includes selecting which authentication method to use, enabling logging, setting the maximum number of connections (remember that the Windows server versions allow for only 2 simultaneous connections, whereas this SFU version allows for up to 63), and other parameters.

Caution

You should only use Secure Shell (SSH), now up to version 2, for remote administration. Telnet is sent in cleartext and your credentials can easily be sniffed off your network segment and used to enter the devices you are trying to protect.

ActiveState ActivePerl 5.8

Web site administrators will be glad to see this SFU component because it’s used on a lot of Web servers. Additionally, Perl can be used for other functions, such as automating system management procedures. The version included with SFU is Perl 5.8 (including Perl Script), ported to the Windows platform. Your Windows clients also will be pleased because this port of Perl provides support for the Windows t cript Host (WSH). By including Perl with the SFU package, it becomes easier for Unix or Web administrators who are already familiar with the language to manage systems or Web sites that run on Windows servers. WSH enables those coming from the Windows camp to continue to use JScript, VBScript, and other procedural languages with which they are used to working.

Samba

Samba is a set of applications that’s freely available on the Internet. Samba enables you to set up Unix servers that can act as file servers for Microsoft clients that use the older SMB (server message block) protocol.

Using Samba, you can make resources running on high-performance Unix/Linux servers available to Microsoft clients on the same network. The reverse is also true. You can offer file shares to Windows clients when those files (or printer) shares exist on Unix/Linux systems.

Possibly related posts: (automatically generated)
New Telnet Server and Client

• Managing on Windows 2000 Server Telnet Server
• Managing Telnet on Windows Server 2003
• Why File Server Protocols are Important
• An ASP-Based Windows Server Script continue...
• Useful Software Technologies on the Internet
• Web Servers
• Windows Server Support for Unix Protocols and Utilities
• The Dynamic Host Configuration Protocol and BOOTP
• Windows Internet Name Service part 1
• The Dynamic Host Configuration Protocol and BOOTP continue...