Seattle Lab Introduces Secure Remote Admin Tool -- Redmondmag.com

Seattle Lab Introduces Secure Remote Admin Tool

By Scott Bekker
12/05/2000

Seattle Lab will demonstrate its new RemoteNT-2000 4.0 with Secure Shell (SSH) and Telnet clients for remote administration of Windows NT and 2000 servers at the LISA 2000 14th Systems Administration Conference in New Orleans.

SSH is an Internet standard secure logon protocol. It protects logon sessions using a range of encryption techniques, so that passwords and user data are never passed over the network as clear text. Additionally, it provides protection against various security attacks. SSH connections must be made from an SSH compatible client to a compatible server. The RemoteNT-2000 client is a compatible client to the RemoteNT-2000 server. The RemoteNT-2000 Client uses SSH to make a connection from the local to remote machines so that the data stream is encrypted, ensuring that passwords and other system data are not intercepted.

Contact Seattle Lab, (425) 825-7000, www.seattlelab.com.

About the Author

Scott Bekker is editor in chief of Redmond Channel Partner magazine.

Featured

Microsoft and OpenAI Continue Global AI Expansions

Microsoft and OpenAI each continued their global expansion this month, with the announcements of new infrastructure investments and service rollouts in new regions, like Asia and the Middle East.
Cisco Warns of Brute Force Attacks Targeting VPNs and Firewalls

Cisco has revealed that a global increase in brute force attacks targeting Virtual Private Networks (VPNs) and other devices is currently taking place.
What's Inside Microsoft 365's Security Toolbox?

Microsoft provides plenty of native tools to secure Microsoft 365. IT pros just have to know where to look.
Microsoft Kills 30-Day Data Retention Policy for Copilot in Fabric

Microsoft this week announced several usability improvements coming to Copilot in Fabric in preparation of its general availability release later this year.
Using Microsoft Office to Build a Network Diagram 2

Now that we've set up our process, let's dig in with the actual execution.