Error 1722 Setting Session Names Msg.exe
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error:1722 Getting session names up vote 1 down vote favorite I am trying to check if anybody is connected to the server in my team with the following command: query session /server:
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > error 1722 getting session names Want to Advertise Here? Solved error 1722 getting session names Posted on 2011-12-02 Networking MS Legacy OS 1 http://stackoverflow.com/questions/31021809/error1722-getting-session-names Verified Solution 22 Comments 7,045 Views Last Modified: 2012-05-12 Trying to send a broadcast from Windows Server 2008 to a XP station Use msg.exe (net send does not exist anymore) Gives the above message But from the server to the server it works, and also from the station to itself, so it seems RPC is okay on both platform ... https://www.experts-exchange.com/questions/27474855/error-1722-getting-session-names.html 0 Question by:LeTay Facebook Twitter LinkedIn Google LVL 12 Best Solution byibrahim52 Alright, a similar discussion is available. Have a look at it. Good luck. Referred Link : http://www.neowin.net/forum/topic/880618-using-msgexe/ Go to Solution 21 Comments LVL 12 Overall: Level 12 MS Legacy OS 6 Networking 1 Message Expert Comment by:ibrahim522011-12-02 It works only on a DOMAIN environment, but if you have a WORKGROUP. It won't work. 0 LVL 12 Overall: Level 12 MS Legacy OS 6 Networking 1 Message Accepted Solution by:ibrahim522011-12-02 Alright, a similar discussion is available. Have a look at it. Good luck. Referred Link : http://www.neowin.net/forum/topic/880618-using-msgexe/ 0 Message Author Comment by:LeTay2011-12-02 It is in a DOMAIN dear friends 0 LVL 12 Overall: Level 12 MS Legacy OS 6 Networking 1 Message Expert Comment by:ibrahim522011-12-02 But did you visit that link ? 0 Message Author Comment by:LeTay2011-12-03 Yes but it did not help me It is maybe a problem of firewall ... Does msg.exe uses a specific port ? 0 LVL 15 Overall: Level 15 MS Legacy OS 5 Networking 2
7 umito Uncategorized Windows Tags error 5, msg, Windows 2008, windows 7 Solution to Msg.exe "Error 5 getting session names" by peterdk on February 20th, 2010 Info My Windows-Server 2008 R2 machine couldn't msg http://blog.umito.nl/2010/02/20/solution-to-msg-exe-error-5-getting-session-names.html/comment-page-1 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 error 1722 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. 🙂 Tweet From → Windows 28 Comments → wick422 permalink I did this on all my Windows 7 error 1722 setting 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. peterdk permalink 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? AbO 3atreeS permalink hey [wick422] try this one msg /server:servername * yourmessage Example: msg /server:AMMAR-LAPTOP * HelloThere! Alex permalink Try msg * /server:AMMAR-LAPTOP "HelloThere!" superray permalink 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