Error 1722 The Rpc Server Is Unavailable Msg.exe
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: [RESOLVED] msg.exe XP -> Windows 7 Error [1722]:The RPC server is unavailable. Windows 7 IT Pro > Windows 7 Networking Question 0 Sign in to vote Hi.. i've been directed here from the Microsoft Answers networking forums. I'm having some problems using the msg utility between Windows XP and Windows 7. I have two computers on the network. PC1 is dual boot between XP Professional SP3 (x86) and Windows 7 Ultimate SP1 (x64). PC2 has Windows XP Professional SP3 (x86) installed. msg works without a problem from PC1 Windows 7 --> PC2 XP. It also works from PC1 XP --> PC2 XP and vice versa. However, I can't get things working from PC2 XP to Windows 7....I always get the following error: Error opening Terminal server PC1 Error [1722]:The RPC server is unavailable. I've tried disabling the firewalls on both computers but the error persists. I've also tried booting Windows 7 into safe mode with networking and then trying with Windows Firewall enabled and disabled but it still doesn't work. I'm thinking that it may be something to do with a setting in Windows 7 considering PC1 XP to PC2 XP and vice versa works ok. All OSs have ESET Smart Security installed and there is nothing in the logs to suggest that anything is being blocked...and as things didn't work in Safe Mode when ESET wasn't running, I don't think it's related to ESET. The AllowRemoteRPC registry value is present and correct on all computers. If anyone has any suggestions, that would be great. If you need more info, i'll be happy to provide. Cheers..
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 https://social.technet.microsoft.com/Forums/windows/en-US/26a6a330-2b5a-4f57-a706-e706be0bdbdd/resolved-msgexe-xp-windows-7-error-1722the-rpc-server-is-unavailable?forum=w7itpronetworking 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 https://www.experts-exchange.com/questions/27474855/error-1722-getting-session-names.html 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 http://techsupt.winbatch.com/TS/T000004018F13.html 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 Verified error 1722 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 ... 0 Question error 1722 the 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 Message Expert Comment by:Russell_V
msg.exe psexec.exe Question: I see that Microsoft has removed the Messenger service in Win7. I would like to send a message to a remote system. Does anyone have any tips on how to use the Terminal Service, wtsSendMessage on Windows 7? When I try and query a Win 7, it fails with Error 103, Unable to open terminal server handle. If I click on More Error Info I get : 6BA "WTSOpenServerAX() : WWWTS_OpenServer(). Answer: Terminal Services has been renamed Remote Desktop Services. Reference: http://msdn.microsoft.com/en-us/library/windows/desktop/dd979766(v=vs.85).aspx. The extended error 6BA is the Hex equivalent of the error 1722. The Windows System error 1722 indicates:1722 The RPC server is unavailable. RPC_S_SERVER_UNAVAILABLE This error is returned if a remote computer was specified in the lpServer parameter and the RPC server is not available. By default remote RPC is disabled on Windows 7. It can be enabled by setting the 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server' value 'AllowRemoteRPC' to 1. However, this will only get you another error - 0x721 - which I am guessing is caused by Windows 7 not allowing 'nul' user access. There are several possible ways around this problem but I haven't tried any of them. One approach would be to add credentials from remote machines to the credential cache on the sending machine but I don't know how practical that is. There may be a way to allow 'nul' user access but that is probably not a good idea either. For what it is worth, one reported solution is to use syteminternal's psexec.exe and the built-in msg.exe command line tool to display message on the remote system. It does have the advantage of circumventing the RPC issue but I don't know that it would not just generate its own set of annoyances. User Reply: It was the AllowRemoteRPC key change to 1. Article ID: W17608 Filename: wtsS