[jcifs] jcifs-1.2.1 Exception

Michael B Allen mba2000 at ioplex.com
Fri Jul 8 17:59:34 GMT 2005

On Fri, 8 Jul 2005 13:42:39 -0400
Michael B Allen <mba2000 at ioplex.com> wrote:

> > SmbFile("smb://CORP;blah:blah@aserver/ashare$/");
> <snip>
> > 
> > jcifs.smb.SmbException: 
> > jcifs.util.transport.TransportException
> > 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.

Actually this does look like it's a bug that maybe can be fixed:


Meaning if it fails to connect to 445 I can retry with 139. As it is a SocketException means total failure. I think we can do better than that.

--> Processing


More information about the jcifs mailing list