How do I configure my network to work with a Superscope?

waco_muse used Ask the Experts™
I have a single DHCP server running Windows Server 2003, currently using the range for clients on a single, physical network. I created a superscope and added the range. I then added the additional TCP/IP address of on the NIC of that server… and now I’m at a loss of what to do next.

I need to ensure that the DHCP server is handing out addresses for both ranges, and that traffic can pass from range to range, and also to the Internet.

I am guessing at this point, but believe I must configure our SonicWall router somehow.

I did connect a laptop to the network and assign a static 10.20.8.X address.  From that computer, I can ping, which is assigned as a secondary address on the DHCP server, but that is it – I cannot ping any 10.20.7.X addresses or reach the Internet.

If it helps, the DHCP server does have a secondary NIC, which is currently disabled.

Thanks for your help.

(Also - I'm not sure how many points to award, so I'm leaving it at 500. If that is not proper, then please advise).
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®


I forgot to mention that the 10.20.7.X range and all clients are working properly. So I haven't managed to break anything... yet.
Without vlans, you need 2 nics and 2 switches. and install routing and remote access and it will route between the networks.


So, what you are saying is that, without a vlan, I would need to activate the second NIC in the server, assign to it, then... you lost me.

You wouldn't draw a diagram for me, would you? ;-)

Or, would it be best to use a vlan? Of course, I'll have to add how to do that as another question.
Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

Do you want two separate LANs, or just more hosts on the same LAN?  If the latter, just change the subnet mask to and you'll have a LAN network from


I thought someone might mention that, jimmyray7. My primary goal is to increase the range of usable IPs, but I will have to do some leg work to find out which devices have static IP/Subnet info set. I was hoping the Superscope would work, thinking it would be a bit more seemless.

I'll have to think through it, but will leave the question open for now.

I think changing the netmask would be less work overall (and less likely to cause future headaches).  

However, you can do what you are proposing.  Depending on the sonicwall device that you have, you can either include the new network on the LAN interface and create access rules to allow both networks to talk to each other
On smaller/older sonicwalls, use one of the additional interfaces for the new network, assign it to the LAN zone, then set up rules to allow the networks to talk to each other.  

If it were me, I'd change the subnet mask on the DCHP server, find the static IPs with a network scanner (it can't be that many, only 254 hosts), and you don't have to mess with routing between networks.  

BTW, one correction to my previous post, with a /23 netmask, your network would be from
jimmy is right, i didnt not know what your end result was. what current subnet mask are you using?


I have been exploring the different ways to get the same (or similar) results, and it seems as though changing the subnet mask is going to be the easiest way.

I am, however, too stubborn to let go of Superscopes. So… I’ll be playing with the concept in a test environment, just to see it through.

Thanks for your help everyone.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial