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
brad_11480's avatar
brad_11480
Icon for Nimbostratus rankNimbostratus
May 22, 2015

i have a similar problem. servers need to connect out to clients across F5 Edge. The clients are able to connect to servers just fine, but if the server tries to initiate a connection it does not make it.

 

i can't even connect from the F5 itself to the client (ping or telnet to a listening port). I did the 'reserve strict port' above. nope.

 

then i created a virtual server to route to that pool subnet. nope.

 

yes, these pool IP's are routed and there is no SNAT.. so the client IP is what arrives on the servers, etc.

 

i have a case open. to me it should just work. something must be missing.

 

  • Mark_129802's avatar
    Mark_129802
    Icon for Nimbostratus rankNimbostratus
    Jun 08, 2015
    Did you ever get a fix for this Brad? I'm in the same boat, everything works fine Client - Tunnel - Server (etc) However nothing on the reverse, I have my routes in place in our networking gear for the Network Access IP pool... Wonder if I need to add a route on the F5 itself for the Client Pool