Hi Derek,

Glad you were able to find your way through the maze.

1) I assume the problems you have are related to mixed 32bit and 64bit for those third party add-ons, and whenever you want to explore that further, we are here to help.

2) The Kerberos / NTLM authentication can be hard to get right, although they are not all that complicated when you get the hang of it. Although I am far from having all the details of your setup, then I would guess that you have a browser that connects to your VWG application that uses webservices calls to your sharepoint webservices. If that is the case, you have a typical 3-tier scenario, where  the authentication token will have to be able to "travel" from the browser, through the VWG application to the SharePoint webservices, and that in turn requires Kerberos and correct setup of Kerberos. This means registering the correct SPNs and making sure they are unique, as well as adjusting some attributes within Active Directory on the account (user or computer) running services involved, so they will be allowed to pass-through the token to the next service. All in all, fairly complicated at first, but quite doable, but may require some adjustments to accounts running the application pools and possibly some adjustments to the ports used etc.

To get around having to use Kerberos, you could have your VWG application authenticate to the sharepoint webservices with a specific username, instead of passing through the token from the browser. That would mean you didn't have Kerberos to worry about as you would then only have 2-tiers in the setup, the third tier (sharepoint) having fixed user authentication.

I hope you enjoyed the hot tub.

Palli