Just wondering if there is a way to send a WinPopup message to a user (using username). I have had a look at smbclient but it appears to only allow sending messages to a computer name. Thanks in advance, Russell Kliese
Russell, Seeing as you have gotten no response yet, I will lend my uneducated piece of observational guesswork. The NT machine which I use, when I log on, registers itself with the WINS server as an 03 resource type (i.e. able to receive WinPopUp messages) under both the machine name _and_ my logon name. This is verified by performing an nmblookup -R -U wins-server 'username#03', which returns a value, as does the same query with the machine name. So you should be able to use smbclient -M username and get the message to go to them. Again, this is on my NT machine - I have no idea if this is standard or freakish behavior. Good luck! Russell Kliese wrote:> > Just wondering if there is a way to send a WinPopup message to a user > (using username). I have had a look at smbclient but it appears to only > allow sending messages to a computer name. > > Thanks in advance, > > Russell Kliese-- Bill Knox Senior Operating Systems Programmer/Analyst The MITRE Corporation
Just wanting to thank the people who responded to my problem and post the solution that worked for me. Russell>> >> Just wondering if there is a way to send a WinPopup message to a user>> (using username). I have had a look at smbclient but it appears toonly>> allow sending messages to a computer name. > >You could try and work round this. Use nmblookup to elucidate the >machine that your use is logged into. For example, you can do this:- > >$ nmblookup mb#03 >querying mb on 192.168.1.255 >192.168.1.110 mb<03> > >this'll show you the IP address of the host you're trying to send the >winpopup message to. > >Using the -S flag to nmblookup should do a node status query on thehost>in question. I used to have this working, but on my system, nmblookup's>status query returns nothing, and I've no idea what went wrong >(anybody??), so I don't trust it very much at the moment. You can also >parse the output of smbstatus to get the client name. After you've got >the netbios name of the machine, it hsould be easy. > >HTH, > >Mike