Skype for Business: Using the Big IP as my Default Gateway

Hey Mike, I have not yet made it to the Edge server deployment, I am still working on internal. Just FYI, I initially had internal working for IM, presence, and screensharing, but i wanted to revisit https://www.f5.com/pdf/deployment-guides/microsoft-skype-for-business-dg.pdf page 8 item c to ensure that I am properly set up for internal AV services before continuing on to the edge services deployment. (I needed to ensure that SNAT was not happening)

I followed the Fast L4 profile and virtual server steps EXACTLY, and then set up a route. The Route is setup so that Destination and netmask are both 0.0.0.0, the resource is set to use a gateway, and the gateway address is the router address on that VLAN (which is the address that works for my Front End servers when i set their default gateways to this same address).

Finally, in reference to part of your question, there are no static routes set on any of these servers, they solely use whatever default gateway I have set. I did test this several times, everything stops functioning on the client side as soon as i change the default gateway to the F5, even if I wait up to 30 minutesand try to sign in again. But as soon as i change the gateway over to my firewall as it used to be, i can immediately sign in again.

Is there any more info i could give that would help get to a resolution with this?