Recommended Posts

Well for one, its not really the same as net send. And you have the syntax wrong.. Its

MSG {username | sessionname | sessionid | @filename | *}

[/sERVER:servername] [/TIME:seconds] [/V] [/W] [message]

username Identifies the specified username.

sessionname The name of the session.

sessionid The ID of the session.

@filename Identifies a file containing a list of usernames,

sessionnames, and sessionids to send the message to.

* Send message to all sessions on specified server.

/SERVER:servername server to contact (default is current).

/TIME:seconds Time delay to wait for receiver to acknowledge msg.

/V Display information about actions being performed.

/W Wait for response from user, useful with /V.

message Message to send. If none specified, prompts for it

or reads from stdin.

So for example - from my one quad-w7 to other box p4-28g

msg adminstrator /server:p4-28g.local.lan test

post-14624-12677363813267_thumb.jpg

But just tested and you can put the /server before the username -- you might have a firewall blocking?

Link to comment
https://www.neowin.net/forum/topic/880618-using-msgexe/#findComment-592310642
Share on other sites

  On 05/03/2010 at 23:21, mzta cody said:

BudMan, I don't know if anyone else has said this, but I find your posts responding to various issues to be of a high quality. I almost always learn something reading them. Just wanted to say that.

Ditto, I enjoy them very much. Thanks BudMan!

Link to comment
https://www.neowin.net/forum/topic/880618-using-msgexe/#findComment-592316012
Share on other sites

I try and help as much as I can -- glad you guys are learning something!! If you like my posts -- make sure to vote them up.. The green + signs.. ;)

Link to comment
https://www.neowin.net/forum/topic/880618-using-msgexe/#findComment-592316538
Share on other sites

  • 3 months later...

I still can't get this to work. I am trying to send between XP and 7, when sending from XP it gets a access denied error. Vista and 7 say the user doesn't exist or is disconnected.

Yet I can sucessfully make each system send a msg to it's self.

All in the same workgroup.

perhaps you can't send between these OS's.

Anyone know whether this is possible?

Link to comment
https://www.neowin.net/forum/topic/880618-using-msgexe/#findComment-592800152
Share on other sites

Ok -- when I tested it was from win7 to a 2k8 box.. So this was allowed by default since AllowRemoteRPC is set to 1 in the reg..

So I tested and duplicated your problem -- but then set on both machines

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AllowRemoteRPC to 1

So I have now tested with xp --> w7 and win7 to xp and both ways work.

post-14624-12773190977655.jpg

Now I am logged into each machine as bud with the same password - so there is no permissions issues..

So I tested by logging in with a different account, and got access denied. So looking into that.. Also seem to have issues sending msg to different account logged other machine when even logged into account that matches up with account on other machine that has admin rights. So clearly some issues between w7 and xp.. But again this msg tool is really designed for sending messages to true terminal server.. I have to do some real work ;) but will get back to it to see if there is a way to make it work.. But for sure your going to have to enable allowremoterpc with w7 and or xp.. Just need to figure out what other permissions are coming into play.. Seems unable to determine if user session is there, even when account that has admin right on other machine using passthrough.

Getting this error when try to send from bud account on xp that matches up with bud account on w7 with same password, but bud-w7 is logged into the win7 box.

bud-w7 does not exist or is disconnected

So you found something interesting to look into ;)

Link to comment
https://www.neowin.net/forum/topic/880618-using-msgexe/#findComment-592804292
Share on other sites

Ok -- figured out the issue I was seeing when trying to send to different users on the win7 box..

To xp from win7 works fine.

post-14624-12773266863119.jpg

As you can see bud-xp is logged into the xp box, and I sent him a message from the win7 box logged in as bud, and there is a bud account on the xp box with the same password to no permission issues. And by default admin shares are enabled on xp.

Now sending from xp to win 7, logged in as bud that matches up with an account on win 7 I was only able to send messages to bud, if he was logged in to the win7 box, if logged in with different account would get "user does not exist or is disconnected" error.

So I enabled admin shares on the win 7 box -- need to create this dword

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy and set to 1

This enables admin shares on win7, which are disabled out of the box.

Now I can send to a different account, ie bud-w7

post-14624-12773269650925.jpg

So for this to work in a non domain setup.. The account your using to send the message with has to have a matching admin account on the boxes your sending too, and looks like admin shares have to be enabled - which on win7 are disabled by default. And from before you also need the allowremoterpc setting.

Link to comment
https://www.neowin.net/forum/topic/880618-using-msgexe/#findComment-592804828
Share on other sites

Only vista box, which I just have not updated yet is my son's laptop who is no longer in the house - so would have to fire up a test box to verify.. But I would assume it would be the same, you would need to allow the do the allowremoterpc, and Im like 99% sure that vista also by default has the admin shares disabled - so will also need to do the LocalAccountTokenFilterPolicy -- if you have problems with it just let me know and will fire up a test of it.

Link to comment
https://www.neowin.net/forum/topic/880618-using-msgexe/#findComment-592808474
Share on other sites

  • 1 year later...
  • 1 month later...
  • 2 years later...

Hi, ok I know this topic is old, but I'm trying everything on this thread and I'm seeing flames. I'm failing to send a message from XP to Win7, maybe what I need is a step by step guide. When I run "msg win7 /server:testxp testing xp" I get, Error opening Terminal server testxp
Error [1722]:The RPC server is unavailable. HELP!!!!

Link to comment
https://www.neowin.net/forum/topic/880618-using-msgexe/#findComment-596613217
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.2.3 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.2.3 changelog: All GPUs: Fixed hardware rescan issue when cleaning all GPUs without restarting or shutting down UI: Added Guru3D mention in the About section. General: Various fixes and enhancements. Download: Display Driver Uninstaller (DDU) 18.1.2.3 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot | Forum Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • That would be nice, if excel could refresh pivot tables without bugs. Frequently you refresh a pivot and all parameters get lost. Now this will happen automatically. Bravo MS!
    • If one could ever put all the crap of the world in one box, that would be Microsoft.
    • The most corrupt and vile CEO any company ever had ! The only company that makes an insane amount of money decade after decade but doesn't deliver on even barely passable quality to customers, screws over partners and treats employees like trash
  • Recent Achievements

    • Dedicated
      Profit earned a badge
      Dedicated
    • One Month Later
      hhgygy earned a badge
      One Month Later
    • Week One Done
      hhgygy earned a badge
      Week One Done
    • One Year In
      NIKI77 earned a badge
      One Year In
    • Week One Done
      artistro08 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      631
    2. 2
      ATLien_0
      237
    3. 3
      Xenon
      167
    4. 4
      neufuse
      146
    5. 5
      +FloatingFatMan
      123
  • Tell a friend

    Love Neowin? Tell a friend!