[jcifs] Using port 445 instead of 139 with NtlmHttpFilter
Michael B Allen
mba2000 at ioplex.com
Tue Jul 27 22:54:10 GMT 2004
m_stanski at poczta.onet.pl said:
>> The port 445 work was not completed. It was a reasonably complicated
>> operation to get both 139 and 445 to work together smoothly so I didn't
>> pursue it too hard. There's no ETA.
> Thanks for help.
> I have additional two questions:
> 1. How long can it take to make jCifs work with 445 port. I'm asking
> because I consider making it myself and I would like to estimate how
> difficult it is. I expect it is no easy to estimate, but is it a matter of
> hours, days, weeks, or months ? How do you think ?
The problem is getting 445 *and* 139 working *and* some alternate port
specified in the SMB URL and have them all do the right thing whatever
However, if you just want 445 and don't care about 139 I believe the
communication is very similar if not simpler. Meaning, you could take a
capture of port 445, take a capture of the same thing on port 139 and then
look at the difference. I think you'll find that you can change
jcifs.smb.Handler default port to 445 and then just chop out the NetBIOS
session establishment. What's left should be very close.
> 2. Do you know any other product or library which I can use to autenticate
> IE users against NT Domain using NTLM with Java. I know solutions with IIS
> or Apache as supporting servers, but maybe there is an easier way to do
> that ?
I don't know for sure but WedgeTail might do the trick. Also the Squid
proxy might do the trick but of course you would need to set that up on
More information about the jcifs