Solution to Msg.exe “Error 5 getting session names”
Info
My Windows-Server 2008 R2 machine couldn’t msg my Windows 7 box due to Error 5 getting session names.
I found the solution here, in a comment made by Consoles. I reblog it so it can be found easier.
It turns out it has nothing to do with not being on the same domain or whatever. It is due to a setting related to Terminal Server.
That’s not to miraculous, since msg.exe is designed for messaging to terminal users.
So, changing a simple registry value and rebooting makes it all work again.
Solution
On the machine that you cannot message to:
Use regedit to navigate to: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
Then change the following value:
Name : AllowRemoteRPC
Type : REG_DWORD
Value : 1
Reboot. Now it should work. đ
Trackbacks & Pingbacks
- Msg.exe - TechExams.net IT Certification Forums
- Triggern einer Infobox auf einer Win7 workstation - IP-Symcon Community Forum
- Displaying Messages
- Anonymous
- Displaying a message on Networked Computer
Comments are closed.
I did this on all my Windows 7 HP machines and it got rid of the error 5 but now it says [username] does not exist or is disconnected. Any solution yet. I have been google-ing for about 3 hours on this and haven’t found anything other than 3rd party installs which is impractical in my situation.
What is the exact command you give to send a message? Does the user you send the message to indeed exists on the target machine? And is it logged on there?
hey [wick422] try this one
msg /server:servername * yourmessage
Example:
msg /server:AMMAR-LAPTOP * HelloThere!
Try msg * /server:AMMAR-LAPTOP “HelloThere!”
Hi All after much trying and re trying i got it right to send windows 7 to windows 7
using the following command
msg /server:pcname username message
server stays as is. pcname is the name of the pc you are sending to. user name is the name the user is logged in under on that PC. message is obviously the msg u want to send.
you will also need to change a setting on the receiving computer by using regedit.
the following registry key must be activated (as described by Consoles above):
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
Name : AllowRemoteRPC
Type : REG_DWORD
Value : 1 (the dafault is ‘0’)
I do not appear to have HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server on my computer? Is there any way for me to get it?
Isn’t allowing remote RPC like, a *HUGE* security risk?
I’d like to enable this so me and my roommate downstairs can have a ridiculously simple way to communicate, but if it means allowing his computer to make RPC calls, I’m afraid if he has a virus my computer will catch it, or if for some reason RPC requests are able to pass through my router, anyone over the internet will have an easy attack vector to my machine.
I think there’s a reason it’s disabled in Vista/7 by default. I’m not sure if the winpopup is worth compromising your security.
superray: search in regedit (F3) for ‘allowremoterpc’ it will find it
anon: yes, but only in intranet, and only if your firewall does not stop it. the rooter firewall will prevent all attempts by default. (it could be a problem only in mass lan-s like barding school. If scared, use skype or msn (meeboo.com)
You can send messages among Windows 7 machines and Windows XP machines on a LAN using freeware. It took a lot of searching, but I found an app that works from a command prompt and in batch files to send messages.
For sending messages, use Sent from WinSend.
For receiving messages, each machine needs to run WinSent Innocenti.
Both are available here:
http://www.winsentmessenger.com/download/
I had hoped to use msg.exe on our LAN, but after trying all the recommended Registry tweaks, firewall changes, etc., I could only send messages to Windows 7 machines. The above freeware apps worked right away sending to Windows XP machines and to Windows 7 machines. They work on both Workgroup LANs and on domains.
WinSend is a more traditional Instant Messaging application that starts at about $12 and goes down in price based on quantity of licenses purchased.
ssghsg sjjsjtr 146776378
lo mejor
I know this is old, but maybe someone has a solution.
My computer: PC
Target: LAPTOP (192.168.0.110)
msg /server:laptop * “Hello Laptop”
Returns * does not exist or is disconnected.
Trying with IP
msg /server:192.168.0.110 * “Hello Lappy”
Returns ‘Error 5 getting session names’
I have already applied the registry change and rebooted the machine multiple times.
Any other suggestions?
if both system is running on win7, then u need to add to receiver system’s login userid and password in “windows credentials”
you need to do what SUHAIL said…
and the computer wich you are triying to conect need a password, and user… added in windows credentials,
shearch in windows credential manager… and add the user and password…
My name is Ronald. Am new here. Am getting a lot of help from this forum.
I recommend to try http://messenger.softros.com . This app very stable and it has Terminal service support. Windows Server is supported too.
this is what did it for me. Needed notification from a remote service a long running job had finished!
Hi i tried to go to regedit and follow the steps but it doesn’t have a folder called HKML instead it has HKEY_CLASSES_ROOT and HKEY_CURRENT_USER etc. can i get the path for the folders i have?
HKLM is shorthand for HKEY_LOCAL_MACHINE in the Registry. I would suggest if you didn’t already know this, then you know too little to be fiddling around in there.
modify regedit file
Start
regedit
HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server
Name: AllowRemoteRPC
Type: REG_DWORD
Value: 1 (the dafault is ‘0’)
sending message
msg / SERVER: Destination User “send message”
regards
_______________________________________
modificar archivo regedit
Start
regedit
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
Name : AllowRemoteRPC
Type : REG_DWORD
Value : 1 (the dafault is â0â)
envio de mensaje
msg /SERVER:Destino Usuario “mensaje a enviar”
Saludos
It’s even easier! Just enter the following line into CMD or RUN (Win+R)
Reg ADD “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server” /v AllowRemoteRPC /d “1” /t REG_DWORD /f
Skype: Captain.TechLord I keep getting the Error: Access is denied> How do i fix this.
Wiz, try logging in as an administrator and/or running CMD and admin.
msg * /server:servername(or ip) messenger
Windows XP use the NET SEND command, Windows Vista got the MSG command, and Windows 7 Business, Enterprise, and Ultimate also have the MSG command, but Windows 7 Home was out of such commands. There is no simple command-line based messaging tool for LAN-wide messages included with Windows 7 Basic and Home, and recreating the command line experience is a hassle (as you need a replacement for both the command line tool msg.exe and for the messaging services running in the background).
If youâre not big fan of on a command line interface, a easy Windows 10 based application you may want to check out is LAN cet chat. Itâs looks like an usual IM client, and compatible with net-send/pop-up messages so older PCs on the network wonât even need the app installed to receive the messages.
i have a little promlem pls help
āĻ¤ā§āĻŽāĻžāĻ° āĻāĻžā§ āĻāĻžāĻ āĻāĻ°ā§ āĻ¨āĻžāĨ¤āĨ¤
āĻā§āĻ¯āĻžāĻ¨ āĻāĻ āĻāĻ āĻā§ āĻŽāĻŋ āĻŦāĻžāĻā§āĻāĻžāĻ˛ā§āĨ¤