Netsupport Manager 1.3

NetSupport Manager 1.3: A Deep Dive into the Legacy Remote Control Powerhouse In the fast-paced world of IT asset management and remote support, version numbers often blur together. However, certain releases stand as milestones. For IT professionals who came of age in the late 1990s and early 2000s, NetSupport Manager 1.3 represents a pivotal moment in the evolution of cross-platform remote control. While modern users may be running versions 14 or 15, revisiting NetSupport Manager 1.3 offers a fascinating lens through which to view the history of remote desktop technology. This article explores the architecture, features, system requirements, and lasting legacy of version 1.3, explaining why it remains a reference point for stability and efficiency in legacy environments. The Historical Context: Why Version 1.3 Mattered Released during the twilight of the Windows 95 era and the dawn of Windows NT 4.0, NetSupport Manager 1.3 arrived at a time when remote control software was either prohibitively expensive (like early pcAnywhere) or insecure (like basic VNC). NetSupport sought to bridge the gap. Version 1.3 was not the first iteration of the software, but it was the first to achieve three critical breakthroughs:

Low-bandwidth efficiency over 28.8k and 56k dial-up modems. True color compression that didn't crash the host machine. Hardware-level locking of input devices during remote sessions.

For system administrators managing school labs or corporate server rooms without KVM switches, NetSupport Manager 1.3 became an indispensable tool. Core Features of NetSupport Manager 1.3 Despite its age, version 1.3 packed a suite of features that competitors took years to replicate. Below is a breakdown of what made this release special. 1. The "Single-Click" Viewer Architecture Unlike modern solutions that require cloud authentication, NetSupport Manager 1.3 operated purely on IPX, NetBEUI, or TCP/IP. The Viewer (client) could discover Control (host) clients via broadcast. The interface was a Spartan gray dialog box—no ribbons, no dashboards—just a list of online machines and connection status. 2. Remote Deployment via Login Scripts For the era, this was revolutionary. Version 1.3 allowed the nsmctrl.exe (the client piece) to be pushed via Windows NT domain login scripts. An IT manager could deploy the remote control agent to 100 workstations overnight without touching a single floppy disk. 3. Screen Capture & Thumbnail Viewing The 1.3 release introduced the "Thumbnail View" feature, which allowed a single administrator to watch up to 16 remote screens simultaneously in a grid. This was originally designed for classroom management but quickly became a favorite for helpdesk triage. 4. The Chat & Messenger Module Before Slack or Teams, NetSupport Manager 1.3 included a built-in text chat and "Send Message" popup utility. This allowed helpdesk staff to warn users before taking control of their mouse and keyboard—a polite standard that 1.3 helped popularize. System Requirements: A Trip Back in Time To run NetSupport Manager 1.3 effectively, your hardware was modest by today's standards but specific: Control (Hosted Machine):

Operating System: Windows 95, Windows NT 3.51/4.0, or Windows for Workgroups 3.11 Processor: Intel 486 DX2/66 or higher RAM: 8 MB (16 MB recommended) Network: NE2000 compatible card or dial-up modem (28.8k minimum) netsupport manager 1.3

Viewer (Admin Machine):

Operating System: Windows 95 or NT 4.0 RAM: 8 MB Display: 640x480, 256 colors (though 800x600 was preferred)

The "No Internet" Rule : Version 1.3 lacked modern NAT traversal. It worked flawlessly on LANs and direct modem-to-modem connections, but connecting over the public internet required port forwarding (default TCP port 5405) or a VPN. Installation Walkthrough: Installing NetSupport Manager 1.3 on a Modern VM For preservationists or those managing legacy industrial machines, installing 1.3 today is a challenge. Here is how to do it on a Windows 95 virtual machine (VirtualBox or VMWare). Step 1: Source the media The original 1.3 distribution came on a single 1.44 MB floppy disk or CD-ROM. The executable was SETUP.EXE , roughly 1.2 MB. Step 2: Disable modern security Windows 95 has no UAC. Run the installer from the A:\ drive. The installer uses a 16-bit stub; it will complain if you have less than 4 MB of free conventional memory. Step 3: The license key Unlike later versions, 1.3 used a simple 6-digit site key. No online activation was required—just a printed sticker on the manual. Step 4: Protocol selection During installation, you must explicitly check which protocols to bind to. If you only check "TCP/IP", NetBIOS name resolution fails. Most admins in 1998 checked "IPX/SPX" for Novell networks and "TCP/IP" for internet. Step 5: The reboot After copying files to C:\PROGRAM FILES\NETSUPPORT MANAGER , a reboot was mandatory. Upon restart, the NSM Service would appear in the system tray as a gray monitor icon. Security in the NetSupport Manager 1.3 Era Let us be blunt: Security in 1.3 is nonexistent by 2025 standards. However, for its time, it was adequate. NetSupport Manager 1

Authentication : Stored passwords were hashed using a proprietary 40-bit algorithm (crackable now, secure then). Encryption : No TLS or SSL. Version 1.3 used "Scrambled Data Transfer" – a simple XOR cipher. Do not use this over the open internet today. Hardware Locking : A unique feature was the ability to physically disable the remote keyboard and mouse at the driver level , preventing the local user from interfering.

Troubleshooting Common NetSupport Manager 1.3 Errors If you are maintaining a legacy system (e.g., a CNC machine running Windows NT), you may encounter these classic errors: Error 105: "Protocol Not Bound" Cause: The client’s network stack does not match the viewer’s. Fix: Re-run the setup and ensure both sides have identical protocols (TCP/IP or IPX). Error 210: "Connection Refused - Security Mismatch" Cause: The password hash stored on the client is corrupted. Fix: Delete NSM.INI from the Windows directory and reconfigure the client password. Black Screen on Connection Cause: Video driver conflict with the mirror driver. Fix: In the viewer, disable "Mirror Driver Capture" and revert to "Slow Polling." NetSupport Manager 1.3 vs. Competitors (1998) To understand the value of 1.3, we must compare it to its direct rivals: | Feature | NetSupport Manager 1.3 | Symantec pcAnywhere 8.0 | VNC (AT&T) | | :--- | :--- | :--- | :--- | | Multi-screen viewer | Yes (16 thumbnails) | No | No | | Dial-up modem support | Excellent (28.8k optimized) | Good | Poor | | File transfer | Yes (drag & drop) | Yes (separate window) | No | | Windows NT service | Native | Native | Add-on required | | Cost (1998 USD) | $195 (single license) | $149 | Free | The Legacy: Where Is NetSupport Manager 1.3 Today? You will rarely find a production environment running version 1.3 natively. However, its DNA persists. Modern NetSupport Manager (versions 14 and 15) retains the same core philosophy: fast screen updates, granular permission controls, and a lightweight viewer. Collectors and retro-computing enthusiasts specifically seek out NetSupport Manager 1.3 for two reasons:

Windows 3.11 Compatibility : It is one of the few remote tools that works perfectly on Windows for Workgroups. OS/2 Warp Support : The 1.3 client had a specific build for IBM OS/2, which modern versions have dropped. While modern users may be running versions 14

Should You Use NetSupport Manager 1.3 in 2026? The short answer: No, unless you have no choice. While the software is stable and lightweight, it suffers from:

No modern encryption (vulnerable to sniffing). No UAC support (cannot remote-elevate on Windows 10/11). No IPv6 . Driver conflicts with modern graphics cards.