I'll make note of the performance concerns, but for the existing IM/presence deployment that should not be a concern, correct?
I made the change Michael referenced above, but the Lync 2013 client on my Samsung S3 still won't connect when using the Cisco Anyconnect client 3.0.09156. But my laptop using Cisco Anyconnect 2.5.6005 will allow Lync 2013 to connect. Details:
S3 using WiFi, connected to "BC" SSID
interface: WLAN0
IP: 192.168.88.31
Gateway: 192.168.88.1
Mask: 255.255.255.0
DNS1: 192.168.88.1
DNS2: 0.0.0.0
After connecting to VPN, additional interface listed:
Intrface: CSCOTUN0
Inet Addr: 192.168.255.119
P-t-P addr: 192.168.255.119
Mask: 255.255.255.0
*****
Laptop using WiFi, connected to "BC" SSID
Wireless
IP: 192.168.88.236
Mask: 255.255.255.0
Gateway: 192.168.88.1
After connecting to VN, additional interface listed:
Local Area Connection 3
IPv4 address: 192.168.255.113
Mask: 255.255.255.0
Gateway: 192.168.255.1
*****
So both VPN clients are receiving the same client IP range. When connected to VPN from the S3, I can browse to internal Windows server shares.
We have a single forest single domain, but have multiple SIP domains. These are the mobile Lync sign-in values I'm using:
Sign-in address: [My SIP address]
Password: My domain password
Auto-Detect server: Off
User Name: NetBIOSDomain\username
Internal Discovery Address:
https://lyncdiscoverinternal.domain.com/autodiscoverservice.svc/root
External Discovery Address: fake FQDN because it won't accept a blank field
HTTP Proxy: [We use ISA2006 as an internal proxy, I have this configured with my domain credentials]
Using the above settings, it will not connect. If I change it to auto-detect the server it still fails to connect. So since it works from the laptop going over the same network, I have to think that it's either the mobile client or missing settings some
where.
I cannot get the Lync Connectivity Analyzer to do anything but crash upon startup, and I'm trying to get that resolved for more insight. When connected to VPN, my S3 can ping the internal discovery FQDN listed above, average latency is 32ms.