[jcifs] Transport1 timedout waiting for response to

Michael B Allen ioplex at gmail.com
Tue May 11 09:00:36 MDT 2010


Hi Mohan,

If you are getting an "timedout waiting for response" error, the most
common explanation would be that the server is simply not responding
within the timeout period. I suggest trying the following properties:

jcifs.smb.client.responseTimeout = 120
jcifs.smb.client.soTimeout = 140

Also, make sure you're using the latest version of JCIFS.

Mike

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

On Tue, May 11, 2010 at 10:32 AM, Mohan Radhakrishnan <mohanr at fss.co.in> wrote:
> Hi,
>
>      We require some ideas about this nagging error. The default time out
> period is 30 seconds ? This error is thrown just by monitoring a directory.
> Monitoring means just reading a directory and checking if a file is present
> or not.
>
>
>
> Should the response time out period be changed to fix this ?
>
>
>
>
>
> Thanks,
>
> Mohan
>
>
>
> The error was "jcifs.h: Transport1 timedout waiting for response to
> SmbComSessionSetupAndX[command=SMB_COM_SESSION_SETUP_ANDX,received=false,errorCode=0,flags=0x0018,flags2=0xC803,signSeq=0,tid=0,pid=45961,uid=16391,mid=15897,wordCount=12,byteCount=391,andxCommand=0xFF,andxOffset=0,snd_buf_size=16644,maxMpxCount=10,VC_NUMBER=1,sessionKey=0,lmHash.length=0,ntHash.length=0,capabilities=-2147479468,accountName=null,primaryDomain=null,NATIVE_OS=Windows
> 2003,NATIVE_LANMAN=jCIFS]
>
> jcifs.k: Transport1 timedout waiting for response to
> SmbComSessionSetupAndX[command=SMB_COM_SESSION_SETUP_ANDX,received=false,errorCode=0,flags=0x0018,flags2=0xC803,signSeq=0,tid=0,pid=45961,uid=16391,mid=15897,wordCount=12,byteCount=391,andxCommand=0xFF,andxOffset=0,snd_buf_size=16644,maxMpxCount=10,VC_NUMBER=1,sessionKey=0,lmHash.length=0,ntHash.length=0,capabilities=-2147479468,accountName=null,primaryDomain=null,NATIVE_OS=Windows


More information about the jCIFS mailing list