I've been able to install LYNC and have the meet and dialin function working properly internal/external. I'm attempting to test setting up external access to the client with an edge server. All seems to install properly etc with no errors being thrown my way. But in the services i have a few that will not start with the below errors. Can anyone point me to a deployment scenario with an edge server how-to?

Any help would be greatly appreciated.

The Lync Server Access Edge service terminated with service-specific error %%-1008124918.

The Lync Server Web Conferencing Edge service terminated with the following error:
The requested address is not valid in its context.

I worked with him on this offline.

He did not have his external IP addresses assigned correctly on his edge serve which was causing the services to not start.

I am having the same issue.  Can you please post what your setup is and how you where able to get this working.

• Edited by Mike11110011 Thursday, October 21, 2010 4:28 PM word change

I am having the same issue.  Can you please post what your setup is and how you where able to get this working.

• Edited by Mike11110011 Thursday, October 21, 2010 4:28 PM word change

I'm having a similar issue.  Looking at it I think I have the IPs correct.

I fixed the issue by installing a public cert to the server.  Below is my config.

Two network cards. DMZ and inside.

DMZ has an ip address of 192.168.0.21, 255.255.255.0, GW 192.168.0.1

Inside has an ip address of 10.10.10.21, 255.255.255.0, No GW.

I used a public cert for both inside and external and everything worked.

• Proposed as answer by Ara Khlghatyan Friday, July 22, 2011 5:59 AM

I fixed the issue by installing a public cert to the server.  Below is my config.

Two network cards. DMZ and inside.

DMZ has an ip address of 192.168.0.21, 255.255.255.0, GW 192.168.0.1

Inside has an ip address of 10.10.10.21, 255.255.255.0, No GW.

I used a public cert for both inside and external and everything worked.

• Proposed as answer by Ara Khlghatyan Friday, July 22, 2011 5:59 AM

I worked with him on this offline.

He did not have his external IP addresses assigned correctly on his edge serve which was causing the services to not start.

hello,

can you confirm what was actually wrong with the assignment of the External IP address.

I have the same issue, but believe I have both IP addresses enabled correctly.

Dale

Hi every body, I am trying to do  a proof of concept before we buy the public Certificate for my Edge server but I have this error..

I have the same error as you guys (1008124918 )

Here is my setup

Active directory with a CA on it. ( I used this CA for my Front-End, and for both Internal/External Edge Certificate )

FrontEnd ;

-In the domain

-192.168.16.55 255.255.255.0

==

Edge:

Inside NIC : 192.168.16.57 255.255.255.0, no gateway

Outside NIC (dmz ) : 192.168.18.80 255.255.255.0   . Gateway 192.168.18.0

The edge is not in the domain.

==

My Public IP : 69.70.xx.xx

=====================

In the wizzard for the edge-pool

I choose:

-Single computer pool

-----

I check :

- Use a single FQDN & IP

-Enable federation ( port 5061 )

-The external IP address of this edge pool is translated by Nat

-----

external fqdn : sip.OurCie.com / 5061 Port

Internal IP : 192.168.16.57

External IP ( for sip access, web conf, A/V Edge services )  : 192.168.18.80

Public IP used by nat : 69.70.xx.xx

=====================

So when I start the service I have this error code :  Windows could not start the Lync Server Access Edge....code : 1008124918

in the eventvwr here is ther error that I have :

Transport TLS has failed to start on local ip : 69.70.xx.xx at port 5061

cause: config error, low system ressources or another proram is using this port

can also happen if the ip address has become invalid

---------------------------------------

Any idea ?

• Edited by philzs Wednesday, September 28, 2011 3:30 PM

Hi every body, I am trying to do  a proof of concept before we buy the public Certificate for my Edge server but I have this error..

I have the same error as you guys (1008124918 )

Here is my setup

Active directory with a CA on it. ( I used this CA for my Front-End, and for both Internal/External Edge Certificate )

FrontEnd ;

-In the domain

-192.168.16.55 255.255.255.0

==

Edge:

Inside NIC : 192.168.16.57 255.255.255.0, no gateway

Outside NIC (dmz ) : 192.168.18.80 255.255.255.0   . Gateway 192.168.18.0

The edge is not in the domain.

==

My Public IP : 69.70.xx.xx

=====================

In the wizzard for the edge-pool

I choose:

-Single computer pool

-----

I check :

- Use a single FQDN & IP

-Enable federation ( port 5061 )

-The external IP address of this edge pool is translated by Nat

-----

external fqdn : sip.OurCie.com / 5061 Port

Internal IP : 192.168.16.57

External IP ( for sip access, web conf, A/V Edge services )  : 192.168.18.80

Public IP used by nat : 69.70.xx.xx

=====================

So when I start the service I have this error code :  Windows could not start the Lync Server Access Edge....code : 1008124918

in the eventvwr here is ther error that I have :

Transport TLS has failed to start on local ip : 69.70.xx.xx at port 5061

cause: config error, low system ressources or another proram is using this port

can also happen if the ip address has become invalid

---------------------------------------

Any idea ?

• Edited by philzs Wednesday, September 28, 2011 3:30 PM

hello,

can you confirm what was actually wrong with the assignment of the External IP address.

I have the same issue, but believe I have both IP addresses enabled correctly.

 

Dale

What he said. What was the problem with IP addresses?

Thanks,

Andrew

I have similar issue, two of edge service fail to start. I added AV Webconf and sip address in my external interface and all started without any issue.