[jcifs] jcifs-1.2.1 Exception
Michael B Allen
mba2000 at ioplex.com
Mon Jul 18 19:20:36 GMT 2005
I think we got a handle on this one. If you set jcifs.smb.client.laddr to the IP address of your network interface does it fix the problem?
Also what OS/version and Java version are using again?
On Fri, 8 Jul 2005 13:59:34 -0400
Michael B Allen <mba2000 at ioplex.com> wrote:
> > > java.net.SocketException: Invalid argument or cannot
> > > assign requested address
> > > at java.net.PlainSocketImpl.socketConnect(Native
> > > Method)
> > > at
> > > java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> > This is a low-level socket error and has nothing to do with jCIFS other
> > than the fact that 1.2.x now tries port 445 first and falls back to
> > 139. Try "smb://CORP;blah:blah@aserver:139/ashare$/". Do you have a
> > firewall?
> > This might have to do with a bug that was reported about what types of
> > socket exceptions are being caught in the transport layer that determine
> > when to "fall back" to trying 139. I would think this should be one of
> > them but if not it's a bug and should be fixed.
> > I will add this to my "Processing" folder for futher examination.
<skip bad diagnosis>
> --> Processing
More information about the jcifs