AltocumulusSo I ended up getting this working by following the steps outlined here under the SMB Configuration Table on page 8
Deploying the BIG-IP system with Microsoft App-V (f5.com)
Works great now!
Thanks for your added help Paulius
MVPLog4j2 Is your F5 in path between the client and destination pool members? If the F5 is not in path then you will most likely have to enable SNAT like whisperer has mentioned. A topology of the path the client takes to get to Virtual Server (VS) and ultimately the pool members would assist in coming up with the correct configuration for your situation. If you enable SNAT you should create a new snatpool with the VS IP in it and use that rather than automap.
AltocumulusPaulius I put together a quick flow of current state and what I'm trying to achieve
In the new flow, the VIP IP is a host entry on all servers known as, for this example, 'vip-alias'.
MVPLog4j2 Based on what you provided this is in path between the source and the destination so you should not need SNAT. What information are you seeing when you perform a tcpdump on the F5. You can try the following to see what you get. This should save the file and then allow you to open it up in wireshark.
tcpdump -nni 0.0:nnp host <vs_IP> -w /shared/tmp/mycapture.pcap
AltocumulusSo I ended up getting this working by following the steps outlined here under the SMB Configuration Table on page 8
Deploying the BIG-IP system with Microsoft App-V (f5.com)
Works great now!
Thanks for your added help Paulius
