newbie question related to sync service connection options

[GoogleCodeExporter]

What steps will reproduce the problem?
1. install sync service and configure
2. go to diagnostic.aspx in a browser and try to write appointment data
3.

What is the expected output? What do you see instead?
I expect the output to try to connect to Exchange.ServerName on port 139 to
write appointment data but it is connecting on port 80.

What version of the product are you using? On what operating system?
newest f/b from website, windows xp

Please provide any additional information below.
i've reviewed the documentation and configuration seems fairly
straightforward.  should exchange host be listening on 80?

Original issue reported on code.google.com by raymond....@gmail.com on 3 Jun 2010 at 12:53

[GoogleCodeExporter]

oh and another note is the company the pilot is for has an externally hosted 
exchange
so i'm not sure if port 80 is an option.

Original comment by raymond....@gmail.com on 3 Jun 2010 at 7:07

[GoogleCodeExporter]

Sync service uses webdav to write to free\busy server. It makes an http\https 
call so
connects at port 80\443. What is your configuration and why are you expecting 
it to
connect at 139 ?

Original comment by jaideepg...@google.com on 7 Jun 2010 at 5:43

[GoogleCodeExporter]

well, 80/443 would imply that there was some interface to receive the request.  
this
clients exchange environment is hosted by aliant and port 80 does not appear to 
be
open.  do you know specifically what portion of exchange is required?  i am 
currently
asking aliant to open this port to us but is there anything specific they need
configured on the exchange end?  thanks.

Original comment by raymond....@gmail.com on 7 Jun 2010 at 1:55

[GoogleCodeExporter]

(they have already configured receive as permissions on the mailbox store)

Original comment by raymond....@gmail.com on 7 Jun 2010 at 1:55

[GoogleCodeExporter]

I have stopped updating this thread from lack of response but here goes for 
another try.  I was not able to get free busy working because aliant would not 
open port 80.

Failing that, the client had a parallel 2010 exchange in place so I was able to 
successfully connect.  Now all tests in diagnostic.aspx pass except writing 
information to exchange.  I have verified that the exchange admin user has 
receive as permissions and that the sync service is running as this user.  I 
have also verified that public folders are available in exchange.  

The error message when trying to write to exchange is (440) Login Timeout.

Original comment by raymond....@gmail.com on 8 Jul 2010 at 3:18

[GoogleCodeExporter]

The supported exchange servers are 2003 and 2007, so I am not sure about the 
behaviour in Exchange 2010.

If the option which is failing in diagnostics is "Verify Appointment can be 
written to Exchange", you can avoid it. It is for verification of 
AppointmentWriter which is not fully supported. You should use SchedulePlus 
write in your config file. To verify that SchedulePlus writer is working, 
please check "Verify Free/Busy can be written to Exchange" option works in 
diagnostics.

Original comment by jaideepg...@google.com on 8 Jul 2010 at 5:22