X-no-Archive:yes
Thanks, Chris and Lars, for suggesting smbclient and providing details
instructions. Works well. Interesting that in spite of the "Type your
message, ending it with a Control-D" message, :EOD is what does the trick.

For me, this idea raises some questions. The first is how to work this out
dynamically, so that for any user who for instance streams a particular job,
that job could resolve !HPSTREAMEDBY to a host name for -M. Even more
generically, what might be a good means to, for instance, send out "two
minute warning" messages (using smbclient, and from the 3000) only to users
who are currently connected when quiescing the system for backups? Since
DHCP is available, hardcoding some logic for IP addresses and host names
will not work.

Finally, our 3000 is on another network segment. So we have to use the
remote announce setting in smb.conf with our WINS server as its argument, to
have our 3000s show up in Network Neighborhood. The reverse is also a
problem - to send a message, smbclient seems to require both the host name
and the IP address. Can SAMBA use our WINS server for host name lookups?