Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Unable to establish a connection between the Confluence server and Sharepoint 2007
  2. "Basic Connection Test Failed:: Connection refused: connect" error while conducting "test connection" (under the Sharepoint Admin in Confluence).

The following appears in the atlassian-confluence.log:

...

  1. Check the operating system that the Confluence server is on. If it is Windows, the "Connection Refused" means Confluence couldn't connect to the Windows NTLM SOAP Proxy started by Confluence.  If If it is Unix or Mac, need to check on the network and firewall configuration, as Confluence is being prevented from connecting to SharePoint over the network.
  2. Check if something else is using this port by running the following command from a command prompt: netstat -a -b. Example output:

    Code Block
    C:\Windows\system32>netstat -a -b
    
    Active Connections
    
      Proto  Local Address          Foreign Address        State
      TCP    0.0.0.0:80             bluetongue:0           LISTENING
     Can not obtain ownership information
      TCP    0.0.0.0:135            bluetongue:0           LISTENING
      RpcSs
     [svchost.exe]
      TCP    0.0.0.0:389            bluetongue:0           LISTENING
     [dsamain.exe]
      TCP    0.0.0.0:445            bluetongue:0           LISTENING
     Can not obtain ownership information
      TCP    0.0.0.0:636            bluetongue:0           LISTENING
     [dsamain.exe]
      TCP    0.0.0.0:3389           bluetongue:0           LISTENING
      CryptSvc
     [svchost.exe]
      TCP    0.0.0.0:5357           bluetongue:0           LISTENING
     Can not obtain ownership information
      TCP    0.0.0.0:17500          bluetongue:0           LISTENING
     [Dropbox.exe]
      TCP    0.0.0.0:18798          bluetongue:0           LISTENING
     [Skype.exe]
      TCP    0.0.0.0:23284          bluetongue:0           LISTENING
     Can not obtain ownership information
      TCP    0.0.0.0:32843          bluetongue:0           LISTENING
     Can not obtain ownership information
      TCP    0.0.0.0:32844          bluetongue:0           LISTENING
     Can not obtain ownership information
      TCP    0.0.0.0:32846          bluetongue:0           LISTENING
     [SPUCHostService.exe]
      TCP    0.0.0.0:39045          bluetongue:0           LISTENING
     Can not obtain ownership information
      TCP    0.0.0.0:49152          bluetongue:0           LISTENING
     [wininit.exe]
      TCP    0.0.0.0:49153          bluetongue:0           LISTENING
      eventlog
     [svchost.exe]
      TCP    0.0.0.0:49154          bluetongue:0           LISTENING
     [lsass.exe]
      TCP    0.0.0.0:49155          bluetongue:0           LISTENING
      Schedule
     [svchost.exe]
      TCP    0.0.0.0:49157          bluetongue:0           LISTENING
     [dsamain.exe]
      TCP    0.0.0.0:49239          bluetongue:0           LISTENING
     [services.exe]
      TCP    0.0.0.0:49268          bluetongue:0           LISTENING
      PolicyAgent
     [svchost.exe]
      TCP    0.0.0.0:52885          bluetongue:0           LISTENING
     [idea.exe]
      TCP    127.0.0.1:4331         bluetongue:0           LISTENING
    


...

It looks like the technology we use to run the proxy (.NET's HttpListener) actually required admin privileges to run , because it depends on a sensitive HTTP access library built in to into Windows. Details can be found here:   https://connect.microsoft.com/VisualStudio/feedback/details/93940/httplistener-requires-admin-priveleges

...