|
Command MSG net send Command line format: user- Username. Important! msg Parameter AllowRemoteRPC type REG_DWORD and equal 1 AllowRemoteRPC 0 msg.exe 445 Examples of using MSG: Server 192.168.0.1 TSServer Windows7 To execute the command msg PSExec from the package PSTools or a regular tool runas.exe msg |
MSG command - send a message to the user.Command MSG existed in Windows 2000 / XP and was intended for the exchange of messages between users logged into the system locally and users of terminal sessions (connected to a remote desktop). In Windows Vista and later Windows operating systems, the MSG command has become the main standard messaging tool because the command net send is no longer supported in these OS. Command line format: MSG (user | session name | session ID | @ filename | *) Description of command line parameters: user- Username. |
How to send a message to all computers on the local network?
Important!
The current implementation of msg.exe is perfect for exchanging messages between sessions of local and terminal users within the same system, however, in cases of exchange between different computers on the local network, you will need to change some of the default security settings in Windows Vista, 7 and more. late.
With the standard settings, sending a message to users of remote computers is not performed and is accompanied by the message:
Error 1722 while getting session names
This means that it is not possible to obtain information about the logged in users on the computer where the message is to be sent. This could be because the firewall is blocking incoming connections, the user has insufficient rights to the remote system, or RPC is not allowed in the Terminal Server settings. At least for messaging using the command msg between computers, you must have a user account valid for the remote system and configure the following settings:
On each computer to which messages will be sent, add to the registry key HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server parameter AllowRemoteRPC type REG_DWORD and equal 1 To change the settings, you can use the .reg file with the following content:
Windows Registry Editor Version 5.00
"AllowRemoteRPC" = dword: 00000001
In Windows Vista, Windows 7, 8, 10 registry key AllowRemoteRPC exists but has a value equal to 0 what needs to be fixed. A reboot is required to apply the changes.
Since the messaging utility msg.exe uses the SMB (Server Message Block) protocol, a TCP port must be open on each computer to which messages will be sent 445
Examples of using MSG:
msg * / server: Server "Test message"- send a test message to all computer users Server
msg * /server:192.168.0.1 "Test message"- send a test message to all computer users with an IP address 192.168.0.1
msg RDP-Tcp # 0 / server: TSServer "Test message"- send a test message to the user of the terminal session with the name RDP-Tcp # 0 on the computer TSServer
msg console / server: Windows7 "Test message"- send a test message to the current local computer user Windows7
msg console "Test message"- sending a test message from the user of the RDP session to the local user. If this command is executed by a non-terminal user, then the message will be sent by the local user to himself.
To execute the command msg on behalf of another user, you can use the utility PSExec from the package PSTools or a regular tool runas.exe
psexec -u otheruser -p otherpass msg * / server: win10 TEST message
runas / user: otheruser "msg * / server: win10 Test message"
Messages sent by the team msg to a local user of a computer running Windows XP, which is absent (not yet logged into Windows) are displayed in a window with an invitation to log on to the system and may be accessed by unauthorized persons.
The entire list of CMD Windows commands
MSG command - send a message to the user.Command MSG existed in Windows 2000 / XP and was intended for the exchange of messages between users logged into the system locally and users of terminal sessions (connected to a remote desktop). In Windows Vista and later Windows operating systems, the MSG command has become the main standard messaging tool because the command net send is no longer supported in these OS. Command line format: MSG (user | session name | session ID | @ filename | *) Description of command line parameters: user- Username. Important! The current implementation of msg.exe is perfect for exchanging messages between sessions of local and terminal users within the same system, however, in cases of exchange between different computers on the local network, you will need to change some of the default security settings in Windows Vista, 7 and more. late. With the standard settings, sending a message to users of remote computers is not performed and is accompanied by the message: Error 1722 while getting session names This means that it is not possible to obtain information about the logged in users on the computer where the message is to be sent. This could be because the firewall is blocking incoming connections, the user has insufficient rights to the remote system, or RPC is not allowed in the Terminal Server settings. |
Sending a message via command line to another computer
At least for messaging using the command msg between computers, you must have a user account valid for the remote system and configure the following settings:
On each computer to which messages will be sent, add to the registry key HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server parameter AllowRemoteRPC type REG_DWORD and equal 1 To change the settings, you can use the .reg file with the following content:
Windows Registry Editor Version 5.00
"AllowRemoteRPC" = dword: 00000001
In Windows Vista, Windows 7, 8, 10 registry key AllowRemoteRPC exists but has a value equal to 0 what needs to be fixed. A reboot is required to apply the changes.
Since the messaging utility msg.exe uses the SMB (Server Message Block) protocol, a TCP port must be open on each computer to which messages will be sent 445
Examples of using MSG:
msg * / server: Server "Test message"- send a test message to all computer users Server
msg * /server:192.168.0.1 "Test message"- send a test message to all computer users with an IP address 192.168.0.1
msg RDP-Tcp # 0 / server: TSServer "Test message"- send a test message to the user of the terminal session with the name RDP-Tcp # 0 on the computer TSServer
msg console / server: Windows7 "Test message"- send a test message to the current local computer user Windows7
msg console "Test message"- sending a test message from the user of the RDP session to the local user. If this command is executed by a non-terminal user, then the message will be sent by the local user to himself.
To execute the command msg on behalf of another user, you can use the utility PSExec from the package PSTools or a regular tool runas.exe
psexec -u otheruser -p otherpass msg * / server: win10 TEST message
runas / user: otheruser "msg * / server: win10 Test message"
Messages sent by the team msg to a local user of a computer running Windows XP, which is absent (not yet logged into Windows) are displayed in a window with an invitation to log on to the system and may be accessed by unauthorized persons.
The entire list of CMD Windows commands
Net send command reference
1. General information about the net send command
2. Using the net send command
3. Syntax of the net send command
4. Notes on using the net send command
5. Examples of using the net send command
6. Enabling and disabling the messaging service and net send
7. How to send net send messages in Windows 7
Understanding the net send command
Net send is a console application that is included with some versions of Windows and is designed to send messages over the local network to another user, computer or alias. The command is only available in Windows NT, 2000, XP, 2003 and is not available in Windows 7, Vista, ME, 98, 95 and older. In Windows XP starting with Service Pack 2, the net send command is disabled by default.
Using the net send command
The Windows Messenger service must be running for net send to work. In fact, the net send command is only a command line interface to the messaging service, which is directly involved in sending and receiving messages. To receive messages on the computer to which the message is sent, the messaging service or another program that uses the same messaging protocol must also be running. The message can only be sent to an active object on the network. If a message is sent to a user, he must log in with his own name.
To send messages with the net send command, start the command interpreter (command line). To start the command interpreter, select Run from the Start menu, type cmd and click OK. Use the net command with the send parameter and other parameters according to the command syntax. Messenger displays received messages in a standard Windows message dialog box.
Net send command syntax
The net send command has the following syntax:
net send (username | * | / domain | / users) message
username- username, computer name or alias to whom you want to send a message;
* - sending messages to all members of a domain or workgroup;
/ domain- sending a message to all names in the computer's domain or in the domainname domain;
/ users- sending a message to all users connected to the server;
message- Message text.
Notes on using the net send command
If command parameter arguments contain spaces, they must be enclosed in quotation marks.
It can be difficult to use long names for message recipients. The names used by the messaging service are up to 15 characters long.
The maximum length of broadcast messages is 128 characters. The maximum length of personal messages is 1600 characters.
Examples of using the net send command
To send the message "You can send a message over the local network using the net send command" to the ivanov user, enter:
net send ivanov You can send a message over the local network using the net send command
To send a message to all users connected to the computer from which the message is sent, enter:
net send / users Everybody quit 1C immediately!
To send a message to all users in the ukmz domain, enter:
net send / domain: ukmz The electricity in the building will be cut off in 5 minutes
To send a message to all users in the domain of the computer from which the message is sent, enter:
net send * Gentlemen, the meeting with the CEO will take place at 13:00
Enabling and disabling the messaging service and net send
Enabling and disabling the messaging service is possible through both the MMC (the Services snap-in) and using the command line.
To perform these operations, you must have administrator rights.
To enable the messaging service using the MMC, follow these steps: Go to the Control Panel. Open the Administrative Tools folder, Services. Find Messenger in the list. Open the properties window for the service. Select the ‘Auto’ value from the ‘Startup type’ list if you want the service to start automatically when Windows starts up. Then click the Start button. Click OK.
To disable the messaging service, follow these steps: Go to the Control Panel. Open the Administrative Tools folder, Services. Find Messenger in the list. Open the properties window for the service. Select 'Manual' from the 'Startup Type' list. Then press the Stop button. Click OK.
To enable the messaging service from the command line, enter the following commands in a command interpreter:
sc config messenger start = auto
net start messenger
To disable the messenger service from the command line, enter the following commands in a command interpreter:
net stop messenger
sc config messenger start = disabled
How to send net send messages in Windows 7
To send net send messages in those versions of Windows where this command is absent (Windows 7, Vista, ME, 95, 98), you can use third-party software.
Sending messages with msg.exe
We suggest you use two programs: WinSent Messenger and Sent utility. WinSent Messenger is a LAN messenger compatible with net send. The Sent utility is designed to send messages from the command line. More information is available on the pages of these software products:
WinSent Messenger - messenger for local network
Sent is a utility for sending net send messages from the command line in Windows 7 / Vista.
Is your company experiencing communication difficulties within the team? Tired of inviting every colleague to a meeting? Tired of walking all over the office to solve the simplest issue? If you answered “yes” to at least one of these questions, then it’s time to implement a corporate local messenger.
Softros LAN Messenger is a simple and convenient office messenger - a program for exchanging messages on a local network of any size. The messenger for the company does not require and does not use an Internet connection and thus ensures that the transmitted information does not go beyond the local network. The application is easy to install and use, has a pleasant, intuitive interface and works correctly for users with limited rights. For your convenience, there is also a function for exchanging files between users of the network messenger. Fine-tuning allows the administrator to prohibit the use of certain functions of the application and change its settings, which can be useful in a large company with a disparate infrastructure. Serverless messaging and file exchange saves hardware costs. 14 years of constant improvement guarantee the quality and stability of our messenger for your local network.
short info
Latest version: 9.2
Supported OS: Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows 2008, Windows 7, Windows 8.1, Windows 10, Windows 2012, Windows 2016
Supported network types: LAN, WAN
Key features of the Corporate Messenger:
- Chatting messaging
Create virtual chats within your network with any number of users. - Safe network communication
Messages do not go outside the local network. - Group messages on the local network
Use bulk messaging to keep employees informed of upcoming events. - Quick messages
Configure up to 10 preset template messages with instant hotkey sending for quick replies with typical phrases or sentences. - Huge set of emoji emoticons
Spice up your messages with the built-in emoji pack (approx 830 emoticons) - Intranet file transfer including bulk file distribution
Sharing documents with colleagues has become much easier.Net send on Windows 7
- User grouping
Assign your colleagues by department or job title for ease of communication. - Remote Desktop Sharing
Request remote assistance from your colleague or network administrator directly from Messenger, giving him access to your desktop remotely. Ask the administrator to help you with setting up any programs or Windows on your computer, ask a colleague to help you solve work issues. - Remote desktop administration
Administrators who are authorized on a domain as Domain Administrators, or on a remote computer as Local Administrators, can connect to user desktops directly, bypassing user connection permissions. - User rights management
The administrator can prohibit the use of any function if necessary. - Message history
You will never lose any messages as they are all saved in history files. - Serverless messenger architecture
LAN Chat does not require dedicated server installation. - No need for an Internet connection
Messenger for local area network works only within your network of your company and saves your subordinates from wasting time in ICQ, saving your traffic and minimizing the possibility of attacks. - Terminal Server Support
LAN Messenger successfully runs on a terminal server from Microsoft or Citrix, and also supports the simultaneous use of multiple user sessions. (After installing Softros TS Engine.) - Easy to install
You don't need any administrative skills to start using our program. Just install the internal messenger on every computer on your local network and it's ready to go. - Ease of distribution
Having configured the network settings, as well as the settings of user groups on one computer, you can export them to a file, so that you can then use them on all computers within the company's network. This makes it easy to configure the program on complex networks.
Top 10: Chat for LAN
Client-server messenger for the local network. Integrates with Active Directory, multi-level contact list, message board, bulk notification system, conferences, SSL traffic encryption, offline message and file transfer, flexible user rights management system, file and folder transfer. Built-in Kanban boards for projects
Client-server program for communication in a corporate network, which runs on the Windows OS platform. CommFort includes modules for chat, image exchange, file transfer, VoIP and video communication. Supports video conferencing for up to 32 users
Softros LAN Messenger
Simple and reliable messenger for the local network. Doesn't require internet connection. In addition to sending instant messages and transferring files, it allows you to create virtual rooms, make bulk mailings, save message history, group contacts by department or job title.
Corporate mobile messenger in source codes. Includes Enterprise mobile messenger in source codes
Multimedia corporate messenger. Supports online status control, chat, voice and video calls, conference calls, video mail, screen-sharing.
Msg Team
Works on PC, Mac and mobile platforms - iPhone, iPad, Nokia, Android and BlackBerry. Uses Open Jabber Protocol (XMPP)
Enterprise client-server platform for real-time interaction and communication. Integration with Active Directory, access to the archive of all transmitted messages and files, delivery of offline data and assignment of documents to employees with strong encryption.
Simple and fast multi-user chat with activity control on the local network. Designed for medium and small local area networks (up to 300 computers). Doesn't require a dedicated server and can be quickly deployed even on a network without a professional administrator.
Simple and powerful cross-platform client-server chat for local network and the Internet, open source.
Free open-source cross-platform messenger for local network. Doesn't require a server. Logging messages. File transfer.
Free cross-platform chat for corporate networks. File transfer. Offline messages.
Free software for instant messaging on Microsoft Windows networks. High speed of delivery of messages to a large number of recipients (1000+)
I ran into the problem of informing users, the most common reason is updating 1C, in which it is necessary that all my users (and there are more than 160 of them) exit 1C and do not enter for some time. It would seem, what is difficult, you can send an email message, as I did before when I had office 365, but Yandex mail has its own limitations: no more than 50 users on the mailing list. If you send to a larger number of users, then the letter will simply not reach some. Sending 50 users separately is not convenient. The second problem with Yandex mail - the need to enter captcha in some cases, the system perceives the mass mailing as spam, and the letters are necessary, if you do not warn the user he does not save on time and there may be problems ...
In general, it has become terribly inconvenient to send messages to all users. I started thinking about solutions.
The first thing that came to mind: but there were several inconveniences:
- Messages are received in about 30 minutes for 160 jobs, which is a very long time.
- The message goes only to the taskbar, if the user works through the remote desktop - he will not see the message immediately.
- It is necessary to maintain the operability of Kaspersky agents on the user's work machines, otherwise the message will not reach at all.
The second option is to install some messenger, but there are also some inconveniences here.
- There are a lot of messengers, they are not universal, you cannot send messages to each other between messengers.
- Good messengers are paid.
- Messages do not pop up on top of all windows, and if you need to communicate something urgent and important, then this is a useful property of the message.
- Installation and configuration of these messengers is required, as well as training of users in new software.
As a result, I am on the Windows command line, there are net send and msg commands to send messages to all computers on the local network. Everything works very simply, you open the command line, write a command, a message comes to the computer whose name you indicated in the command text. Moreover, the message pops up on top of all windows, no registration is required, and everything is completely free.
The command for sending messages to one computer in the local network looks like this:
msg * / server: computername "Test message, click OK"
I made a list of computers, then a little tedious work on creating commands of the same type in one txt file, but it's done quickly through copy-paste. The main thing is to make a list of computers. In a domain, this is done quite simply through the Users and Computers snap-in, right-click under the list of computers, then Export the list directly to a TXT file. Since I have about 160 computers in the domain, I approached the question a little more creatively, did not do "copy-paste", but made an autochange of the first letter in the computer name to msg * / server: + the first letter in the name of computers, for my luck it was the same for everyone. Likewise for the second part, but only with the last letter of the computer name (the last letter in the computer name + "Test message, press OK"), as a result received a TXT file with a list of commands. I changed the file extension from txt to bat and launched it for execution. As a result, all computers in the domain received a "test message, click OK."
Unfortunately, outside the domain, such a command does not work, and since I completed the task, it was simply not rational to experiment further. I failed to send messages to computers in a workgroup, but I have only a few such computers. They can be sent a message by mail, or in the same kaspersky, or through some messenger. Let this be the theme for one of the following posts.
As a result, what I got: 1 file in which you can quickly change the text of the message and with which I can send any message for free to everyone in the domain. It seems super, but there are still a couple of disadvantages:
- It is necessary to keep the file up to date, add new ones, delete non-existent computers.
- No prompt feedback.
- The file turned out to be ugly, I think it is possible to load the computer name values from the file into this command, but there was no time to figure it out to the end.
However, the pros overlap all the cons:
- Quickly to implement, practically does not require preparation for the next dispatch.
- Works reliably, the user will definitely see this message.
- Is free.
- Very, very simple, you just need to know one command and computer names.
I will be glad to any comments, suggestions, comments)
It existed back in Windows 2000 / XP and was intended for the exchange of messages between users logged into the system locally and users of terminal sessions (connected to a remote desktop). In Windows Vista and later Windows operating systems, the MSG command has become the main standard messaging tool because the command net send is no longer supported in these OS.
Command line format:
MSG (<пользователь> | <имя сеанса> | | @<имя файла> | *} [<сообщение>]
Description of command line parameters:
<пользователь>
Username. <имя сеанса>
Session name. Session ID. @<имя файла>
A file containing a list of usernames, session names, or session IDs to which the message is sent. *
Send a message to all sessions on the specified server. / SERVER:<сервер>
Server (default - current). / TIME:<секунд>
The interval to wait for confirmation from the recipient. / V Displays information about the actions performed. / W Waiting for a response from the user, useful in conjunction with / V. <сообщение>
The message to be sent. If not specified, prompts or accepts input from STDIN.
Important!
The current implementation of msg.exe is perfect for exchanging messages between sessions of local and terminal users within the same system, however, in cases of exchange between different computers on the local network, you will need to change some of the default security settings in Windows Vista, 7 and 8. ...
Usually, with standard settings, sending a message to a remote computer is not performed and is accompanied by a message
Error 1722 while getting session names
This means that it is not possible to obtain information about the logged in users on the computer where the message is to be sent. This could be because the firewall is blocking incoming connections, the user has insufficient rights to the remote system, or RPC is not allowed in the Terminal Server settings. At least for messaging using the command msg between computers, you must have a user account valid for the remote system and configure the following settings:
|
Windows Registry Editor Version 5.00 "AllowRemoteRPC" = dword: 00000001 In Windows Vista, Windows 7, 8, 10Technical Preview registry key AllowRemoteRPC exists but has a value equal to 0 what needs to be fixed. A reboot is required to apply the changes. Examples of using MSG: msg * / server: Server "Test message"- send a test message to all computer users Server msg * /server:192.168.0.1 "Test message"- send a test message to all computer users with an IP address 192.168.0.1 msg RDP-Tcp # 0 / server: TSServer "Test message"- send a test message to the user of the terminal session with the name RDP-Tcp # 0 on the computer TSServer msg console / server: Windows7 "Test message"- send a test message to the current local computer user Windows7 msg console "Test message"- sending a test message from the user of the RDP session to the local user. If this command is executed by a non-terminal user, then the message will be sent by the local user to himself. To execute the command msg on behalf of another user, you can use the utility PSExec from the package PSTools or a regular tool runas.exe psexec -u otheruser -p otherpass msg * / server: win10 TEST message runas / user: otheruser "msg * / server: win10 Test message" Messages sent by the team msg a local user of a computer with the operating system Windows XP, which is absent (has not yet entered Windows) are displayed in a window with an invitation to register in the system and can be accessed by unauthorized persons. |
Command MSG existed in Windows 2000 / XP and was intended for the exchange of messages between users logged into the system locally and users of terminal sessions (connected to a remote desktop). In Windows Vista and later Windows operating systems, the MSG command has become the main standard messaging tool because the command net send is no longer supported in these OS.
Command line format:
MSG (user | session name | session id | @ filename | *) [message]
Description of command line parameters:
user- Username.
session name- Session name.
Session ID- Session ID.
@File name- A file containing a list of usernames, sessions, or session IDs to which the message is sent.
*
- Send a message to all sessions on the specified server.
/ SERVER: server- Server (default - current).
/ TIME: seconds- The interval of waiting for confirmation from the recipient.
/ V- Displays information about the actions performed.
/ W- Waiting for a response from the user, useful in conjunction with / V.
message- The message to be sent. If not specified, prompts or accepts input from STDIN.
Important!
The current implementation of msg.exe is perfect for exchanging messages between sessions of local and terminal users within the same system, however, in cases of exchange between different computers on the local network, you will need to change some of the default security settings in Windows Vista, 7 and more. late.
With the standard settings, sending a message to users of remote computers is not performed and is accompanied by the message:
Error 1722 while getting session names
This means that it is not possible to obtain information about the logged in users on the computer where the message is to be sent. This could be because the firewall is blocking incoming connections, the user has insufficient rights to the remote system, or RPC is not allowed in the Terminal Server settings. At least for messaging using the command msg between computers, you must have a user account valid for the remote system and configure the following settings:
on each computer to which messages will be sent, add to the registry key HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server parameter AllowRemoteRPC type REG_DWORD and equal 1 To change the settings, you can use the .reg file with the following content:
Windows Registry Editor Version 5.00
"AllowRemoteRPC" = dword: 00000001
In Windows Vista, Windows 7, 8, 10 registry key AllowRemoteRPC exists but has a value equal to 0 what needs to be fixed. A reboot is required to apply the changes.
since the messaging utility msg.exe uses the SMB (Server Message Block) protocol, a TCP port must be open on each computer to which messages will be sent 445
Examples of using MSG:
msg * / server: Server "Test message"- send a test message to all computer users Server
msg * /server:192.168.0.1 "Test message"- send a test message to all computer users with an IP address 192.168.0.1
msg RDP-Tcp # 0 / server: TSServer "Test message"- send a test message to the user of the terminal session with the name RDP-Tcp # 0 on the computer TSServer
msg console / server: Windows7 "Test message"- send a test message to the current local computer user Windows7
msg console "Test message"- sending a test message from the user of the RDP session to the local user. If this command is executed by a non-terminal user, then the message will be sent by the local user to himself.
To execute the command msg on behalf of another user, you can use the utility PSExec from the package PSTools or a regular tool runas.exe
psexec -u otheruser -p otherpass msg * / server: win10 TEST message
runas / user: otheruser "msg * / server: win10 Test message"
Messages sent by the team msg a local user of a computer with the operating system Windows XP, which is absent (has not yet entered Windows) are displayed in a window with an invitation to register in the system and can be accessed by unauthorized persons.
Note
If the firewall is not turned off, then the program Nassi should be included in its exceptions.
Net send text message command
Text messages over the local network can be sent not only in special programs (Radmin, Nassi), but also from the command line Windows XP. Command Net send serves to send text messages to another computer on the network. However, in order to command worked, you must first enable the message delivery service. To do this, go to Control Panel... Open the folder Administration, Services... Find the messaging service in the list (fig. 20.9).
Rice. 20.9.
Open its properties. Please select meaning Auto from the list Startup type, if you want the service to start automatically at boot Windows... Then click on the button Start and OK(fig.20.10 and fig.20.11).
Rice. 20.10.
Rice. 20.11.
Let's take a look at examples of using the command net send when sending messages to a workgroup (domain) 110. To send a message to all users in a workgroup 110, enter: net send / domain: 110 CHECK COMMUNICATION. Another variation of this command: to send a message to all users in your domain, enter: net send * check connection(fig. 20.12 and 13)
Rice. 20.12.
Rice. 20.13.
To send a message to a specific user, for example 110-1, enter: net send 110-1 HELLO!(fig.20.14).
Rice. 20.14.
V Windows XP has another option for sending messages over the network. Run the commands Control Panel-Administrative Tools-Computer Management... Farther: Action-All Tasks-Send Console Message... Next, select the PC and send it the text (Fig. 20.15).
