1. Problems with subnetting a network:
- Biggest problem is creating a complicated and complex envirnment for no real reason. Some of the factors to include in the decision making process:
- how many PCs/hosts in the environment
- how many physical locations
- accessing resources on a different subnet
- providing Internet access
If you are working with a small (less than 100)number of PCs/hosts, the I'd say subnetting is not really useful.
2. Do you mean the same machine, or the same IP address as the default gateway? If you mean machine (acting as a gateway), then yes, as long as that gateway machine is connected to each subnet and has an IP address that belongs to each subnet. If you mean IP address, then no. IP hosts need to be able to communicate directly with their gateway address. If the gateway address is on a different subnet, they will never be able to communicate with it.
3. You should have no problem using your existing equipment, you'll just have to erconfigure IP addressing to work with a subnetted environment (re-assign IP address, re-create DHCP scopes, etc. etc.)
4. You have a couple of choices when it comes to DHCP:
- place a DHCP server on each subnet. DHCP requests are broadcast, and when you subnet your network, broadcasts will be stopped by the routers in your network. Also, putting a DHCP server on each subnet ensures that hosts will receive an IP address for the subnet they reside on.
- work with DHCP relay agents. If you only want one DHCP server to serve all subnets, each subnet will require a DHCP relay agent, which will forward all DHCP requests directly to the DHCP server. Otherwise, you will need a BOOTP-compliant router, which will allow DHCP broadcast traffic to pass through it.
Cheers,
Shawn