All, The fellow who installed Lync has since departed. It's is installed on 2008R2.
I have had to rework the machine's networking a bit, and have configured it somewhat more sanely. It had both pools on NICs with internal IP addresses, both set up with DGs, and one of them on a switch port where the VLAN didn't match the IP address and the switch port was disabled. Ugly. I had to rework the external pool, putting it into our DMZ and readdressing it. The DG is on the NIC in the DMZ, and it is not yet allowed out. I've set up static routes for the internal subnets, so that users inside of the corporate perimeter are able to use it. It worked before I touched it, and it works after I've touched it, except for one thing - I can't open the control panel from the server console, using the FQDN. I can invoke it from my desktop with http://lync.example.com/cscp, but the same URL on the Lync server console just errors out. I can invoke it on the console via the IP address - http://192.168.8.45/cscp - but it takes a *very* long time to load. I've checked the IIS bindings for the internal and external web sites, and they match the NIC address, but can't seem to get into the configuration of the pools. Anyone have a clue what might be going on? Also, more cosmetic than anything else, but really annoying - he set up a pool name as poo01.example.com, and I'd really like to fix that, but I'm still researching it. It's not an active pool, AFAICT, since the status column for it says n/a, and the replication column has a big red X in it. Should I get rid of the pool, or try to modify (is it possible?) the name. Kurt
