locked
Verify reverse proxy RRS feed

All replies

  • Is it

     

    https://externalwebfarm/Abs/Ext/Handler

     

    or

     

    https://externalwebfarm/Abs/Ext/ ?

     

    I'm getting a login dialog in our environment...

     

    Thomas

    Wednesday, September 26, 2007 3:41 PM
  • The deployment guide says https://externalfqdn/Abs/Ext , this gives me "IE cannot display page"

     

    but when I try

    https://externalfqdn/Abs/Ext/handlers

     I get a login promit but I'm not able to login. Can you login when you are promted?

     

    Thanks

    Henrik

    Wednesday, September 26, 2007 3:55 PM
  • I have tried logging on with the administrator account but I get a blanc - not authorized - page. It seems that my communicator is able to access it because I don't have any address book server errors.

     

    By the way: if you look at the OCS MMC console, click on the OCS pool, look at the status tab and expand the Address Book Server Settings I can see:

     

    Synchronization time: 01:30:00
    Output location: C:\Program Files\Microsoft Office Communications Server 2007\Web Components\Address Book Files\Files
    File share location for internal connections: https://internalwebfarm/Abs/Int/Handler
    File share URL for external connections: https://externalwebfarm/Abs/Ext/Handler

     

    So I'm not sure if the "/Handler" entry should be there. It was added as default to the internalwebfarm link so I was adding with the external link.

     

    Cheers,

     

    Thomas

     

    Wednesday, September 26, 2007 4:05 PM
  • HI again!

     

    Everything seems to be ok on there server as far as I can see. I'm no longer sure of the expected result when accessing the ocs external. When I do a serarch in my communicator client on my internal network by typing an "a it displays every user in our AD starting on a regardless of if they are enabled for OCS or not. But when doing the same using the Communicator mobile I onle get the users that are enabled for OCS, what should I expect. And is there a way to logg the traffic from my mobile client to my internal ocs.

     

    Thanks again!

     

    HenrikR

     

    Thursday, September 27, 2007 6:56 AM
  • Hi Henrik,

     

    It seems that everything works fine. I'm telling you this because I know what happens if Communicator can not reach the ABS server. Then you get a very clear error stating that the adress book server can not be reached. In some cases you are not able to make outbound calls via a PBX as well since the policies can not be loaded. Reading your post I may conclude that this is not the case in your environment.

     

    To log traffic you can use a tool named Wireshark (Network Protocol Analyzer). Please refer to http://www.wireshark.org or just analyze the Communicator log in C:\Documents and Settings\%personalaccount%\tracing

     

    Good luck and have fun with OCS!

     

    Thomas

    Thursday, September 27, 2007 7:58 AM
  •  

    Hi,

     

    Same problem here. ISA works fine, I can retrieve the tshoot.html page. But the communicator says 'cannot synchronise address book information'.

    both trying externalfqdn/abs/ext/handler as well as /abs/ext/ doesn't give anything reasonable back.

     

    Hope to find out some more through the forum.

     

    Thanks, Erik

     

    Wednesday, March 5, 2008 12:03 PM
  • Hi can you try to access another service like for example the live meeting groupexpansion service?

    https://external_ocs_servernaam/GroupExpansion/Ext/Service.asmx

    If the reverse proxy plus the external url's are configured in the right way you should at least get access to the page above...
    Wednesday, March 5, 2008 4:24 PM