feesu
asked on
Windows 7 - "Net Send" command alternative
Hi Experts,
I used to use the "Net Send" command line to send messages to other PCs in my LAN.
Now, my laptop is running Windows 7, and other LAN PCs are running XP (90% of them).
How do I use a similar commands? What do I need to install? Do I need to install on the recipient PCs too??
I used to use the "Net Send" command line to send messages to other PCs in my LAN.
Now, my laptop is running Windows 7, and other LAN PCs are running XP (90% of them).
How do I use a similar commands? What do I need to install? Do I need to install on the recipient PCs too??
msg.exe
ASKER
Hi Michael,
You answered less than half of my question :)
>> How do I use a similar commands? What do I need to install? Do I need to install on the recipient PCs too??
You answered less than half of my question :)
>> How do I use a similar commands? What do I need to install? Do I need to install on the recipient PCs too??
Whoops, sorry fella :)
The msg /? command at a command prompt will get you the switches etc to use:-
C:\Users\michael.claridge> 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.
C:\Users\michael.claridge>
MSG.exe replaces Net Send in Windows 7 but isn't avialable for Home Versions.
I think you should be able to still send messages via MSG.exe to Windows XP PC's as long as the messenger service is running :)
Cheers
Michael
The msg /? command at a command prompt will get you the switches etc to use:-
C:\Users\michael.claridge>
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:\Users\michael.claridge>
MSG.exe replaces Net Send in Windows 7 but isn't avialable for Home Versions.
I think you should be able to still send messages via MSG.exe to Windows XP PC's as long as the messenger service is running :)
Cheers
Michael
ASKER
I can't beleive you coppied and pasted that help from the command prompt :D
I have got this IP on my network 192.168.2.73
I wish to send him "Hey!"
Write for me the full command please!
I have got this IP on my network 192.168.2.73
I wish to send him "Hey!"
Write for me the full command please!
I don't believe using msg.exe to send to IP Addresses is possible, there certainly isn't a switch for it. The below is what you would use with the available switches, but this does not work for me her.
msg /server:172.18.3.3 "Hello!"
Cheers
Michael
msg /server:172.18.3.3 "Hello!"
Cheers
Michael
You don't need the messenger service for msg.exe. And yes, it works on XP, W2000 and up. But to send it to all users on a certain workstation, you need to provide an asterisk:
msg * /server:192.168.2.73 /w /v /time:0 Hey! What's up?
That combination sends to all users (*), waits for confirmation (/w), gives verbose output to you (/v), and waits infinitive (/time:0). You can change any of those switches to your liking. I usually issue /time:60 and no wait, so the "nagging" message box disappears after 60 seconds.
msg * /server:192.168.2.73 /w /v /time:0 Hey! What's up?
That combination sends to all users (*), waits for confirmation (/w), gives verbose output to you (/v), and waits infinitive (/time:0). You can change any of those switches to your liking. I usually issue /time:60 and no wait, so the "nagging" message box disappears after 60 seconds.
To clarify some of the above answers....
The MSG command sends a message to *person*... not to a *machine*. So, instead of specifying the IP address of the machine where the person is currently logged in, instead you specify the name of the account for the user.
The /Server option allows you to choose which machine will perform the sending of the message (which might be useful if the ports are blocked on workstations, but not on servers, as an example).
The MSG command sends a message to *person*... not to a *machine*. So, instead of specifying the IP address of the machine where the person is currently logged in, instead you specify the name of the account for the user.
The /Server option allows you to choose which machine will perform the sending of the message (which might be useful if the ports are blocked on workstations, but not on servers, as an example).
graye,
That's not correct. MSG sends a message to at least one person (or session) on one machine. It is not searching automatically for domain users or such, only for sessions on the given machine.
That's not correct. MSG sends a message to at least one person (or session) on one machine. It is not searching automatically for domain users or such, only for sessions on the given machine.
Well, I'll wear orthopedic shoes and stand corrected!
You're right... it was designed to send messages to users that are currently logged into a particular machine.
You're right... it was designed to send messages to users that are currently logged into a particular machine.
Its better to install any lan messenger.
ASKER
But will I need to install it on all clients?
"It's better to" needs some reasoning - why should it be better?
You did not tell us which way you want to follow: The Lan Manager (using a software to be installed on every client), or msg.exe (using a script determining all PCs in your domain or workgroup).
ASKER
I told you at the beginning that I prefer to send from my PC without having to install something on clients.
You did NOT tell us anywhere in this thread what you prefer.
However, this would be how to do it without installing anything, working on any target starting with XP:
@echo off
for /F "delims=\" %%C in ('net view ^| find "\\"') do msg * /server:%%C /time:30 Hey^!
However, this would be how to do it without installing anything, working on any target starting with XP:
@echo off
for /F "delims=\" %%C in ('net view ^| find "\\"') do msg * /server:%%C /time:30 Hey^!
Activity resumed, and waiting for OP acknowledgement.
ASKER
Qlemo,
In my question, I said that I used to use Net Send and I am looking for an alternative, which means that the first choice would be something similar to Net Send, which does not require installation of any third party.
In your last example, where do you specify the IP of the recipient?
Thank you,
In my question, I said that I used to use Net Send and I am looking for an alternative, which means that the first choice would be something similar to Net Send, which does not require installation of any third party.
In your last example, where do you specify the IP of the recipient?
Thank you,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.