Homepage | Products | OX Knowledge Base | Support | Try Now | Contact | Company
OX Logo
Results 1 to 3 of 3
  1. #1

    Default OXtender for Outlook not connecting to server

    Hello,

    I have the following setup:

    * server side
    - Open-Xchange Server Edition - Build: 6.8.1-6812, 2009-04-14
    - installed on Debian Etch with latest updates
    - reachable through https, port 443

    * client side
    - Windows Vista Ultimate SP2
    - Outlook 2007 SP2
    - OXtender for Outlook version 6.2.0.29

    I successfully connect to my server on https://server.example.com.

    OXtender for Outlook installed properly. When opening Outlook for the first time after installing OXtender, I get the OXtender setup page to enter serveur URL, login and password.

    I set server URL to https://server.example.com and my login credential. When I click on apply, I get the following error message:

    "Error: Connection to the server failed. Please check the server name. If the server name was entered correctly please check the server connection (HTTP CODE: -2)"

    The OXlook Debugging viewer does not seem to provide any useful indication:

    "--------------------------------------------------------------------------------------
    [GLOBAL]

    9:53:10 AM Enable debug logging.
    9:53:10 AM Here we go! Starting now.
    9:53:10 AM OXlook Version is: "6.2.0.29"
    9:53:10 AM Working with timezone: (GMT+01:00) Brussels, Copenhagen, Madrid, Paris
    9:53:10 AM Working with outlook version: 12.0
    9:53:10 AM Go next step.
    9:53:11 AM Hook in.
    9:53:11 AM Working with profile "Outlook". Preparing registry.

    [RFLD]
    [SFLD]
    [RMSG]
    [SMSG]
    [IPM.A]
    [IPM.T]
    [IPM.C]
    [SATT]
    [RATT]"

    On the server side, I verify through a tcpdump that the plug-in indeed tries to connect on the server:

    "10:04:56.758937 IP client.example.com.49443 > server.example.com.https: S 4049897153:4049897153(0) win 8192 <mss 1460,nop,wscale 2,nop,nop,sackOK>
    10:04:56.758972 IP server.example.com.https > client.example.com.49443: S 109106683:109106683(0) ack 4049897154 win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 7>
    10:04:56.759941 IP client.example.com.49443 > server.example.com.https: . ack 1 win 16425
    10:04:56.760856 IP client.example.com.49443 > server.example.com.https: P 1:163(162) ack 1 win 16425
    10:04:56.760877 IP server.example.com.https > client.example.com.49443: . ack 163 win 54
    10:04:56.761496 IP server.example.com.https > client.example.com.49443: . 1:1461(1460) ack 163 win 54
    10:04:56.761503 IP server.example.com.https > client.example.com.49443: P 1461:1739(278) ack 163 win 54
    10:04:56.762785 IP client.example.com.49443 > server.example.com.https: . ack 1739 win 16425
    10:04:56.829463 IP client.example.com.49443 > server.example.com.https: P 163:361(198) ack 1739 win 16425
    10:04:56.830959 IP server.example.com.https > client.example.com.49443: P 1739:1798(59) ack 361 win 63
    10:04:56.833134 IP client.example.com.49443 > server.example.com.https: F 361:361(0) ack 1798 win 16410
    10:04:56.833192 IP server.example.com.https > client.example.com.49443: P 1798:1835(37) ack 362 win 63
    10:04:56.833216 IP server.example.com.https > client.example.com.49443: F 1835:1835(0) ack 362 win 63
    10:04:56.833893 IP client.example.com.49443 > server.example.com.https: R 362:362(0) ack 1835 win 0"

    Any idea where the problem is coming from?

    Thanks in advance for your help.

    MichaŽl

  2. #2
    mab75 Guest

    Default Your Post

    Hi MichaŽl,

    i have the same problem. Do you solve the problem or get an answer?

    Kind regards.

    Maik

  3. #3
    benjamin Guest

    Default

    I'm now having the same problem.
    Frankly it works when I use a different user, so I guess this is user related, but I couldn't yet figure out what's the exact problem.

    Any suggestions?

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •