locked
Edge R2 External NIC trying to connect to internal client RRS feed

  • Question

  • Hi,

    I have a lot of experience deploying edge server in multiple scenarios, but this is not working for me and is a really strange behaviour

    Consolidated Edge - Windows 2008 - Internal and External Firewall - Two interfaces

    One "External" with 2 IPs:

    ->Access Edge, Web Conference : DMZ IP

    ->A/V Edge : Another NATed DMZ IP (With NAT checkbox also)

    Another "Internal" with 1 IP

    When an external MOC User calls or is called by an Internal MOC User I get the famous "Call terminated on media connectivity failure"

    - MOC candidates are ok because public IPs are being promoted

    - I only have Def Gw on the External NIC and a route to internal network as the edge guide says

    - All required ports are opened on firewalls

    This is the strange thing: I checked with Wireshark/TCPView and when the call is being established, MediaRelaySvc.exe process is trying to connect through the external IP to the internal moc user IP.

    Example

    Process: MediaRelaySvc.exe

    Local 190.x.x.x Destination 192.x.x.x

    I checked this with another deployment I made, and MediaRelaySvc.exe process tries to connect to internal lan using the correct interfase, like this:

    Process: MediaRelaySvc.exe

    Local 192.x.x.x Destination 192.x.x.x

    I also tested without firewall, I mean, with direct WAN and direct LAN, and the behaviour is the same.

    My guess would be about routing and gateways thing... but I have only one default gateway and it is on the wan side as the guide says.

     Edit: Sorry, I just realized this is not in the correct forum, please move.

    • Edited by Andres_D Thursday, December 16, 2010 8:43 PM forum mistake
    Thursday, December 16, 2010 8:42 PM

Answers

  • It seems Fixed Now.

    If this happens to anyone: Check correct resolution of internal DNS A Record for Edge and Routing Tables of internal firewalls.

    Thanks

    • Marked as answer by Andres_D Monday, December 20, 2010 4:30 PM
    Monday, December 20, 2010 4:30 PM

All replies

  • Can your EDGE resolve the external AV EDGE Address?
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Thursday, December 16, 2010 10:33 PM
  • Sounds like you need to define a route to the internal ip subnet.  "route add -p address mask gateway IF"  So when the server has to make a choice for "address" it knows upon which interface to place the packets.  Did you ever define the internal user subnet on the edge server when you took the GW off the internal NIC?
    John Weber [Lync MVP]
    Thursday, December 16, 2010 11:43 PM
  • Yes, Can resolve it, and I verify this looking at event viewer for the typical message saying about the address binding and is ok.

    Thanks for the answer

    Friday, December 17, 2010 2:40 AM
  • That is exactly the way I defined the route to internal network.

    Thanks for the answer

    Friday, December 17, 2010 2:41 AM
  • It seems Fixed Now.

    If this happens to anyone: Check correct resolution of internal DNS A Record for Edge and Routing Tables of internal firewalls.

    Thanks

    • Marked as answer by Andres_D Monday, December 20, 2010 4:30 PM
    Monday, December 20, 2010 4:30 PM