[jcifs] jCifs writing to Mailslots

[Sascha Teifke]

Yes, they do.

IMHO, Netsend Messages are useful if you need to alert an amount of 
Win32 users without installing any client software
who needs to poll a specific network server. One Problem is, that there 
is no way to send messages to a specific list of
users at once. If you try to make a script that executes every single 
"net send" to shell you often have to wait a long time
because if a computer is turned off it may last up to a minute until it 
returns a message. Parallel processing of "net send"s
has made me mad - it seems like it isn't thread safe.

The environment I'm working in doesn't allow me to write any kind of 
client Software that could be installed on every client.
So I need to use the standard unrelieable way.

Sascha

Allen, Michael B (RSCH) wrote:

>Mmm, yeah. Unfortunately it's just API documentation which isn't that useful at this
>point. Looking at a quick capture it appears as though there is no session setup or tree
>connect at all. It's just an NBT session establishment message followed by a minimal
>SMB the format of the actual payload is as trivial as described below. This would require
>modifying the jcifs.smb files although it would not be difficult. The question is, why
>would one want to use this? It's a neat trick but it's not reliable. Does W2K or XP still
>support these messages?
>
>Mike
>
>  
>
>>-----Original Message-----
>>From:	Christopher R. Hertel [SMTP:crh at ubiqx.mn.org]
>>Sent:	Tuesday, June 10, 2003 1:19 AM
>>To:	Allen, Michael B (RSCH)
>>Cc:	'Sascha Teifke'; jcifs at lists.samba.org
>>Subject:	Re: [jcifs] jCifs writing to Mailslots
>>
>>"Allen, Michael B (RSCH)" wrote:
>>    
>>
>>>>-----Original Message-----
>>>>From: Sascha Teifke [SMTP:sascha at teifke.de]
>>>>
>>>>      FileOutputStream fos = new FileOutputStream( "SENDER\0SENDER\0My
>>>>Message \0\0" );
>>>>
>>>>        
>>>>
>>>        The FileOutputStream constructor takes a filename.
>>>
>>>        Anyway I don't think the win-popup message format is that simple. Ethereal
>>>        probably decodes them properly. Provided you use fos.write(str) you can go
>>>        back and fouth with Ethereal until the pipe mode is correct but then you'll
>>>        probably need to encode the message in binary. See the
>>>        jcifs/smb/SmbComXxx.java files for ideas.
>>>
>>>        Mike
>>>      
>>>
>>The messanger protocol is documented in the X/Open docs.  See:
>>
>>http://www.opengroup.org/products/publications/catalog/c195.htm
>>http://www.opengroup.org/products/publications/catalog/c209.htm
>>
>>    
>>
>
>
>  
>