This message was deleted.
# citrix-netscaler
s
This message was deleted.
c
Multiple interfaces or just one?
b
On the Palo? Two external ISPs on separate interfaces I have the netscaler setup in the DMZ only.
1 interface on the netscaler.
c
on the NS, just checking. One interface makes it pretty easy. You're NATting a public address on the Palo through to a DMZ address on the NS?
b
yup
c
That's about as simple as it gets. Run any packet traces yet?
b
I'm pretty green to the netscaler, can I do that on the netscaler?
c
actually, before we do that, did you add a default route pointing to the Palo?
b
yeah, 0.0.0.0 points to the DMZ gateway x.x.x.1
c
OK, does that gateway eventually go through the Palo?
b
yes, it's an interface on the palo
c
OK cool.
Go to System -> Diagnostics -> Start New Trace. Change Packet Size to 0 and hit start, then try to hit the public IP a couple times then come back to that page to stop and download it. That should let you see if any SYNs are getting through.
If you don't see any SYNs then the rules on the firewall are messed up somehow. If you see SYN/ACKs sent from NS in reply then check a trace on the client side to see if they're getting back to the client.
If the SYN/ACKs aren't getting back to the client then the Palo may be dropping them, again usually a rule issue.
b
This probably isn't good.
c
Ok so those are SYNs going outbound, probably monitor traffic. What you want to do is filter on your client’s WAN IP address.
Are you testing from your internal network?
Well I’m assuming that anyway since I can’t see the IPs. Is the source of the SYN traffic the client or a NetScaler owned IP?
b
The client, I'm running the client from our WIFI which has not connection to our internal network. Source is the external IP of our wifi, destination is the VIP of the gateway.
I had this all working on our watchguard firewall. But we swapped over to the Palo over the weekend. I'm wondering if I should just start from scratch and wipe the config, start over.
c
Sorry, it's been crazy busy. So just to be clear, the packet trace shows client PC WAN address sending SYNs to the DMZ "inside" address of the gateway, right? And the gateway virtual server with that address is showing green/up and has an SSL cert bound?
b
No problem! Thanks for the help. That's correct, as far as I can tell.
@CTXMike I was able to get the gateway website to work internally. My network guys are working on figuring out why it's not coming up on the external side. I ended up clearing the config twice before I got it to work. Thanks again for your help!