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

  • 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

    • Will be available in EventViewer. Suppose they could have also displayed upon next log-on (same as 'didn't shutdown properly' on servers) but seems not.
    • PasteBar 0.7.0 by Razvan Serea PasteBar is a powerful yet free clipboard manager that revolutionizes how you copy, organize, and reuse information. Packed with smart features, it enhances productivity and simplifies your workflow by minimizing repetitive copy-paste tasks—so you can work faster and smarter. PasteBar offers powerful clipboard management with unlimited history, searchable copy records, and note support, making it easy to retrieve past clips. You can save and organize clips into custom collections, tabs, or boards for quick access through intuitive paste menus. Privacy is a priority, with local storage, passcode protection, and PIN-locked collections ensuring your data stays secure. The app also supports custom storage locations, giving you full control over where your clipboard history is saved. Beyond basic clipboard functions, PasteBar includes smart features like support for text, images, files, and code snippets—complete with syntax highlighting and Markdown formatting. A global search function, instant pasting, and dark theme enhance usability, while customization options let you tailor hotkeys, tray behavior, and text filters. Cross-platform compatibility (macOS & Windows) ensures seamless workflow integration, with added tools for web scraping, API data extraction, and multi-language support. Backup and restore capabilities provide extra peace of mind, making PasteBar a versatile productivity tool. PasteBar 0.7.0 changelog: Added backup and restore database and images Added custom data location to store application data in a folder of your choice instead of the default location Added keyboard shortcuts to improve navigation efficiency within the application Added long press on clip to activate clips organize Added "Trim Spaces" option for clips and "Auto Trim Spaces" option for History Capture Added Quick history window user options Added option to disable capturing and storing images from clipboard Implemented clipboard history filtering based on text length limits Added support for setting hotkeys with up to 3-key combinations Fixed update history items in quick paste window after delete operation in main window Added user setting for single-click keyboard focus in history Refactored terminology for history window split to open Updated to React 19 and React Compiler Auto-activate search in quick paste window when typing any letter or number Added single-click copy/paste option in user preferences Added persistent note icons for clips with descriptions Added detect and select language modal on first app run Fixed refresh native menu on history items delete Added history item preview max lines user setting Added protected collection with PIN access Added special copy/paste for history items context menu and settings Added global templates in user preferences for saved clips Press Delete key to delete single or multiple items with confirmation on second press Added customizable tray icon behavior on Windows as user settings Added user preference to copy only menu items to clipboard without auto-pasting Fixed enhance value preview logic to fix text overflow Updated French language translation from Jean-Michel Robert Added deleting menu folders with children by moving submenus up one level Fixed user preferences UI color bug for languages Added settings to preserve pinned and starred items when clearing clipboard history Added option "Show Always on Top" for main window Added support for notes matching in global search Added Turkish language translation by AlijonMurodov Updated Chinese translation by katelya77 Download: PasteBar | Portable | ~30.0 MB (Open Source) Download: PasteBar ARM64 | Portable ARM64 Links: PasteBar Website | Screenshot | MS Store Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Well, it seems version 4.9 doesn't work well at least when trying to make a WinToGo USB. It ends very fast with an error. Had to use 4.8 instead.
    • Hundreds of printer models with weak password algorithms exposed, no firmware patch possible by Usama Jawad Many people don't think or care about it, but printer security is a pretty important avenue when it comes to evaluating your cybersecurity posture. Last month, it was found that the companion software for Procolored printers was distributing malware. Now, it has been revealed that hundreds of printer models all over the globe are susceptible to attacks targeting their admin credentials. Bleeping Computer has reported that CVE-2024-51978 is a one of the eight printer vulnerabilities recently discovered by security researchers. Combined, these allow authenticated and unauthenticated attackers to discover the default admin password, perform remote code execution (RCE), crash the printer, and leak other sensitive information. Severity ratings go from a score of 5.3 (medium) to 9.8 (critical), indicating that these are pretty severe vulnerabilities. The most dangerous vulnerability in there exposes the default admin password, and primarily affects Brother printers. This is because Brother utilizes a rather weak password generation algorithm that is highly dependent upon the device's serial number and a static salt table. Analysis of the code revealed that the first 16 characters of the serial number are appended with eight bytes from a static salt table, with the results being hashed with SHA256 and Base64-encoded. Finally, the first eight characters are then taken and some of them are replaced with special characters to form the password. The static nature of the password generation algorithm means that an attacker can chain various existing vulnerabilities to get access to your serial number and eventually your default admin password. It is important to note that not all printer models are affected by all of these flaws, but the default admin password exposure does affect 695 models. The breakdown for the number of printer model affected by the eight vulnerabilities is as follows: Brother: 689 Fujifilm: 46 Konica Minolta: 6 Ricoh: 5 Toshiba: 2 Brother has informed the security researchers that it cannot fully remediate the password generation vulnerability through a firmware patch. It can only fix the issue in its next printer models by patching the problem during the manufacturing process. This makes it crucial for customers of affected models to change their default admin password as soon as possible, which is good practice anyway.
  • Recent Achievements

    • Week One Done
      suprememobiles earned a badge
      Week One Done
    • Week One Done
      Marites earned a badge
      Week One Done
    • One Year In
      runge100 earned a badge
      One Year In
    • One Month Later
      runge100 earned a badge
      One Month Later
    • One Month Later
      jfam earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      567
    2. 2
      +FloatingFatMan
      177
    3. 3
      ATLien_0
      169
    4. 4
      Michael Scrip
      127
    5. 5
      Xenon
      119
  • Tell a friend

    Love Neowin? Tell a friend!