SV: RE: [jcifs] About the long crawling time again...

[Allen, Michael B (RSCH)]

> -----Original Message-----
> From:	torjo845 at student.liu.se [SMTP:torjo845 at student.liu.se]
> Sent:	Wednesday, August 08, 2001 5:29 PM
> To:	Allen, Michael B (RSCH); jcifs at samba.org
> Subject:	Re: RE: SV: RE: [jcifs] About the long crawling time again...
> 
> Ok, ran some more tests with the following results:
> 
> astmatix <67> nmblookup A828
> Added interface ip=130.236.186.15 bcast=130.236.186.255 nmask=255.255.255.0
> Sending queries to 130.236.186.255
> name_query failed to find name A828
> 
	Well, nmblookup will work because thats just doing a name lookup. At least it will if you query wins with $ nmblookup -U 130.236.230.9 -R.

> astmatix <70> java -Djcifs.wins=130.236.230.9 Test A828
> Host exists.
> 
	Sure. Again, this is just doing a host lookup which comes from WINS. If you call exists() on a workgroup name or server name then the actuall server connect may not work because the host may
be down. If exists() returns true when querying a share or file then you should definiately not get a connect error  though (I beleive this was the context discussed before?).

> astmatix <71> telnet 130.236.218.28 139
> Trying 130.236.218.28... (had to ctrl+c here cause nothing happened)
> 
	Yeah. That's failing to connect. Is this one of the IPs of a host that hung jCIFS?

> astmatix <72> ping A828
> ping: unknown host A828
> 
	This will try to do a DNS query on that name and sent it ICMP packets. It doesn't tell you a lot about a NetBIOS network really.

> astmatix <74> ping 130.236.218.28
> no answer from 130.236.218.28
> (got the IP from the log when I ran my Test program)
> 
	Same.

	If you have nmblookup then you probably have smbclient? If you encounter a "lame" host try using smbclient on it. I think we've come full circle though and we're back to my original assumtion
which is that you're trying to connect to a host that is not alive. The problem is that you're underlying network implementation is waiting a long while to report connection failure which is strange.
That could be a bug in JDK1.3.

	Mike


> ----- Original Message -----
> From: "Allen, Michael B (RSCH)" <Michael_B_Allen at ml.com>
> Date: Wednesday, August 8, 2001 10:30 pm
> Subject: RE: SV: RE: [jcifs] About the long crawling time again...
> 
> > I don't know Torgny. You really got me with this one. It 
> > successfully resolves
> > the name as a file service but trying to connect to port 139 at 
> > that IP looks
> > like it just makes the socket connect hang. I think an important 
> > diagnostichere would be to try and telnet to one of these "lame" 
> > hosts on port 139.
> > You're not going to actually "log in" of course but it will 
> > confirm wheather or
> > not the host is indeed living.
> > 
> > For example a successfull connect would give you a "Connected to"
> > message like:
> > 
> > $ telnet 130.236.186.15 139
> > Trying 130.236.186.15...
> > Connected to 130.236.186.15.
> > Escape character is '^]'.
> > 
> > whereas failure will result in the familar "No route to host" like:
> > 
> > [miallen at prodlinux miallen]$ telnet 130.236.186.15 139  
> > Trying 130.236.186.15...
> > telnet: Unable to connect to remote host: No route to host
> > 
> > Can you try it?
> > 
> > Thanks,
> > Mike
> > 
> > > -----Original Message-----
> > > From:	torjo845 at student.liu.se [SMTP:torjo845 at student.liu.se]
> > > 
> > > Here we go. I've attached the log to this mail.
> > > It took me about 20-25 minutes to get this exception...
> > > 
> > > > > > > torgny at p13:~/java$ java -Djcifs.properties=LinGet.prp
> > > > > > > ThreadedSmbCrawler smb://750 1 1
> > > > > > > Aug 3 08:50:11.280 - SmbFile exception
> > > > > > > java.net.NoRouteToHostException: Connection timed out
> > > > > >
> > > > > >
> > > > 
> > > >  << File: log.txt >> 
> > 
> > 
> > 
>