Re: SMBClient - Messenger service
Simo Sorce wrote: > > We are always interested in things that add functionality into samba. > If you wish to send some patches we can look at, you are welcome. I was originally bouncing ideas back and forth on this (and sitting on patches etc :-), but if you want to case it up you are more than welcome to it... I already have my fingers in too many pies... Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net
Re: SMBClient - Messenger service
On Tue, Oct 22, 2002 at 11:13:34AM -0500, Christopher R. Hertel wrote: : > Oh, by the way, I'm getting SEGV when I try to test this using smbclient > from 2.2.6. Anyone else see this? Skip that. I cleaned up my build environment, removed config.cache and proto.h, rebuilt things, and the problem went away. I should know better by now. Chridz -)- -- Samba Team -- http://www.samba.org/ -)- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)- [EMAIL PROTECTED] OnLineBook -- http://ubiqx.org/cifs/-)- [EMAIL PROTECTED]
Re: SMBClient - Messenger service
On Tue, Oct 22, 2002 at 03:56:31PM +0100, David Lee wrote: : > The single-frame version can only send a short message (less than 128 > bytes), whereas the multi-frame version allows up to 1600 bytes total. See > the description of the "File Sharing Protocol". (Use Google to search for > "INTEL Part Number 138446".) Cool. Thanks for the pointer! > Over the last couple of years I have looked at generalising this code in > Samba, and made some progress. (In a test implementation, I was able to > use UNIX commands such as "wall" and "write" to produce WinPopup messages > on the client PCs.) This required extracting, and altering, some code > from smbclient, but this can be done in a re-useable way. > > If someone of the Samba Team is willing to facilitate this, I'll willingly > submit the changes I made as a possible starting-point. I might be able to do that. What do you have in mind. Chris -)- -- Samba Team -- http://www.samba.org/ -)- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)- [EMAIL PROTECTED] OnLineBook -- http://ubiqx.org/cifs/-)- [EMAIL PROTECTED]
Re: SMBClient - Messenger service
The question below is a good one. Windows sends message service (WinPopUp) messages in a single SMB packet. SMBClient uses three packets. The highly edited Ethereal output is below: No. Source Destination Protocol Info 4 LinuxWin95 NBSS Session request, to WIN95<03> from LINUX<00> 5 Win95Linux NBSS Positive session response 7 LinuxWin95 SMB Send Start of Multi-block Message Request 9 Win95Linux SMB Send Start of Multi-block Message Response 10 LinuxWin95 SMB Send Text of Multi-block Message Request 12 Win95Linux SMB Send Text of Multi-block Message Response 13 LinuxWin95 SMB Send End of Multi-block Message Request 15 Win95Linux SMB Send End of Multi-block Message Response 25 WinntWin95 NBSS Session request, to WIN95<03> from WINNT<01> 26 Win95Winnt NBSS Positive session response 28 WinntWin95 SMB Send Single Block Message Request 30 Win95Winnt SMB Send Single Block Message Response The interesting things are: - WindowsNT registers and uses the machine<01> name as the source name for the messanger service, but smbclient uses the machine<00> name. Curiously, Windows2K uses the machine<03> name as the source name. Wierd. - Ethereal version 0.9.6 isn't able to parse the "Send Text of Multi-block Message Request" message sent by smbclient. It says: Word Count (WCT): 1 Byte Count (BCC): 2 Buffer Format: Unknown (8) It looks to me as though the word count and byte count are just plain wrong. I'll have to take a look when I get a chance. I remember some discussion about the messanger service so this may have been fixed recently. - NT4 requires only two SMB messages to do the job, while smbclient generates six. - The Messanger Service is not documented in the Leach draft and I don't see it in the SNIA doc either. I'm not sure where to look so if anyone has any clues... I'm interested in this (obviously). I'm wondering if someone has pointers to docs. I'm curious to know why the multi-block method (SMBsendstrt, SMBsendtxt, SMBsendend) was chosen over the single block (SMBsends). I also need to see if/why smbclient is getting the block sizes wrong. Oh, by the way, I'm getting SEGV when I try to test this using smbclient from 2.2.6. Anyone else see this? Chris -)- On Tue, Oct 22, 2002 at 10:08:21AM +0100, Nuno Cardoso wrote: > Hi. > > When I use "net send ..." command in windows to send a Winpopup message > to other host, the SMB Command associate to this message is single block > message (0xD0). To do this, it is only necessary sends one SMB "frame" > to the other host. > > When I use SMBClient (samba), the SMB Command associate is multi-block > message (fist it is necessary sends the start comand 0xD5, then a text > comand 0xD7 and finally the end 0xD6). To do this, It is necessary sends > 3 SMB "frames". > > Why SMBClient sends winpopup messages with multi-block message, and not > single block message > Where I use multi and where I use single message block??? > > Nuno Cardoso. -- Samba Team -- http://www.samba.org/ -)- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)- [EMAIL PROTECTED] OnLineBook -- http://ubiqx.org/cifs/-)- [EMAIL PROTECTED]
Re: SMBClient - Messenger service
We are always interested in things that add functionality into samba. If you wish to send some patches we can look at, you are welcome. Simo. On Tue, 2002-10-22 at 16:56, David Lee wrote: > > Why SMBClient sends winpopup messages with multi-block message, and not > > single block message Where I use multi and where I use single > > message block??? > > The single-frame version can only send a short message (less than 128 > bytes), whereas the multi-frame version allows up to 1600 bytes total. See > the description of the "File Sharing Protocol". (Use Google to search for > "INTEL Part Number 138446".) > > Over the last couple of years I have looked at generalising this code in > Samba, and made some progress. (In a test implementation, I was able to > use UNIX commands such as "wall" and "write" to produce WinPopup messages > on the client PCs.) This required extracting, and altering, some code > from smbclient, but this can be done in a re-useable way. > > If someone of the Samba Team is willing to facilitate this, I'll willingly > submit the changes I made as a possible starting-point. > > -- > > : David LeeI.T. Service : > : Systems Programmer Computer Centre : > : University of Durham : > : http://www.dur.ac.uk/t.d.lee/South Road: > : Durham: > : Phone: +44 191 374 2882 U.K. : -- Simo Sorce - [EMAIL PROTECTED] Xsec s.r.l. via Durando 10 Ed. G - 20158 - Milano tel. +39 02 2399 7130 - fax: +39 02 700 442 399 signature.asc Description: This is a digitally signed message part
Re: SMBClient - Messenger service
On Tue, 22 Oct 2002, Nuno Cardoso wrote: > When I use "net send ..." command in windows to send a Winpopup message > to other host, the SMB Command associate to this message is single block > message (0xD0). To do this, it is only necessary sends one SMB "frame" > to the other host. > > When I use SMBClient (samba), the SMB Command associate is multi-block > message (fist it is necessary sends the start comand 0xD5, then a text > comand 0xD7 and finally the end 0xD6). To do this, It is necessary sends > 3 SMB "frames". > > Why SMBClient sends winpopup messages with multi-block message, and not > single block message Where I use multi and where I use single > message block??? The single-frame version can only send a short message (less than 128 bytes), whereas the multi-frame version allows up to 1600 bytes total. See the description of the "File Sharing Protocol". (Use Google to search for "INTEL Part Number 138446".) Over the last couple of years I have looked at generalising this code in Samba, and made some progress. (In a test implementation, I was able to use UNIX commands such as "wall" and "write" to produce WinPopup messages on the client PCs.) This required extracting, and altering, some code from smbclient, but this can be done in a re-useable way. If someone of the Samba Team is willing to facilitate this, I'll willingly submit the changes I made as a possible starting-point. -- : David LeeI.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/South Road: : Durham: : Phone: +44 191 374 2882 U.K. :
SMBClient - Messenger service
Hi. When I use "net send ..." command in windows to send a Winpopup message to other host, the SMB Command associate to this message is single block message (0xD0). To do this, it is only necessary sends one SMB "frame" to the other host. When I use SMBClient (samba), the SMB Command associate is multi-block message (fist it is necessary sends the start comand 0xD5, then a text comand 0xD7 and finally the end 0xD6). To do this, It is necessary sends 3 SMB "frames". Why SMBClient sends winpopup messages with multi-block message, and not single block message Where I use multi and where I use single message block??? Nuno Cardoso.
