Forum Discussion

pspecht_152507's avatar
pspecht_152507
Icon for Nimbostratus rankNimbostratus
Nov 19, 2014

Cant use windows remote assistance to VPN clients

While testing several of my remote sales employees with the F5 Edge client we found that after they connect, our helpdesk team cannot use remote assistance, remote control, or RDP to the remote sales...
BIG-IP Access Policy Manager (APM)
microsoft
security
ssl vpn
Mark_129802's avatar
Mark_129802
Icon for Nimbostratus rankNimbostratus

I've made my virtual server as per above... however do I need a route table entry on the Big-IP for it to forward to? It seems to forward the traffic now but doesn't have a route to the Network Access clients. I've tried a combination of routes however as the Network Access doesn't have it's own interface no matter where I point it, it doesn't seem to work.

 

Mark_129802's avatar
Mark_129802
Icon for Nimbostratus rankNimbostratus
Jul 06, 2015
It is definitely a routing issue Trace route From Network Access Client to PC on inside Inside Big-IP > Router Gateway > Internal Client From Internal Network to Network Access Client Internal Client > Inside Big-IP > Router Gateway > Inside Big-IP > Router Gateway > Inside Big-IP > Router Gateway > Inside Big-IP > Router Gateway > Inside Big-IP > Router Gateway ... Looping Until it times out. I'm thinking it is hitting the default route of the Big-IP and sending it back the way it came. I just can't seem to figure out how to point the route to that network down the tunnel?