My ever evolving and expanding local area network is currently using a class-C address. My network consists of multiple subnets depending on site/location.
192.168.1.x is site HQ
192.168.5.x is secondary site
192.168.10.x is third, so on and so forth.
Long story short - I have inherited this network design from the previous admin who has left the company which started off with a dozen people and now has just over 300 full time/part time employees. We do not yet have client VPN access; but we do have site to site VPN setup.
EDIT - to include details concerning my current setup and future planning:
The main and secondary sites (subnets) have 25 physical servers. The branch sites have 5 (each domain controllers). So in total we are expecting this to grow about 50% in the next 3 years.
We currently have a Web Server and Domino Web Mail server facing the public. I have purchased a Cisco ASAs for DMZ, Client Access VPN, and Site to Site VPN to replace our existing off the shelf (Linksys) VPN/router solution. The only changes I see is the replacement of Domino with Exchange (OWA) and I am looking to add a Cisco VPN server accessible on the internet.
In total, DHCP from our main router is leasing out 150 IPs to client workstations on my main 192.168.1.x subnet which also happens to be the same subnet as my main servers. About 100 IPs on multiple subnets for the remaining sites on the other subnets.
Our management "network" (HP ProLiant iLO) is on the main 1.x subnet.
- There are no immediate plans to implement iSCSI SAN or VoIP but these are highly likely down the road.
- Our MFP (printers) are all static IP which probably will need to be remapped if a readdressing happens.
- I want to add guest access WiFi for guests/visitors.
- Client access VPN is on the top of the list of priorities, however.
It looks something like this: 192.168.1.x consists of Servers using addresses 10 to 40. Printers using 40 to 50. Workstations 50 to 200. iLO management addresses using 200 to 250.
My question is, in preparation for outside client access to my network via Cisco ASA, I would like to re-address the HQ site because I understand a 192.168.1.x or 192.168.0.x are not very good choices for a company subnet - it may conflict with a home user's LAN when connecting to my LAN, I believe? Through your experience, does anyone out there have any suggestions and tips on how I can proceed with re-addressing my subnets. If I designed this network I would have gone with a 10.0.0.0 so I am leaning towards changing it to fit. Thank you.