Portal access lost while connected to external gateway

[joshuahill9]

This is a GP configuration that works, but the portal doesn't respond to web requests from the client while the client is connected to the gateway. There is only an external gateway. The portal and gateway share the same IP on an Internet-facing interface. Clients connect and work fine, but as a result when a user initiates an upgrade of the client in the session, the upgrade hangs because it cannot get to the portal's web interface. There is a route to the portal/gateway IP via the un-tunneled Internet in Windows. Where do you think the problem might be? I am certain traffic to that IP has to go over the un-tunneled Internet, but why would the portal remain silent to web requests during gateway sessions? A workaround may be to give the portal and gateways dedicated IPs, but everything I read is that they should be able to function with the same IP. 

[joshuahill9 · Accepted solution]

OK even though GP adds a static route to Windows pointing it to the Internet when the host wants to go to the portal IP, if that portal IP is not excluded from the gateway here: (gateway->agent->clients settings->config->split tunnel) then GP will still try to push the traffic over the tunnel, which seems to be the problem. I excluded the IP, and for good measure the exact domain name of the portal, now a connected GP client can still reach the portal web address and update the client.