[linux-cifs-client] use non-zero vcnumbers patch
Steve French
smfrench at gmail.com
Wed Feb 4 03:58:18 GMT 2009
In the situation you describe - I thought that the server could
recognize that they are distinct sockets, and source ports, but
perhaps with Win9x didn't
On Tue, Feb 3, 2009 at 9:19 PM, Christopher R. Hertel <crh at ubiqx.mn.org> wrote:
> Steve French wrote:
> :
>> I also remember the old situation that Chris H. mentions about vc
>> numbers and NATs and the nasty behavior change it required.
>
> NATs, and multiple connections from a single machine. Say someone has (for
> example) an smbclient session open and then mounts a share using CIFS. If
> CIFS sends VC=0 the smbclient session may be dropped.
>
> As I recall (haven't tested lately) newer Windows servers no longer drop
> existing connections if a new VC=0 connection comes in. If that is the
> case, then there's no point in sending VC=0 anyway.
>
> Again, I'm going from memory so I could be wrong here, but I think jCIFS
> sends VC=1 for all connections and doesn't have a problem. Two TCP
> connections from the same client with the same VC number would (assuming the
> old OS/2 idea of a VC is supported) be seen as a single virtual circuit over
> two physical circuits.
>
> Chris -)-----
>
> --
> "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
> Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel
> jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq.
> ubiqx Team -- http://www.ubiqx.org/ -)----- crh at ubiqx.mn.org
> OnLineBook -- http://ubiqx.org/cifs/ -)----- crh at ubiqx.org
>
--
Thanks,
Steve
More information about the linux-cifs-client
mailing list