troubleshooting Question

New superscope not assigning IPs from new subnet

Avatar of journeyed
journeyed asked on
Hardware FirewallsDHCPCisco
10 Comments1 Solution572 ViewsLast Modified:
Good Afternoon all,

We had a single Win2K3 DHCP server setup with a scope of 172.16.42.100 - .205/24, and are using a Cisco PIX 515e as both our firewall and our default gateway.  Well, like everyone else here, we were  running out of IP addresses for it to assign.  So I thought I would setup a superscope and add another subnet.  The new member DHCP scope is 172.16.43.1 - .254/24, with an exclusion range from .1 - .10.  Well, I was able to create the superscope, but when I try to assign a static address on a test system within the new .43 network, it can't see anything.  It can't even ping the gateway.  Between the client and PIX, there are no routers, just switches, and I'm thinking this is where the problem is.

Am I correct in assuming that the PIX would have to have an IP address from the new network and the DHCP relay turned on in order to forward packets between the two networks?  And that I would need an additional NIC in the PIX for this as the PIX can only handle one IP address per NIC?

Thanks in advance for your help!
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 10 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 10 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros