[jcifs] JCIFS 1.3.8 java.net.SocketException: Connection timed out:could be due to invalid address

[Michael B Allen]

Hi Ivan,

Please respond only through the mailing list.

On Thu, Apr 1, 2010 at 10:59 AM, Ivan Petrov <lordjohnp at gmail.com> wrote:
> Hi Mike,
>
> I don't get your point. You may be didn't understand me well.
> By local user I ment user created on windows share. This way the
> thisng are running faster than when I use a domain user.

I understood that.

> In both cases I receive the connection time ot error message, with
> local user 1 or 2 error messages, with domain user usually atleast 7
> or more error messages, but it looks like that this is not true
> because in both cases I still receive the content of the folder I'm
> browsing.
> The uncomon responce thing - I didn't get this.

Because the server is AIX, you're seeing an unusual error condition.
In particular the CIFS command is timing out. I don't recall ever
seeing Windows exhibit that behavior.

But I could not even begin to speculate as to what the problem is
because I do not know what the server is or have a valid packet
capture. A wild guess is that the AIX side is just misconfigured.

> Capture is valid. I can opent it with WireShark. If you ment something
> else please explain.

The frames are truncated. That will happen if you run tcpdump without
-s 0 for example.

Mike

> 2010/4/1 Michael B Allen <ioplex at gmail.com>:
>> Hi Ivan,
>>
>> I have a feeling this has little or nothing to do with JCIFS if it
>> works with a local user. You're just getting an uncommon response
>> because the server is AIX.
>>
>> Also, your capture was not valid.
>>
>> Mike
>>
>> On Fri, Mar 26, 2010 at 2:57 AM, Ivan Petrov <lordjohnp at gmail.com> wrote:
>>> Hi,
>>>
>>> I’m using jCIFS 1.3.8 to access windows share from UNIX/AIX server.
>>> LDAP user is used to access windows share.
>>> I’m constantly receiving following error:
>>>
>>> java.net.SocketException: Connection timed out:could be due to invalid address#
>>>        at java.net.PlainSocketImpl.socketConnect(Native Method)#
>>>        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:355)#
>>>        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:220)#
>>>        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:207)#
>>>        at java.net.Socket.connect(Socket.java:479)#
>>>        at java.net.Socket.connect(Socket.java:429)#
>>>        at java.net.Socket.<init>(Socket.java:336)#
>>>        at java.net.Socket.<init>(Socket.java:152)#
>>>        at jcifs.smb.SmbTransport.negotiate(SmbTransport.java:249)#
>>>        at jcifs.smb.SmbTransport.doConnect(SmbTransport.java:306)#
>>>        at jcifs.util.transport.Transport.run(Transport.java:240)#
>>>        at java.lang.Thread.run(Thread.java:770)#
>>>
>>> but finally I’m still receiving folder content. The problem is that
>>> just a simple browsing takes  5-7 minutes just to enter a folder with
>>> 1 file in it.
>>> If I’m using local windows user for this access everything works ok.
>>> I’ve made a thread dumps and they show that 17 to 19 jcifs.transport2
>>> threads are locked by one jcifs.transport2 thread and beside that
>>> there is another jcifs.trasport1 thread that is working ok.
>>> I’ve also made a network dumps and they are attached to the mail.
>>>
>>> With jCIFS 1.2.9 the same scenario worked ok.
>>>
>>> Best regards,
>>> Ivan Petrov Petrov
>>>
>>
>>
>>
>> --
>> Michael B Allen
>> Java Active Directory Integration
>> http://www.ioplex.com/
>>
>



-- 
Michael B Allen
Java Active Directory Integration
http://www.ioplex.com/