cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1019
Views
0
Helpful
1
Replies

ASA5512 after resubnetting, can't see computers on new subnet through VPN

Boutwell Owens
Level 1
Level 1

Hi all, I'm a beginner.  We have a ASA5512X.  Recently I resubnetted our network from 255.255.255.0 to 255.255.254.0.  In the firewall I changed all subnets that were 255.255.255.0 to 255.255.254.0 and applied them.  At this point I can see nothing in the firewalls configuration that says 255.255.255.0 anymore but maybe I missed something in an obscure place (I checked all NATS and Objects). 

 

At night we have users that connect through Cisco VPN of our ASA5512X to our network and then use remote desktop to control their work computers.  If the users work computer is on the original 192.168.1.x network they can remote desktop fine to their work computer.  HOWEVER, if their work computer gets a lease in the new range of 192.168.2.x they can't remote desktop to it through Cisco VPN. 

 

Where do you think I need to look at or missed?  I use ADSM for our firewall settings.  Thanks

1 Reply 1

Hi,
That won't work. If the original network was 192.168.1.0/24 then changing the subnet to 255.255.254.0 (/23) will not include the 192.168.2.0, that's a different network.

2 options:-
- Change the network object/NAT etc to 192.168.0.0/22, this will include the range 192.168.0.1-192.168.3.254 (obviously bigger than your current network, but will include all the networks).
- Add and additional network 192.168.2.0/24 (255.255.255.0) to the ACL and NAT etc to cover the new network.

HTH

Review Cisco Networking for a $25 gift card