[jcifs] java.io.IOException: no andx command supplied with re sponse

[Jerry Jalenak]

According to the API documentation - 

	Notice all jCIFS client properties have several dot '.' separated
components whereas
	I have chosen only to specify the last label in the examples above.
This is perfectly legal
	(except with -Dfull.property.name=value VM parameters). The
following: 

		jcifs.netbios.wins
		jcifs.wins
		wins

	are all identical. The more lengthy versions need only be used to
avoid namespace conflicts. 
	See the jcifs.util.PropertiesTree class for more information.


Based on this doc, I *assumed* that "jcifs.smb.client.useBatching" and
"useBatching" would be the same.  I'll modify the setProperty and try
it.....

Jerry Jalenak
Development Manager, Web Publishing
LabOne, Inc.
10101 Renner Blvd.
Lenexa, KS  66219
(913) 577-1496

jerry.jalenak at labone.com


> -----Original Message-----
> From: eglass1 at comcast.net [mailto:eglass1 at comcast.net]
> Sent: Tuesday, May 04, 2004 1:15 PM
> To: Jerry Jalenak
> Cc: 'jcifs at lists.samba.org'
> Subject: Re: [jcifs] java.io.IOException: no andx command 
> supplied with
> response
> 
> 
> 
> 
> > I've googled for an answer, and found a couple of hits that 
> suggested
> > setting the "useBatching" property to "false"; I've done 
> this (I think) with
> > the following statement:
> > 
> > 	jcifs.Config.setProperty("useBatching", "false");
> > 
> 
> It would be:
> 
>     jcifs.Config.setProperty("jcifs.smb.client.useBatching", "false");
> 
> but I can't say whether that will fix the problem you're 
> seeing or not.
> 
> 
> Eric
> 

This transmission (and any information attached to it) may be confidential and
is intended solely for the use of the individual or entity to which it is
addressed. If you are not the intended recipient or the person responsible for
delivering the transmission to the intended recipient, be advised that you
have received this transmission in error and that any use, dissemination,
forwarding, printing, or copying of this information is strictly prohibited.
If you have received this transmission in error, please immediately notify
LabOne at the following email address: securityincidentreporting at labone.com