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

    • Debian switches to 64-bit time completely to avoid Y2K38 disaster by Usama Jawad Some of you may remember the Y2K problem, where the world expected airplanes to fall from the sky as soon as we reached the year 2000, primarily because many software applications at that time typically just used the final two digits of each year to store calendar year data, which meant that the year 2000 was indistinguishable from the year 1900. Fortunately, we were able to avoid the 2K problem, thanks to the tireless efforts of many software vendors and engineers. Now, we are a few years away from a similar issue, and it looks like the Linux distro Debian wants to solve that problem right now in its own operating system. Basically, older 32-bit architectures will face the Y2K38 problem in the year 2038. This is because the signed representation of Unix datetime values will overflow the 32-bit space, which would cause bugs in associated software. Debian is a pretty old distro with its first release dating back to 1993, so the maintainers say that a lot of sensitive computing is still happening on 32-bit architecture. Although there are still roughly 13 years to go before we reach 2038, developers want to proactively tackle the problem rather than having to scramble at the last minute like with Y2K, according to The Register. Another name for Y2K38 is the Unix Epochalypse, since it impacts systems that store datetime values in the Unix format within a signed 32-bit space. On January 19, 2038, 03:14:07 UTC, this space will overflow. As such, Debian maintainers will use 64-bit time_t formats even on 32-bit architectures starting with the release of Debian 13 "Trixie". This is not a small change, as maintainers found the use of the time_t variable in random places across 6,429 packages. The maintainers went on to say that: This may be a breaking change for some applications, so it is important to test your program's response to the time_t variable switch by leveraging the Debian wiki. Interestingly, Y2K38 may also impact certain older Windows programs and out-of-support Windows operating systems.
    • I hope they programed its eyes to turn red when it becomes evil, that is an important feature for any AI representation.
    • Microsoft gives Copilot visual appearance with real-time expressions and emotions by Taras Buria Several months ago, during its 50th anniversary event, Microsoft teased a visual upgrade for Copilot (then called "Copilot Avatar") that would give the chatbot a visual character with expressions, reactions, and emotions. Now, users in the US, UK, and Canada can try Copilot Appearance, "a new, visual way to chat." Conversational mode has been available in Copilot for a while, but it lacked any visual cues or non-verbal communications. All users see on their screens is some abstract animation. With Copilot Appearance, Microsoft is improving voice conversations with real-time visual expressions. Sadly, Copilot Appearance is not a Clippy 2.0. In its current form, it is an abstract blob with a face that can morph into different shapes, express emotions, nod in agreement, etc. The concept is similar to what xAI offers with Grok AI companions that cost $300 per month, but Microsoft's approach is much more toned down (and you cannot undress it). On the official Copilot Labs website, Microsoft describes Copilot Appearance as "an experiment to incorporate a more visual, engaging experience into Copilot." Copilot Appearance is rolling out to a limited set of users in just three countries as Microsoft takes a cautious approach to a more personified AI. If you have a lucky ticket, you can try Copilot Appearance by launching Voice Mode (click the microphone button in the composer) and toggling the feature in Voice Mode settings. Microsoft says that the initial release is experimental, and it is working on refining the experience.
    • A number of years ago I purchased a "Renewed" HP laptop. It worked great until it didn't work at all. Both of my W11 devices are HP AIO desktops. Have had them since before W11. They upgraded fine and have worked great ever since. My printer is also an HP inkjet. I have had it several years and have never paid for ink.
    • If you use AdGuard on your PC, you can find the new "Disable Windows Recall" feature in Settings > Tracking Protection. The "Disable Windows Recall" feature in Adguard 7.21 in turned on by default. No need to do anything if you want to use the feature.
  • Recent Achievements

    • Week One Done
      CyberCeps666 earned a badge
      Week One Done
    • Very Popular
      d4l3d earned a badge
      Very Popular
    • Dedicated
      Stephen Leibowitz earned a badge
      Dedicated
    • Dedicated
      Snake Doc earned a badge
      Dedicated
    • One Month Later
      Philsl earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      626
    2. 2
      ATLien_0
      240
    3. 3
      Xenon
      163
    4. 4
      +FloatingFatMan
      124
    5. 5
      neufuse
      123
  • Tell a friend

    Love Neowin? Tell a friend!