Document Connection- Cannot connect to sharepoint site

[jaim...@officeformac.com]

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel

Im trying to connect but get an error "The connection failed"

I have tried both user/pass, basic auth, and kerberos.

Could it be the port?

The url takes the form: <http://oursharepointserver.outdomain.org:5280/sitename/default.aspx>

[William Smith [MVP]]

jaim...@officeformac.com wrote:

> Im trying to connect but get an error "The connection failed"
>
> I have tried both user/pass, basic auth, and kerberos.
>
> Could it be the port?
>
> The url takes the form:
> <http://oursharepointserver.outdomain.org:5280/sitename/default.aspx>

Shorten the URL to the site address alone. Try
<http://oursharepointserver.outdomain.org:5280/sitename/>

Hope this helps!

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

[kang...@officeformac.com]

I am having the same problem of not being able to connect to my sharepoint server through Document Connection. For the address, user name, and passworld, I typed into Document Connection exactly what I do when I access my sharepoint server through web access. Yet, I am prompted with Connection Failed in Document Connection when I can log in through web access just fine. Any suggestions?

[jaim...@officeformac.com]

shortening the url did not help. hmmm....

[William Smith [MVP]]

jaim...@officeformac.com wrote:

> shortening the url did not help. hmmm....

Are you using your server's fully qualified domain name such as
"server.example.com" and not just "server"?

[jaim...@officeformac.com]

Hi William,

I am using the fully qualified domain name.
Could it the port?

Jaime

[William Smith [MVP]]

jaim...@officeformac.com wrote:

> I am using the fully qualified domain name. Could it the port?

Others here have reported that this same problem is caused by SharePoint
version. Document Connection requires SharePoint Services 3.0. What
version is your server running?

[gor...@officeformac.com]

I am having the same problems. Document Connection does not work with either SP2 nor with MOSS3.

[gor...@officeformac.com]

Here is the dump of the last communication to the MOSS 3 server:

POST /_vti_inf.html HTTP/1.1
Host: portal.rapidsoft.ru
From: 192.168.62.129
User-Agent: Microsoft Office/12.2.0 (Macintosh 10.5.7, Microsoft Document Connection 12.2.0; Pro)
Accept: */*
Accept-Language: en
Cookie: WSS_KeepSessionAuthenticated=80
Content-Length: 0
Connection: Keep-Alive

HTTP/1.1 200 OK
Date: Thu, 23 Jul 2009 09:40:10 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
MicrosoftSharePointTeamServices: 12.0.0.6219
Exires: Wed, 08 Jul 2009 09:40:10 GMT
Cache-Control: private,max-age=0
Content-Length: 246
Public-Extension: <http://schemas.microsoft.com/repl-2>
Set-Cookie: WSS_KeepSessionAuthenticated=80; path=/

<!-- FrontPage Configuration Information
FPVersion="12.0.0.000"
FPShtmlScriptUrl="_vti_bin/shtml.dll/_vti_rpc"
FPAuthorScriptUrl="_vti_bin/_vti_aut/author.dll"
FPAdminScriptUrl="_vti_bin/_vti_adm/admin.dll"
TPScriptUrl="_vti_bin/owssvr.dll"
-->

[jfma...@officeformac.com]

I've been wondering if others had this problem.

Same here. I'm running SP Services version 3 on an alternative port and having the same issues. Connection Failed. Log in is OK via browser.

One thing I noted is that when I attempt a connect via Document Connection there is nothing in the server logs. But something must be going on between the app and the server because it says "you do not have permission to connect" when I try a bogus ID.

[jaim...@officeformac.com]

We're using 3.0.

Thanks,
Jaime

> jaim...@officeformac.com wrote:
>
> > I am using the fully qualified domain name. Could it the port?
>
> Others here have reported that this same problem is caused by SharePoint
> version. Document Connection requires SharePoint Services 3.0. What
> version is your server running?
>
> --
>
> bill
>
> Entourage Help Page

> Entourage Help Blog
> YouTalk
> Twitter: follow
>

[Web...@officeformac.com]

I am able to connect to http, but https sites are not working. Can someone verify SSL is an option.
Thx

[Jim Gordon MVP]

Also - Document Connection won't connect to SharePoint if you are using
Home and Student Edition of Office.

-Jim

--
Jim Gordon
Mac MVP

http://www.agentjim.com/MVP/welcome.htm

[jfma...@officeformac.com]

Using Special Media Edition here. Not Home or Student.

[jaim...@officeformac.com]

no home and student either. we use exchange here.

[phil]

On Jul 29, 9:22 am, jaime...@officeformac.com wrote:
> no home and student either. we use exchange here.

I'm having the exact same issue....nothing helps.

[Kirk Engelmeier]

Is it possible to create a second binding for the SharePoint server to the
default port 80?
I know this may not be feasible for a number of reasons, but if possible it
might be worth a try to help isolate the issue.
-Kirk

--
This posting is provided "AS IS" with no warranties, and confers no rights.

<jaim...@officeformac.com> wrote in message
news:59b78...@webcrossing.caR9absDaxw...

[gu...@officeformac.com]

I'm going to join in because we're seeing exactly the same problem in our office - and we are running on port 80.

Here is some information:
- Our server is Windows Small Business Server 2008 (x64 version)
- It is running SharePoint Services 3.0
- To access SharePoint from a browser we can use <http://companyweb> BUT other URLs such as <http://companyweb.name.local> OR <http://server> (the actual hostname of the server) do not work... they bring up the standard IIS7 homepage
- Microsoft Document Connection shows the error message "The connection failed." when we try to connect to <http://companyweb>
- It appears that Document Connection is able to connect to Sharepoint because "The connection failed." is only shown when we type the correct password. If we use an invalid username or password we get the message "You do not have permission to connect." But we cannot get past the "The connection failed." message to actually use Document Connection

[gu...@officeformac.com]

Just in case it helps, here is a dump of the HTTP traffic during a failed login using Microsoft Document Connection. "The connection failed." is displayed after this.

Note that I have placed the NTLM authentication lines with [...] for security reasons... the rest is unaltered.

* *************************************************

OPTIONS / HTTP/1.1
Host: companyweb
From: 192.168.83.64

User-Agent: Microsoft Office/12.2.0 (Macintosh 10.5.7, Microsoft Document Connection 12.2.0; Pro)
Accept: */*
Accept-Language: en

Translate: f
Content-Length: 0
Connection: Keep-Alive

HTTP/1.1 401 Unauthorized
Server: Microsoft-IIS/7.0
WWW-Authenticate: Negotiate
WWW-Authenticate: NTLM
X-Powered-By: ASP.NET
Date: Wed, 05 Aug 2009 08:20:46 GMT
Content-Length: 0

OPTIONS / HTTP/1.1
Host: companyweb
From: 192.168.83.64

User-Agent: Microsoft Office/12.2.0 (Macintosh 10.5.7, Microsoft Document Connection 12.2.0; Pro)
Accept: */*
Accept-Language: en

Translate: f
Content-Length: 0
Connection: Keep-Alive
Authorization: NTLM [...]

HTTP/1.1 401 Unauthorized
Server: Microsoft-IIS/7.0
WWW-Authenticate: NTLM [...]
WWW-Authenticate: Negotiate
X-Powered-By: ASP.NET
Date: Wed, 05 Aug 2009 08:20:46 GMT
Content-Length: 0

OPTIONS / HTTP/1.1
Host: companyweb
From: 192.168.83.64

User-Agent: Microsoft Office/12.2.0 (Macintosh 10.5.7, Microsoft Document Connection 12.2.0; Pro)
Accept: */*
Accept-Language: en

Translate: f
Content-Length: 0
Connection: Keep-Alive
Authorization: NTLM [...]

HTTP/1.1 200 OK
Cache-Control: private,max-age=0
Allow: GET, POST, OPTIONS, HEAD, MKCOL, PUT, PROPFIND, PROPPATCH, DELETE, MOVE, COPY, GETLIB, LOCK, UNLOCK
Content-Length: 0
Accept-Ranges: none
Server: Microsoft-IIS/7.0
DAV: 1,2
Exires: Tue, 21 Jul 2009 08:20:47 GMT

Public-Extension: <http://schemas.microsoft.com/repl-2>
Set-Cookie: WSS_KeepSessionAuthenticated=80; path=/

X-Powered-By: ASP.NET
Date: Wed, 05 Aug 2009 08:20:46 GMT

PROPFIND / HTTP/1.1
Host: companyweb
From: 192.168.83.64

User-Agent: Microsoft Office/12.2.0 (Macintosh 10.5.7, Microsoft Document Connection 12.2.0; Pro)
Accept: */*
Accept-Language: en

Translate: f
Brief: t
Depth: 0
Content-Type: text/xml; charset=utf-8
Cookie: WSS_KeepSessionAuthenticated=80
Content-Length: 181
Connection: Keep-Alive

<?xml version="1.0" encoding="utf-8"?><D:propfind xmlns:D="DAV:"><D:prop><D:resourcetype/><D:getetag/><D:getcontentlength/><D:lockdiscovery/><D:supportedlock/></D:prop></D:propfind>

HTTP/1.1 207 MULTI-STATUS
Cache-Control: no-cache
Content-Length: 646
Content-Type: text/xml
Server: Microsoft-IIS/7.0

Public-Extension: <http://schemas.microsoft.com/repl-2>
Set-Cookie: WSS_KeepSessionAuthenticated=80; path=/

X-Powered-By: ASP.NET
Date: Wed, 05 Aug 2009 08:20:46 GMT

<?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:" xmlns:Office="urn:schemas-microsoft-com:office:office" xmlns:Repl="http://schemas.microsoft.com/repl/ <http://schemas.microsoft.com/repl/>" xmlns:Z="urn:schemas-microsoft-com:">
<D:response><D:href>http://companyweb/</D <http://companyweb/</D>:href><D:propstat><D:prop><D:resourcetype><D:collection/></D:resourcetype><D:getetag>&quot;{73F92E5D-009D-48F0-8B40-3162E93DD709},0&quot;</D:getetag><D:lockdiscovery/><D:supportedlock/></D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
<D:propstat>
<D:prop>
<D:getcontentlength/></D:prop>
<D:status>HTTP/1.1 404 Not Found</D:status>
</D:propstat></D:response>
</D:multistatus>

POST /_vti_inf.html HTTP/1.1
Host: companyweb
From: 192.168.83.64

User-Agent: Microsoft Office/12.2.0 (Macintosh 10.5.7, Microsoft Document Connection 12.2.0; Pro)
Accept: */*
Accept-Language: en
Cookie: WSS_KeepSessionAuthenticated=80
Content-Length: 0
Connection: Keep-Alive

HTTP/1.1 404

[gu...@officeformac.com]

HTTP/1.1 404 NOT FOUND
Cache-Control: private,max-age=0
Content-Length: 0
Server: Microsoft-IIS/7.0

[ol...@officeformac.com]

We're having exactly the same problem, the same config and the same HTTPDump!

[ol...@officeformac.com]

Is there are FPSE required to access?
The "404 Not Found" message on "_vti_inf.html" is seemingly needed to start the WEBDAV service. ( See Michael Shavnev's post at <https://issues.alfresco.com/jira/browse/ETHREEOH-920> )...

[ol...@officeformac.com]

Document Connection on SBS 2008

After few hours of trying now I'm one step further!

1. Error HTTP/1.1 404

HTTP/1.1 404 means that no "_vti_inf.html" file exists.
Just create it!

File: "_vti_inf.html" contains:

<!-- FrontPage Configuration Information
FPVersion="12.0.0.000"
FPShtmlScriptUrl="_vti_bin/shtml.dll/_vti_rpc"
FPAuthorScriptUrl="_vti_bin/_vti_aut/author.dll"
FPAdminScriptUrl="_vti_bin/_vti_adm/admin.dll"
TPScriptUrl="_vti_bin/owssvr.dll"
-->

Now save this file on the �SBS SharePoint" physical location (on my SBS 2008:
�C:\Programm Files\Windows Small Business Server\Bin\WebApp\InternalWebSite")

2. Error HTTP/1.1 405 (Method Not Allowed)

Go to "Server-Manager"-"Internet Information Services - Manager".
Expand the tree to "COMPUTERNAME"-"Sites"-"SBS SharePoint".
Double click on "Handler Mappings" icon, select the "Add Script Map" button.
Type "*.html" (without quotes) in the "Request Path� box.
underneath this, insert in �Executable� �c:\windows\System32\inetsrv\asp.dll�" (without quotes) and find an apposite name.
Select the "Request Restrictions" button, on tab �Mapping� checking the checkbox �Invoke handler only if request is mapped to:� and mark radiobutton �File.
Go to tab �Verbs� and insert �POST� in the textfield.
On �Access� tab check the Script radiobutton an confirm that all with clicks of the �ok� Button.

After a IIS reboot I can now access �companyweb� with �Document Connection�,but there are several problems with write access.

I CANNOT TAKE LIABILITY FOR ANY PROBLEMS RESULTING FROM THIS CHANGE!!!
THE EFFECTS HAVE NOT YET BEEN TESTED!

[gu...@officeformac.com]

Good news � I found the solution!

SharePoint needs to have its 'Client Integration' feature turned on. Log in to your SharePoint Central Administration site as an administrator. Navigate to Central Administration > Application Management > Authentication Providers then click the appropriate zone (in my case, 'Default'). If 'Enable Client Integration' is set to No, switch it to Yes and click Save.

In my case this immediately fixed up the problem. I can now use Microsoft Document Connection to view, create and edit documents in our SharePoint sites.

[ol...@officeformac.com]

OK! The simple way is the best! A little more documentationfrom MS would have been helpful...

[jaim...@officeformac.com]

Gutch's solution solved my issue in a round about way. While in the authentication management area, i noted the url as <http://sharepointserver_nonfqdn:5280/>

When I used the non fqdn, it worked.

[mike...@officeformac.com]

I've tried all of the above and still no luck! I have two sites (two IP's) pointing to the same data one is set for forms authentication and the other is windows. The forms has a FQDN the windows just has an IP. The system is NOT running AD. When I try to access the windows based through the IP I get all the same errors above. Any thoughts?

[Kirk Engelmeier]

Hi Mike,
I tried connecting via IP address and it did not work for me either, I'll
keep trying and let you know if I get it to work. Unfortunately there is no
support for form based authentication in the Document Connection.

I imagine you have but I need to ask, have you tried using the machine name
instead of the IP for the windows authentication?

Thanks,
-Kirk

--
This posting is provided "AS IS" with no warranties, and confers no rights.

Please remove "NoSPAM" from my return email address for mail to reach my
Inbox.
--------------------------------------------------------------------------------

<mike...@officeformac.com> wrote in message
news:59b78...@webcrossing.caR9absDaxw...

[Jim Gordon MVP]

mike...@officeformac.com wrote:
> I've tried all of the above and still no luck! I have two sites (two IP's) pointing to the same data one is set for forms authentication and the other is windows. The forms has a FQDN the windows just has an IP. The system is NOT running AD. When I try to access the windows based through the IP I get all the same errors above. Any thoughts?

Hi,

Does it make any difference if you add the domain to your search domains
in the Network control panel?

-Jim

--
Jim Gordon
Mac MVP

Co-author of Office 2008 for Mac All-in-One For Dummies
http://tinyurl.com/Office-2008-for-Dummies

[Kirk Engelmeier]

One user reported that adding the IP address to the bypass proxy list in the
Network Preferences has worked (though this has not worked for me).
-Kirk

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please remove "NoSPAM" from my return email address for mail to reach my
Inbox.
--------------------------------------------------------------------------------

<mike...@officeformac.com> wrote in message
news:59b78...@webcrossing.caR9absDaxw...

[mike...@officeformac.com]

No it didn't make any difference. I also created a fqdn for (machinename).domain.com and it still did not work. I can't just access the machine via machine name because it's not local. I also have been unsuccessful creating a VPN to the machine if that helps...

> mike...@officeformac.com wrote:
> > I've tried all of the above and still no luck! I have two sites (two IP's) pointing to the same data one is set for forms authentication and the other is windows. The forms has a FQDN the windows just has an IP. The system is NOT running AD. When I try to access the windows based through the IP I get all the same errors above. Any thoughts?
>

[mike...@officeformac.com]

I was able to mount the sharepoint via finder when I have a VPN connection to the server, however I can't see any documents. I can only connect via webdav when my osx machine user name and password are the SAME as an account on Server 2008. Document connection still does not work when connected to the vpn. Any ideas?

[mike...@officeformac.com]

OK now something really weird is happening. After I connected with the above settings, now I can connect with "my" account on the win2008 server and see the sharepoint document library - without a VPN connection! I still cannot connect via document connection.

[mike...@officeformac.com]

New.. improved.. doesn't work again :(

My two days of bliss has ended. I had to restart my mac yesterday and now while I can connect to the webdav share on the sharepoint server, now I cannot see anything. Furthermore it won't let me eject the volume because it says it's in use, but I have no connections to it. When I run DF from terminal it reports:

df: negative filesystem block count/size from fs /Volumes/(my ip removed)
df: negative filesystem block count/size from fs /Volumes/(my ip removed)
df: negative filesystem block count/size from fs /Volumes/(my ip removed)
df: negative filesystem block count/size from fs /Volumes/(my ip removed)
Filesystem 512-blocks Used Available Capacity Mounted on
/dev/disk0s2 624470624 568413816 55544808 92% /
devfs 238 238 0 100% /dev
fdesc 2 2 0 100% /dev
map -hosts 0 0 0 100% /net
map auto_home 0 0 0 100% /home
df: negative filesystem block count/size from fs /Volumes/(my ip removed)
df: negative filesystem block count/size from fs /Volumes/(my ip removed)
<http://(my> ip removed)/ 0 0 0 0% /Volumes/(my ip removed)

any suggestions now?

[mike...@officeformac.com]

I solved it!!!

<http://technet.microsoft.com/en-us/library/cc288173.aspx>

I had to make sure it had a Public URL.

[mike...@officeformac.com]

I want to note that you have to also do the the previous post concerning putting in the _vti_inf.html file and other steps. I tried to take it out and it immediately stopped working.