Lync Edge Services Won't Start (Network Steve Forum)

Lync Edge Services Won't Start

I read a lot about thee problems others faced but none of them solved my issues . in the event viewer here are the problems.

LS Protocol Stack : Unable to bind for socket.

Transport:TLS, IP address:77.42.220.238, Port:5061. Error:0x80072741 (The requested address is not valid in its context.).
Resolution:
Ensure that no other program is listening to the specified port and that the IP address is valid.Log Name:      Lync Server
Source:        LS Protocol Stack
Date:          4/14/2015 5:31:34 PM
Event ID:      14346
Task Category: (1001)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      lyncedge.domtech.org
Description:
Unable to bind for socket.

Transport:TLS, IP address:77.42.220.238, Port:5061. Error:0x80072741 (The requested address is not valid in its context.).
Resolution:
Ensure that no other program is listening to the specified port and that the IP address is valid.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="LS Protocol Stack" />
    <EventID Qualifiers="50153">14346</EventID>
    <Level>2</Level>
    <Task>1001</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-14T14:31:34.000000000Z" />
    <EventRecordID>992</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer>lyncedge.domtech.org</Computer>
    <Security />
</System>
<EventData>
    <Data>TLS</Data>
    <Data>77.42.220.238</Data>
    <Data>5061</Data>
    <Data>0x80072741</Data>
    <Data>The requested address is not valid in its context.</Data>
</EventData>
</Event>
LS Protocol Stack : A configured transport has failed to start.

Transport TLS has failed to start on local IP address 77.42.220.238 at port 5061.
Cause: Configuration error, low system resources or another program is using the specified port. Can also happen if the IP address has become invalid.
Resolution:
Ensure that the IP address specified is valid and that no other program is listening on the specified port.Log Name:      Lync Server
Source:        LS Protocol Stack
Date:          4/14/2015 5:31:34 PM
Event ID:      14336
Task Category: (1001)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      lyncedge.domtech.org
Description:
A configured transport has failed to start.

Transport TLS has failed to start on local IP address 77.42.220.238 at port 5061.
Cause: Configuration error, low system resources or another program is using the specified port. Can also happen if the IP address has become invalid.
Resolution:
Ensure that the IP address specified is valid and that no other program is listening on the specified port.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="LS Protocol Stack" />
    <EventID Qualifiers="50153">14336</EventID>
    <Level>2</Level>
    <Task>1001</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-14T14:31:34.000000000Z" />
    <EventRecordID>993</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer>lyncedge.domtech.org</Computer>
    <Security />
</System>
<EventData>
    <Data>TLS</Data>
    <Data>77.42.220.238</Data>
    <Data>5061</Data>
</EventData>
</Event>
LS Server : The protocol stack reported a critical error: code 80072741 (The requested address is not valid in its context.). The service has to stop.Log Name:      Lync Server
Source:        LS Server
Date:          4/14/2015 5:31:34 PM
Event ID:      12303
Task Category: (1000)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      lyncedge.domtech.org
Description:
The protocol stack reported a critical error: code 80072741 (The requested address is not valid in its context.). The service has to stop.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="LS Server" />
    <EventID Qualifiers="50152">12303</EventID>
    <Level>2</Level>
    <Task>1000</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-14T14:31:34.000000000Z" />
    <EventRecordID>994</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer>lyncedge.domtech.org</Computer>
    <Security />
</System>
<EventData>
    <Data>80072741</Data>
    <Data>The requested address is not valid in its context.</Data>
</EventData>
</Event>
LS Protocol Stack : Unable to start the stack.

Error: 0xC3E93C0A (SIP_E_STACK_TRANSPORT_FAILED)Log Name:      Lync Server
Source:        LS Protocol Stack
Date:          4/14/2015 5:31:34 PM
Event ID:      14352
Task Category: (1001)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      lyncedge.domtech.org
Description:
Unable to start the stack.

Error: 0xC3E93C0A (SIP_E_STACK_TRANSPORT_FAILED)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="LS Protocol Stack" />
    <EventID Qualifiers="50153">14352</EventID>
    <Level>2</Level>
    <Task>1001</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-14T14:31:34.000000000Z" />
    <EventRecordID>995</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer>lyncedge.domtech.org</Computer>
    <Security />
</System>
<EventData>
    <Data>0xC3E93C0A</Data>
    <Data>SIP_E_STACK_TRANSPORT_FAILED</Data>
</EventData>
</Event>

Any Help Would be apreciated , Thanks !

Edited by JadCham Tuesday, April 14, 2015 3:02 PM

April 14th, 2015 3:01pm

I fought this error yesterday, it was a typo in the IP that I swore wasn't there. Is 77.42.220.238 assigned to a NIC directly? Can you paste the results of an ipconfig /all and we'll be a second set of eyes?

Also post the results of

netstat -an | find "5061"

Free Windows Admin Tool Kit Click here and download it now

April 15th, 2015 10:06am

Hi , Thanks for helping.

The ip 77.42.220.238 is not directly assigned . one of the NICs (the one with default gateway) has an ip 192.168.16.133 and this ip is on dmz on the firewall server.

Is there something wrong with this configuration ?

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : lyncedge
   Primary Dns Suffix . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio
n #2
   Physical Address. . . . . . . . . : 00-50-56-AC-1B-77
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::f18d:359b:1d9b:2544%16(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.16.133(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 369119318
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-AE-6E-57-00-50-56-AC-0B-CD

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio
n
   Physical Address. . . . . . . . . : 00-50-56-AC-0B-CD
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6d50:4e3f:fc9c:602d%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.16.111(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 77.42.220.238(Duplicate)
   Subnet Mask . . . . . . . . . . . : 255.255.255.252
   Default Gateway . . . . . . . . . : 192.168.16.1
   DHCPv6 IAID . . . . . . . . . . . : 251678806
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-AE-6E-57-00-50-56-AC-0B-CD

   DNS Servers . . . . . . . . . . . : 192.168.16.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{90E4A645-CCFD-4E7E-909B-93EA2B2065FB}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{0E4827CF-DA02-4AB0-866E-775D7AF9BA63}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

April 15th, 2015 11:18am

That won't work. The IPs you have laid out in Topology builder need to be directly assigned to the NICs. For example, if you have 77.42.220.238 NAT'd to 192.168.16.133, you'd want to add 192.168.16.133 in the topology builder so the Edge knows which IP to listen on for that set of ports.

Let's take a step back. For your edge, you ideally want two NICs in two separate subnets. One subnet is external facing, meaning that it would talk to the Internet (and would NAT to/from 77.42...). The other is strictly for talking to Internal servers like your Front End. This is ideally a second DMZ.

The second item to consider is are you using three public IP addresses for your edge, or only one? That will make a difference in how you lay this out in topology builder.

So, currently, how many subnets/IPs do you have assigned to the edge and what are those subnets, are they DMZs?

Free Windows Admin Tool Kit Click here and download it now

April 15th, 2015 11:52am

This topic is archived. No further replies will be accepted.