InfoPath Dev

A 401 would indicate a problem authenticating with the DBXL webservice not with the database. Is a hostheader defined for the site?  One would be to access http://server/qdabrawebservice/default.htm before you click Finish on the tabbed setup dialog.  Verify you can authenticate with the page and check if it shows Local Intranet ...

Adding records from the form would best be handled in a stored procedure.  That way you can enforce your validation on the server and respond with a descriptive error if the record already exists or you have other constraints not met (e.g. name contains invalid characters, etc...).  Here are two links on this ...

If you remote desktop to the SharePoint server and open IE, are you able to browse to these SharePoint sites?

SharePoint Central Administration must be configured correctly for alternate access mappings or server-side communication can break when accessed from the external url.  Alternate access mappings let SharePoint know that a url, say extranet.yourdomain.com, is known internally as http://servername and it will make the calls using the ...

Do you have alternate access mappings configured correctly for the extranet site?

Are you using the standalone Qdabra AD Webservice or the AD webservice as part of Qdabra DBXL?

I don't think getting InfoPath to authenticate in that manner is possible without interceding like you are currently doing. But there is a simpler method.  When publishing, use 'To a network location' and specify a local folder, but in the step where it asks 'If all users can access the location that you ...

This is about as complex a structure as AD can get.  I can't guarantee it will work for this specific case, but it will require at least using the Global Catalog.  The syntax for the LDAP connection string would be GC://domain or GC://servername. Give this a try and see if it works for this situation.

Although they aren't all shown in DAT for DBXL v2.3, the following should all work in mapping: DBXL::Link DBXL::DocId DBXL::DocType DBXL::RefId DBXL::VerNo DBXL::CreatedBy DBXL::DateCreated DBXL::ModifiedBy DBXL::DateModified  

What account are you using for the DBXL application pool?  The default is Network Service, which if the machine is joined with the domain, should have permission to access AD. When you rant setup, did it prepopulate the LDAP string or did you have to edit it yourself?