I use the exchange connector at work and the GC connection is via ldap. I don't think it will honor the host:port usage though. Maybe if you did -L389:host:389 and point your connector to localhost for the GC that might work for you. (unless your running an ldap server locally on that port).
-paulw -----Original Message----- From: Jeff Macdonald [mailto:[EMAIL PROTECTED] Sent: Friday, September 24, 2004 10:56 AM To: Paul Lussier Cc: GNHLUG Discussion Subject: Re: Evolution and Exchange - a Global Catalog Server question Ok, as Paul requested, some better details (I'll try my best, I'm at work now): OWA is enabled and I can see calanders, public folders, etc. That part works just fine. The part that doesn't work fine is the Global Catalog Server stuff that Evolution can use for address completion. I don't believe this uses OWA. When specifying an Exchange server connection for the account there is a box for providing the address of the Global Catalog Server (GCS). There is not a input box were one can set the port like you can when a Directory Server is used. So I just added a :port# to the end of the server address. So here are the steps I took: I ssh to work and specify port forwarding like so: ssh -L 1389:ad.work.com:389 ssh-host.work.com I set the server for GCS to localhost:1389 I click on the Global Address List and type a name. Nothing. I tried composing a message and typing someones name at work. No auto-completion. So I'm assuming that Evolution doesn't support the port hack I did. So I'm making the assumption that the GCS uses LDAP. That may be a bad assumption. Anybody know? -- Jeff Macdonald Ayer, MA _______________________________________________ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss _______________________________________________ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
