3 replies
by madanpms Accepted solution
by nathan. Accepted solution
net send "computer/domain" "message"
This requires messenger service enabled on all pc's in the org to work and is disabled by default in service pack 2 cause of a vulnerability to certain DOS attacks and advertising crap.
I think there's also some third party programs out there that also do the same thing.
PS.
If you do decide to enable the messenger service to use the net send command, make sure to properly secure and block the netbios ports at the firewall.
by rob miners Accepted solution
C:\>msg.exe /?
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.
C:\>
Keep us informed as to your progress if you require further assistance.
If you think that any of these posts have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending