locked
Errors during edge server validation RRS feed

  • Question

  • Hi, I'm encoutering the following errors during my edge server's validation.

    192.168.36.71 is my external edge address

    192.168.36.10 is my domain controller and DNS server.

     

    I don't understand why it tryes to connect to my DNS / DC on the port 5061...

     

     

     

    No WMI Instance Returned By Query : select * from MSFT_SIPFederationNetworkProviderTable where Enabled = 'TRUE'
    No WMI Instance Returned By Query : select * from MSFT_SIPFederationPartnerTable
    Found External Edge listening address : 192.168.36.71:5061:TLS - Enabled
    Found External Edge listening address : 192.168.36.71:443:TLS - Enabled
      

    Failure
    [0xC3FC200D] One or more errors were detected 

     

    _________________________________________________________


    DNS Resolution succeeded: 192.168.36.10


    TLS connect failed: 192.168.36.10:5061 Error Code: 0x274d Aucune connexion n'a pu être établie car l'ordinateur cible l'a expressément refusée


    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. 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.
      

    Failure
    [0xC3FC200D] One or more errors were detected 


    Thanks for your help !

     

    Regards

    Thursday, August 16, 2007 9:13 AM

All replies

  • Hi,

    I'm getting your same first edge server validation error about "No WMI Instance Returned By Query

    I'm not sure whether its related to this but external users cannot sign in and internal users get a 'Limted Extneral Calling' warning.

     

    We haven't enabled Federation so not sure whether this is an issue, but we have had external users signing in fine in both the Public Beta and Release Candidate versions.

    Not sure why this is suddenly popped up.. Unless its new to the RTM version?

     

    Have tried flushdns / reboot on both front end server and edge server without any success..

    Wednesday, September 19, 2007 1:29 AM