#PULSE DESKTOP CLIENT WINDOWS#

#PULSE DESKTOP CLIENT WINDOWS#

To be complete, the route output under Windows looks as normal as could be. I found out what the problem was but it wasn't fun. Xauth access-profile DYN-VPN-access-profile Pre-shared-key ascii-text 'XXX' # SECRET-DATA

Session ID: 6802, Policy name: DYN-VPN-policy/6, Timeout: 4, Valid Session ID: 6791, Policy name: DYN-VPN-policy/6, Timeout: 2, Valid Session ID: 6781, Policy name: DYN-VPN-policy/6, Timeout: 2, Valid Session ID: 6406, Policy name: DYN-VPN-policy/6, Timeout: 46, Valid Session ID: 6403, Policy name: DYN-VPN-policy/6, Timeout: 42, Valid Session ID: 6401, Policy name: DYN-VPN-policy/6, Timeout: 36, Valid

Session ID: 6396, Policy name: DYN-VPN-policy/6, Timeout: 26, Valid It just seems like there is something blocking the packets going from the Windows machine back to the VPN client but the default trust-to-untrust rule should take care of that and also doesn't explain why it works for the UNIX appliance. Displaying security flow session indicates 192.168.3.100 does get an ICMP but it's not returned to the VPN client. Within the Windows machine I can access J-Web through 192.168.3.254. I also noticed if I attempt to access J-Web through vlan.0's router IP (192.168.3.254) I get the same response as though I'm accessing through the WAN. I'm not too concerned if hosts in vlan.0 can't ping hosts in vlan.72/vlan.82 at this time.

When logged into the UNIX appliance, I can ping all resources in vlan.0, but not the routers at vlan.72/vlan.82. If I login to the SRX I can ping all resources. I have set vlan.0's entire /24 in remote-protected-resources. I can ping the UNIX appliance, but I can't ping the Windows machine. Once I connected as 192.168.4.104, I can ping all 3 subnets' routers. I have 3 subnets in my trust zone, each on a different VLAN. After adding the interface I could connect. Initially the Pulse client returned error 1804 'Connection method doesn't allow concurrent connections' and the SRX on the WAN side won't resolve to (redirects to The problem was 'system services web-management https' did not contain the untrust interface. I'm experiencing a perplexing Dynamic VPN issue with my SRX running 12.1X46-D71 using the straightforward example at.

Pulse desktop client