[jcifs] Re: NoRouteToHostException?

Levi Purvis jcifs at purvis.ws
Tue Oct 4 19:22:54 GMT 2005

Just guessing, but a firewall in the network path somewhere may be set to
just drop packets on port 445 rather than refuse connections -- this is
generally regarded as more secure. If this is the case, then IMO the JCIFS
code should expect it and still try the 139 fall-back.

On 10/4/05, Michael B Allen <mba2000 at ioplex.com> wrote:
> On Tue, 4 Oct 2005 11:19:59 +0000 (UTC)
> Malte <haendehochdasisein at mailueberfall.de> wrote:
> > I'm just stupid. I added port 139 to the URL and got it running.
> Actually JCIFS tries to connect to port 445 and then if that fails with
> a ConnectException it automatically tries port 139. But unfortunately,
> for some reason in your environment, trying port 445 causes a
> NoRouteToHostException and therefore the client does not fallback to
> trying port 139.
> Mike
-------------- next part --------------
HTML attachment scrubbed and removed

More information about the jcifs mailing list