Edge Server cannot contact next hop server

مؤمّن Edge Server cannot contact next hop server

  • 01/محرم/1429 11:46 ص
     
     

     

    Hi there,

     

    I am at my wit's end. When I run the Edge server validation Wizard I get the following error:

     

    DNS Resolution succeeded: 192.168.1.69
    TLS connect failed: 192.168.1.69:5061 Error Code: 0x2751 A socket operation was attempted to an unreachable host
    Suggested Resolution: Make sure that the server is listening on the specified IP address/Port/Transport. If you have a firewall make sure that this port is open. Make sure that the server is running. If this is an Edge Server, ensure that remote user access has been enabled. This can be ignored if you have not enabled the transport on the target server.
    Suggested Resolution: Ensure that the DNS records have been setup correctly. If this server is an Access Edge Server, make sure outside user access is enabled.

     

     

    I installed OCS using a Single Site Edge Topology with ISA 2006 as firewall. Cummunicator works like a charm internally, but as you can imagine, it is all pretty useless without the ability to use Federation and remote access.

     

    Due to a lack of resources I had to install the Edge server on the ISA server.

     

    Any advice on where possibly to start looking for a solution would be greatly appreciated.

     

    Regards,

    Warren

جميع الردود

  • 01/محرم/1429 04:24 م
    المشرف
     
     

    Due to a lack of resources I had to install the Edge server on the ISA server.

     

    I think you are going to run into a lot of headaches if you try to run an OCS Consolidated Edge Server on the same hardware as your ISA server; it might not even be possible.

     

    Verify that your Edge internal interface and Front-End server not seperated by any NAT.

    Telnet to port 5061 on the front-end server from the Edge server to test connectivity.