external users are unable to download address book. meet and dialin pages come up fine externally, can make calls, have meetings etc. just no ab d

I got group expansion and ab download to work by publishing the lync interal web services instead of lync external web services.
The external web services gave me an error on the lync front end server's IIS external website:
POST lyncpool.domain.com/groupexpansion/service.svc/WebTicket_Bearer  500 internal server error
Once i changed the reverse proxy to forward to my internal web services everything worked. Hope this helps someone
I dont know if there is any difference between the lync external webservices website and the internal one on the front end. Can anyone tell me if this is ok or not recommended in what i d

Exposing the Internal web services to the Internet is Not recommended. Authentication is handled differently and Virtual Directories like the CSCP on the internal web services will now be exposed.

I'd recommend resolving the root problem, take a look at the following: http://social.technet.microsoft.com/Forums/en-US/ocsaddressbook/thread/83106a88-7b38-49cc-b62d-52867a99bfd1 it suggests removing the Web Components and IIS and installing them again, make sure to apply the latest CU and windows updates as well.

How did you configure your reverse proxy for the external services.

The reverse proxy should forward the request to the port 4443 oft the FE server

It is expected error when you browser lyncpool.domain.com/groupexpansion/service.svc with the error 500 Internal Server Error on the Lync Server Front End Server. You need to browser the URL on other computer.

yes the rp is forwarding to the FE on 4443, no i am not running the url on the FE directly, this is shown up in the IIS logs on the FE when an ext client connects and attempts to dl the ab

Any update? Did you remove the web components and install them again?

I went into control panel and removed the "lync 2013 web components server" and also removed IIS. now rebooting the server and going to reinstall them

getting same error.

Apply windows updates again, make sure it's at the same CU as the other components.

Any update?