[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 593
  • Last Modified:

Problems Connecting to Citrix Access Gateway from Internal VLAN

We have a Citrix Access Gateway that can be reached from all the VLAN's within our internal network except for one. The VLAN in question can ping any other host in the CAG's VLAN, however it can't ping the CAG itself.

We have a core switch, which is an HP 5412, that handles all of our VLAN's and as far as I can tell from the config there shouldn't be anything preventing the traffic from getting through. I suspect that the issue may be caused by a setting on the CAG itself, however I'm not familiar enough with the appliance to know where to look. The CAG software version is 5.0.4.

Any ideas or suggestions would be greatly appreciated!
0
Scott Fowler
Asked:
Scott Fowler
  • 4
  • 4
1 Solution
 
robocatCommented:
Is the device connected to the network by more than one network port (e.g. one port for the internal LAN and one for the DMZ)?
0
 
Scott FowlerAuthor Commented:
Yes, that's correct. One NIC is connected to the internal network on our Default VLAN and the other NIC is connected to the DMZ.
0
 
robocatCommented:
The problem is likely to be routing related. You need to add the IP subnet (from the VLAN) to the routing table and make sure it's routed through the internal NIC.

Look for the network -> routing settings in the management interface, you'll probably see how it's done for your other subnets. Add an entry for the subnet with gateway to the internal net.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
Scott FowlerAuthor Commented:
Thanks for the help robocat...

I was able to find the routing section on the CAG that you referred to. Contained therein are static routes to all of our internal VLAN's, including the VLAN that can't connect to the CAG. Just in case it was entered incorrectly , I went ahead and deleted and re-added. Unfortunately, still no joy.

In doing some further testing I found another VLAN that won't talk to the CAG. This particular VLAN we use exclusively for printers and copiers, so there would never be a need for a device on this network to connect to the Citrix Gateway. Still, it's also in the static routes section on the CAG, so it seems like it should be able to connect as well.
0
 
robocatCommented:
Try using traceroute to see how far you get from the source device to the CAG. It might give you a clue where the problem is situated in your network. Compare that to a traceroute from a working subnet.
0
 
Scott FowlerAuthor Commented:
There's only one hop between the problem VLAN and the CAG VLAN. So a tracert  hits the default gateway and gets a response, but then gets a request timed out when trying to talk to the CAG.

By digging some more into the static routes I think I may have found the problem...

Even though we've added static routes for all our VLANs to the Web GUI of the CAG, if you console into the CLI, there are two routes that don't show. The two routes that don't show are the two VLANs we can't access the CAG from. Unfortunately, as far as I can tell, there's no way to add static routes through the CLI. Looks like this problem may be a bug in this particular version of the software.
0
 
robocatCommented:
Perhaps a reboot could cause the device to re-read the entire routing table?

Something you could also try: delete and add the route again. Immediately after, check the CAG log files for any errors.
0
 
Scott FowlerAuthor Commented:
It turns out that it was an issue with the device itself. We've since replaced the CAG with a Netscaler VM and everything is working as expected. Thanks for the help robocat!
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now