We'd love to hear about it! Click here to go to the product suggestion community
In reply to BarryG:
In reply to AngeloC:
In reply to ntomsheck:
Just a quick question, are these servers also using the ASG as their gateway? You seem to have correct configuration. Can you answer these?
1) Whats the IP of the ASG internal interface? Can you ping that? (i think from the above text you can, if that is what your pinging.
2) What's the netmask for your internal interface/lan look like? is your lan just 10.0.0.0/24 with 10.0.0.1 as the internal IP of the ASG interface?
3) if you can connect and ping the INTERNAL interface of the ASG from your VPN pool assigned to you (which you said is the default) then you have a tunnel and permissions are probably correct, especially if you have packet filter rules set to auto. Can you telnet or RDP for example to the client lan, or is it just ping which is lost?
Some more info and we can sort you out.
In reply to BAlfson:
What is the default gateway for the devices in .x.0/24?Cheers - Bob
Is there anything unusual in the Intrusion Prevention log?
Maybe it's time to take a look at the traffic on the remote internal interface with tcpdump from the Astaro command line.
Cheers - Bob
In reply to Tetz:
In reply to number2jcb:
Are you running Windows 7? Is UAC enabled? If so, exit the ssl versions that starts with your profile, and right click and choose: Run As Administrator. See if it works then. I was having a very similar problem. It turned out that the routes were not getting added (showed as error in the status window of astaro client) to the IP tables because a recent windows update made that an Admin only priveledge.