How do I use msg in Windows 7?

Discussion in 'Windows 7 Networking' started by sinkingshriek, Jan 26, 2010.

  1. sinkingshriek

    sinkingshriek New Member

    Jan 26, 2010
    Likes Received:
    Ok so I searched the whole internet for this but I still can't figure out what the problem is. I just want to send simple txt message between local computers. We are all in the same group "workgroup" but everytime I type:
    msg * "test message"
    I only get the message and noone else gets it.
    And when I try:-
    msg /:server:workgroup friend_username "test message"
    I get an error message saying
    Error 1722 getting session names

    I and my friend's PC both have Windows 7 and we are on same group. Why can't I send a simple txt message between my local computers?? Someone help.

  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Aug 28, 2007
    Likes Received:
  3. Trouble

    Trouble Noob Whisperer

    Nov 30, 2009
    Likes Received:
    Hello and welcome to the forums. Good luck getting it to work, I gave up after a while, when most research seemed to indicate that msg.exe was only for use in terminal server environments. You might want to take a look at this as a free alternative WinSent Messenger - frequently asked questions. If WinSent does not work, help, install, setup, problem solving, winpopup and net send. I don't need it bad enough to try it, so the decision is up to you. But I sure do miss good ole WinPopUp and NetSend
    Hope this helps
  4. ethenshaw

    ethenshaw New Member

    Oct 19, 2010
    Likes Received:
    Next, test MSG.EXE by typing the following command:

    C:'Windows'system32>msg /?
    Send a message to a user.

    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. Running a command like this one:

    C:'msg /server:seidon daniel "Please contact help desk immediately!"
    Will result in a message being sent to the seidon computer, to Daniel's session.
    BTW, the MSG.EXE command does NOT require the Messenger service to be running on the target computer.
    #4 ethenshaw, Oct 19, 2010
    Last edited: Oct 19, 2010
  5. vinomalo

    vinomalo New Member

    Jun 28, 2011
    Likes Received:
    Hello, I did not manage to work out .msg command, so I tried dmessage and winpopup ... You can try them too Good luck
  6. TheCric

    TheCric New Member

    Oct 18, 2011
    Likes Received:
    I suppose the message "Error 1722 getting session names"
    is translated by MS to french as
    "Erreur 5 lors de l'obtention des noms de session"

    For my "french" computers the solution is to change AllowRemoteRPC to 1
    in the registry of the machines you want to address to

    launch regedit.exe (You have to be administrator to do that)
    goto HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
    and change AllowRemoteRPC from the value 0 to the value 1
    on each machine which should be able to receive a message

    this is tested ok between computers with Seven enterprise or Ultimate, I don't know for the other
    1 person likes this.

Share This Page