[jcifs] SmbNamedPipe

[Michael B. Allen]

Looks better. You're only closing one of the pipes though. You open
two. I'll look at it more closely and try to have a proper fix this
weekend.

However, these pcaps have other stuff in them that I don't think is
jCIFS. There are major SYN, ACK, PSH, ACK packets flying all over the
place. The host you're running jCIFS from is trying to connect to port
9700 on host ESTSPECHT but never really establises a TCP session. Try
catching dead air with no jCIFS at all and see if the background noise
remains. What are you running on 9700? I think you can get that info
from netstat -a. Might be a virus of some kind.


On Thu, 21 Nov 2002 10:09:20 +0100
"Specht, Uwe" <Uwe.Specht at est.fujitsu.com> wrote:

> Hi,
> I changed the classes and have 2 pcap files. One with actively calling the
> close method of the Stream (after using the Stream) one without. I think
> ther is one jcifs timeout inbetween in any case. But what happens if a
> timeout occurs? By the way it looks much better now (Some closing action is
> done on serverside) but still the pipe is not closed properly (In my
> tracefile on the other side of the pipe it says something like 
> Error: Connection reset by peer)
> 
> thy for your help
> 
> -----Original Message-----
> From: Michael B. Allen [mailto:miallen at eskimo.com]
> Sent: Mittwoch, 20. November 2002 21:13
> To: Specht, Uwe
> Cc: jcifs at samba.org
> Subject: Re: [jcifs] SmbNamedPipe
> 
> 
> On Wed, 20 Nov 2002 11:46:47 +0100
> "Specht, Uwe" <Uwe.Specht at est.fujitsu.com> wrote:
> 
> > Hi,
> > I have to ethereal files as attachments. one is the windows file which
> just
> > closes the pipe properly.
> > For jcifs my file is much bigger as I have to open a connection do
> something
> > and after doing nothing the connection is closed
> > sorry that the files come so late but I had to find a windows test case to
> > do this.
> > I hope this helps.
> 
> There's only 3 frames in Winclient.pcap but I think I know
> what the problem is. The TransactNamedPipeInputStream and
> TransactNamedPipeOutputStream close() methods are empty! Put a
> 
>   pipe.close();
> 
> in them and try calling the pipe stream close() methods. I will test and
> fix this in 0.6.8 and 0.7.0b9 too but it would be nice if you could try
> it and send me another pcap like Jcifsclient.pcap.
> 
> 
> > 
> > cu US
> > 
> > -----Original Message-----
> > From: Michael B. Allen [mailto:miallen at eskimo.com]
> > Sent: Samstag, 16. November 2002 05:54
> > To: Specht, Uwe
> > Cc: jcifs at lists.samba.org
> > Subject: Re: [jcifs] SmbNamedPipe
> > 
> > 
> > On Fri, 15 Nov 2002 14:00:07 +0100
> > "Specht, Uwe" <Uwe.Specht at est.fujitsu.com> wrote:
> > 
> > > Hi,
> > > is there any method to close a SmbNamedPipe.I already close the Input
> and
> > > Output stream, but the connection is not closed properly. (compared to a
> > > windows close of that pipe). I think there should be something like this
> > or
> > > am I wrong?
> > 
> > Well if you mean disconnect, no. There is no explicit way to
> > disconnect. It will disconnect after jcifs.smb.client.soTimeout. If you
> > mean that calling close() on the stream does not do the same thing as
> > Windows then I'll have to take a packet capture. But that's not easy for
> > me to do. If you have ethereal or netmon it will expedite the process
> > quite a bit.
> 
> -- 
> A  program should be written to model the concepts of the task it
> performs rather than the physical world or a process because this
> maximizes  the  potential  for it to be applied to tasks that are
> conceptually  similar and, more important, to tasks that have not
> yet been conceived. 
> 
> 


-- 
A  program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes  the  potential  for it to be applied to tasks that are
conceptually  similar and, more important, to tasks that have not
yet been conceived.