Comments on: Upon Further Review: Microsoft’s Document Connection Tool

By: trikks

trikks — Mon, 08 Nov 2010 22:37:39 +0000

Sorry for the late reply but Microsoft Document Connection doesn’t go through the IIS but directly to the SharePoint WSS Service. Which means its your Application URL that matters, in the best of worlds it should be the same as your host header.

Go to “Application Management” > “Web Application List” and check what is says below the URL.

In my case, i got a machine that have demo1.bendsoft.com as host header but only demo1 as URL. To fix this take that url, in my case simply demo1 and put it in your hosts file along with the IP, in example
demo1 192.168.10.201

Now you can connect with document connection by simply typing http://demo1 as the address.

Check more about this, and how to resolve it at http://www.bendsoft.com (in a few days from post date)

By: elf77

elf77 — Wed, 23 Dec 2009 22:53:46 +0000

I got it to work but it is slow and it sometimes hangs (especially with check-in). It takes a long time to initially load or refresh a folder file listing. I’m guessing it locally caches all the files in a folder. The larger the files, the longer it takes to display folder contents.

By: Bettiblue

Bettiblue — Sat, 05 Dec 2009 02:09:04 +0000

Niether have I. I cant connect to our WSS 3.0 site. I am a domain admin, my Mac is part of the domain. I have tried all kids of ways to connect to it, hostname, IP, my domain account, just my user name, domainusername, FQDN of domainusername, legacy netbois name of domainusername. Nothing works.

I am on WSS 3.0 SP1 and NOT SP2 because we have an apps on sharepoint that is not compatible. Maybe SP2 on sharepoint is needed.

By: Mark Burgess

Mark Burgess — Sat, 05 Dec 2009 01:36:01 +0000

I have never been able to get the thing to work. And received completely unhelpful technical support from Microsoft.