MAC Office 2008 Document Connection - The connection failed

MIkei-ma
MIkei-ma used Ask the Experts™
on
trying to access my sharepoint server with document connection tool in new 12.2.0 version of office 2008 and keep getting "the connection failed"

I have two access to the same server, one uses form based authentication (external use) and one uses windows & basic authentication. The checkbox for "use basic authentication" does not make a difference.

Both access points fail with document connection.  I have been able to use the web interface with the forms authentication through safari & firefox, but never have been able to use the straight webdav connection

Any suggestions?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
When adding a new location in Document Connection you need to use the FQDN for your site without anything added for a specific library:

GOOD:  http://yoursite.yourcompany.com
BAD:   http://yoursite.yourcompany.com/sites/anothersite/library/Forms/AllItems.aspx

Under the Authentication dropdown choose Username and password:

User name: domain\user
Password:

Author

Commented:
That is how I log in Neither works.

sites are:
http://partner.domainname.com (forms authentication)
or
http://##.##.##.##  (basic and windows authentication)

Is there a log somewhere I can look at to see what it says?

I do not have a domain controller, I've tried the computer name\user but that doesn't work either (I use the computername\user that is listed in sharepoint as user in the upper right hand corner when I login via web interface.
If you're not even connecting there really wouldn't be a log.  

Since you're connection via ip address, what is the port for the site and are you adding it?  http://xxx.xxx.xxx.xxx:xxxx


Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Both sites are at :80 on different IP's  I tried :80 for giggles & grins.. but same response.  FYI I've even tried the administrator password with same results.
I tried this on my home setup (where I have a mac and SharePoint) and I was able to get it to work with ip:port, but I have AD.  I did some poking around in the documentation, what little there is, and I'm guessing your setup wasn't one that was anticipated. I would open a ticket with Microsoft to report it as a bug and see their response.

Author

Commented:
Thanks.  Hopefully MS has a solution.  I'm not sure I said this before but if I put in an incorrect password it does report that it is incorrect.  Wouldn't there be a log SOMEWHERE that sharepoint uses for this type of thing?
Well that's a different story and may allow us to see some extra information. You can use the security event log to see if there are any entries for your attempts.  If you don't see anything in this log you'll need to enable auditing first.

Author

Commented:
the security event log in sharepoint or on the server?
You would use the server security event log that is available via the event viewer.

Author

Commented:
OK here's the two entries that were created when I attempted to log in.

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          8/11/2009 8:24:37 AM
Event ID:      4624
Task Category: Logon
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      WIN-N5-196
Description:
An account was successfully logged on.

Subject:
      Security ID:            NULL SID
      Account Name:            -
      Account Domain:            -
      Logon ID:            0x0

Logon Type:                  3

New Logon:
      Security ID:            WIN-N5-196\mikei
      Account Name:            mikei
      Account Domain:            WIN-N5-196
      Logon ID:            0xcf7d5ec
      Logon GUID:            {00000000-0000-0000-0000-000000000000}

Process Information:
      Process ID:            0x0
      Process Name:            -

Network Information:
      Workstation Name:      
      Source Network Address:      71.192.45.138
      Source Port:            46641

Detailed Authentication Information:
      Logon Process:            NtLmSsp
      Authentication Package:      NTLM
      Transited Services:      -
      Package Name (NTLM only):      NTLM V2
      Key Length:            0

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
      - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
      - Transited services indicate which intermediate services have participated in this logon request.
      - Package name indicates which sub-protocol was used among the NTLM protocols.
      - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" />
    <EventID>4624</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8020000000000000</Keywords>
    <TimeCreated SystemTime="2009-08-11T12:24:37.865Z" />
    <EventRecordID>130861</EventRecordID>
    <Correlation />
    <Execution ProcessID="640" ThreadID="764" />
    <Channel>Security</Channel>
    <Computer>WIN-N5-196</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-0-0</Data>
    <Data Name="SubjectUserName">-</Data>
    <Data Name="SubjectDomainName">-</Data>
    <Data Name="SubjectLogonId">0x0</Data>
    <Data Name="TargetUserSid">S-1-5-21-1530438755-196007718-2331082839-1011</Data>
    <Data Name="TargetUserName">mikei</Data>
    <Data Name="TargetDomainName">WIN-N5-196</Data>
    <Data Name="TargetLogonId">0xcf7d5ec</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">NtLmSsp </Data>
    <Data Name="AuthenticationPackageName">NTLM</Data>
    <Data Name="WorkstationName">
    </Data>
    <Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">NTLM V2</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x0</Data>
    <Data Name="ProcessName">-</Data>
    <Data Name="IpAddress">71.192.45.138</Data>
    <Data Name="IpPort">46641</Data>
  </EventData>
</Event>

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          8/11/2009 8:24:37 AM
Event ID:      4776
Task Category: Credential Validation
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      WIN-N5-196
Description:
The domain controller attempted to validate the credentials for an account.

Authentication Package:      MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account:      MIKEI
Source Workstation:      
Error Code:      0x0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" />
    <EventID>4776</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>14336</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8020000000000000</Keywords>
    <TimeCreated SystemTime="2009-08-11T12:24:37.865Z" />
    <EventRecordID>130860</EventRecordID>
    <Correlation />
    <Execution ProcessID="640" ThreadID="764" />
    <Channel>Security</Channel>
    <Computer>WIN-N5-196</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="PackageName">MICROSOFT_AUTHENTICATION_PACKAGE_V1_0</Data>
    <Data Name="TargetUserName">MIKEI</Data>
    <Data Name="Workstation">
    </Data>
    <Data Name="Status">0x0</Data>
  </EventData>
</Event>
The log looks fine. I sent a note to our Microsoft contact and his response was less than thrilling. Supposedly this is a known issue for the beta version of the document connection tool, but it was supposed to be fixed by installing Office 2008 SP2 (which came with the full version).  It didn't take him long to reply back so it must just be a standard entry in their knowledge base since I doubt he would know off the top of his head.
I would still recommend getting some feedback to Microsoft.

Author

Commented:
Now.. that feedback would that be in the form of your ^^%$^&( programs don't work?  All kidding aside, where should I post this to get some response?

Author

Commented:
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?

Author

Commented:
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.

That really doesn't make sense then. If you can access it directly over webDAV then you should be able to use it in an application (document connection). The VPN/non VPN connection variation, or now lack thereof, might be worth looking into in the future, but since you're able to access the library now I can't see how it would be impacting anything to resolve this question. I'd definitely treat this as a bug. Have you contacted Microsoft yet?

Author

Commented:
posted to the mactopia forums, but no-one has stepped up from MS - others have, but not MS

Author

Commented:
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?
I know it looks like this should be bad, but it's normal for a mounted volume over webDAV since it can't get the information like it could with a local volume.  

You can force the volume to unmount using terminal:

diskutil umount force /Volumes/NAME

Open in new window

Commented:
I solved it!!!

see this technote

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

make sure you have a PUBLIC URL that can be mapped and WHALA!! it worked :)

Author

Commented:
I also want to comment that you have to add the vt_inf.html file process listed in this post to make it work.

http://www.officeformac.com/ms/ProductForums/Office/3914/34

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial