Hi all,
I last properly dabbled with Lync in 2010 and am looking at a 2013 lab.
Ive set it all up and published the topology without issue but I wanted to check Edge and external access (not necessarily federation).
I put two NICs on my edge server and left it in a workgroup but change the DNS suffix to match the internal domain.
The 1st NIC is the internal network NIC
The 2nd NIC is for the external stuff and has 3 ips attached to it
Lets say internal NIC is 10.10.10.1
External is set as 10.40.40.40 (access), 10.40.40.42 (webconf), 10.40.40.44 (AV)
My question is, what do I need to do the NICs as there seems talk about setting persistent / static routes. Internal Lync clients work fine.
I created a Win7 VM not domain joined, and plumbed into the HOST file that sip.domain.com should point to 11.11.11.1.
11.11.11.1 is the router address which PFSense NATs to the edge server 10.40.40.40. and the lync client is manually configured to use sip.domain.com.
Am I in the right direction for testing?
I last properly dabbled with Lync in 2010 and am looking at a 2013 lab.
Ive set it all up and published the topology without issue but I wanted to check Edge and external access (not necessarily federation).
I put two NICs on my edge server and left it in a workgroup but change the DNS suffix to match the internal domain.
The 1st NIC is the internal network NIC
The 2nd NIC is for the external stuff and has 3 ips attached to it
Lets say internal NIC is 10.10.10.1
External is set as 10.40.40.40 (access), 10.40.40.42 (webconf), 10.40.40.44 (AV)
My question is, what do I need to do the NICs as there seems talk about setting persistent / static routes. Internal Lync clients work fine.
I created a Win7 VM not domain joined, and plumbed into the HOST file that sip.domain.com should point to 11.11.11.1.
11.11.11.1 is the router address which PFSense NATs to the edge server 10.40.40.40. and the lync client is manually configured to use sip.domain.com.
Am I in the right direction for testing?