Solved

Problems Connecting to Citrix Access Gateway from Internal VLAN

Posted on 2014-04-29
8
580 Views
Last Modified: 2014-07-10
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
Comment
Question by:scfowler
  • 4
  • 4
8 Comments
 
LVL 21

Expert Comment

by:robocat
ID: 40031707
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
 

Author Comment

by:scfowler
ID: 40032281
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
 
LVL 21

Expert Comment

by:robocat
ID: 40032618
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
 

Author Comment

by:scfowler
ID: 40033070
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
Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

 
LVL 21

Expert Comment

by:robocat
ID: 40035508
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
 

Author Comment

by:scfowler
ID: 40035805
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
 
LVL 21

Accepted Solution

by:
robocat earned 500 total points
ID: 40036572
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
 

Author Closing Comment

by:scfowler
ID: 40188283
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

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
DNS @ Naked Domain Record 5 64
Microsoft VPN Client error 7 29
Looking for good easy switch for lab at home. 13 83
VIRTUAL NETWORKING 3 28
#Citrix #Citrix Netscaler #HTTP Compression #Load Balance
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Windows 10 is mostly good. However the one thing that annoys me is how many clicks you have to do to dial a VPN connection. You have to go to settings from the start menu, (2 clicks), Network and Internet (1 click), Click VPN (another click) then fi…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now