Forgive me if this is not the right place to post this, but it's a bit mixed and Microsofty.
We have a dual-NIC ISA Server 2006 running our VPN, and clients were connecting to it fine when we were set up as a flat network, but we've now set up VLANs and the VPN doesn't work as it used to.
Clients can connect to the VPN correctly, but can no longer advance past the firewall onto our network as they used to be able to.
Our server has the following config:
gw: 10.1.1.1 (vlan id 101)
Internal address range to give out to clients: 10.1.10.1-254
When clients connect they receive similar to the following:
ISA Server itself can connect to other servers and workstations on different subnets and VLANS on the LAN, but VPN clients cannot even ping the Internal server address ISA uses (first in range) of 10.1.10.1
Where could we be going wrong? I'm entirely new to segmenting the network in this way and am stumped on this one.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...