How to Use the Net-Send Command: A Quick GuideThe net send command was a simple Windows command-line utility that allowed users and scripts to send short text messages to other users, computers, or messaging names on the same network. It was commonly used in small office LANs and by administrators to broadcast alerts and notifications. This guide explains what net send did, how it worked, how to use it on older Windows systems that support it, common options and examples, troubleshooting, and modern alternatives you should use today.
What net send is (and what it isn’t)
- Net send is a messaging command that used the Messenger service (not to be confused with any instant-messaging client) to deliver short text messages to other machines or user sessions on the same Windows network.
- Net send is not an email tool and had no guaranteed delivery or encryption. It was intended for quick LAN messages only.
- Net send is deprecated — Microsoft removed the Messenger service and the net send command from client versions of Windows starting with Windows Vista and later. It still exists on some older Windows Server editions if the Messenger service is installed.
How the underlying system worked
Net send relied on the Windows Messenger service (a system service, not the consumer “Messenger” app). When a net send command was issued, the Messenger service on the recipient machine received the message and displayed it in a dialog window to the logged-in user. The protocol used was the SMB/NetBIOS messaging functionality available on older Windows networking stacks.
Where net send still works
- Windows NT, 2000, XP, and some older Server editions: net send worked when the Messenger service was installed and running.
- Vista, 7, 8, 10, 11: net send and the Messenger service are removed/disabled by default; net send does not work unless you use third‑party or compatibility tools that emulate the service.
- Modern Windows networks: Use alternative tools (see “Alternatives” below).
Basic syntax
On older systems that include the tool, the basic command syntax was:
net send <name> <message> Where
- A computer name (e.g., LAPTOP01)
- A user name (e.g., john)
- A * / or /all broadcast to all users (syntax differed slightly by system and configuration)
- An IP address in some configurations
Examples:
net send LAPTOP01 "Server will reboot in 10 minutes." net send john "Please save your work." net send * "Meeting starts in 5 minutes." Common practical examples
-
Send a one-off alert to a single machine:
net send SERVER01 "Backup started." -
Send to a user by username:
net send alice "Please check the print queue." -
Broadcast to all machines on a domain (may require appropriate privileges and Messenger service on clients):
net send * "Network maintenance at 6 PM." -
Use in a script (batch example):
@echo off net send SERVER01 "Automated task completed successfully."
Permissions and requirements
- The Messenger service must be installed and running on recipient machines.
- The sender typically needed sufficient network privileges; in domain environments, domain-wide broadcasts could be restricted.
- Firewalls and network policies could block the underlying messaging ports (NetBIOS/SMB), preventing delivery.
Troubleshooting
- No delivery / “name not found”: check that the recipient’s Messenger service is running and that the computer/user name is correct.
- Message blocked by firewall: ensure NetBIOS/SMB messaging ports and related services are allowed on the network.
- Messages not shown: some modern machines removed or disabled the Messenger service; net send will fail.
- Consider using ping and other network tools to verify connectivity before assuming a messaging failure.
Security and privacy considerations
- Messages were sent in clear text across the local network — no built-in encryption.
- Malicious users could spam or spoof messages if they had access to the same network and permissions.
- Because of these limitations, Microsoft removed the service from newer client operating systems.
Modern alternatives
- Windows: Use msg.exe for sending messages to terminal sessions and remote users on modern Windows — it works with the Terminal Services/Remote Desktop Services environment and is available on newer Windows. Example:
msg /server:SERVER01 username "Your session will log off in 5 minutes." - PowerShell: Use remoting (Invoke-Command) to run scripts that display notifications, or use Toast Notifications for local user alerts.
- Chat/Collaboration tools: Microsoft Teams, Slack, or other chat apps for reliable, logged, and secure messaging.
- Monitoring/alerting systems: Use dedicated monitoring tools (Nagios, Zabbix, PRTG, etc.) for automated alerts and notifications.
- Email or SMS gateways for cross-network notifications with delivery tracking and security.
When you might still use net send (rare cases)
- Maintaining legacy systems that cannot be upgraded and where Messenger is still in use.
- Small isolated LANs where the simplicity of net send is sufficient and security concerns are minimal.
Quick reference table
| Task | Command / Note |
|---|---|
| Send to a computer | net send COMPUTERNAME “message” |
| Send to a user | net send USERNAME “message” |
| Broadcast | net send * “message” (may be restricted) |
| Modern replacement | msg, PowerShell remoting, Teams/Slack, monitoring tools |
Summary
Net send was a lightweight LAN messaging tool tied to the Messenger service, useful in older Windows environments for quick alerts. It’s deprecated and insecure by modern standards; use msg, PowerShell methods, or modern chat and monitoring systems for current networks.
Leave a Reply