Link to home
Start Free TrialLog in
Avatar of jskiba
jskiba

asked on

Net Mask

I know I'm going to feel like a moron when I hear the answer but...My sonicwall LAN interface is set up to 10.0.0.x / 255.0.0.0 but my machines are using 101.0.0.x with a netmask of 255.255.255.0...I didn't set this up , but it doesn't seem to make sense. Am I missing the logic behind this configuration? Also, if it is wrong, how do I change it? I'm not sure how the networked machines are picking up this netmask.
ASKER CERTIFIED SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jskiba
jskiba

ASKER

What a fast response! Thank you.
The internal netmask used to be 255.0.0.0 which made subnetting easier. This is how I found the issue. I want to set up a subnet separate from the LAN with internet access only. Of course, when I try to create an address pool of 10.0.2.x on subnet 255.255.225.0, my Cisco WLC gives me an IP misconfig error.

I'm wondering where I set the default internal netmask to 255.0.0.0

Of course, I admit I might be way off in my way of thinking. Maybe I can get a quick education here.
Can you explain how large your network is, why you need some on the internet, some off and in general, just be more detailed?  We don't necessarily need every tidbit, but I have no idea if your lan is for 10 people 10,000, if you use Windows systems or Linux or Mac or something else entirely, etc.
Avatar of jskiba

ASKER

Sure
it's a small virtualized network with 5 servers and 50 clients. However, we have a wireless guest network that will occasionally need to support up to 150 connections during large events.

Windows 2008 server
DPM server on a Dell box
all windows clients

I realize I don't need all the addresses that a 255.0.0.0 mask would allow, but I don't want to reconfigure the DHCP pool for the entire network.

We have a second organization in the facility that leases from us and shares the T1. They are on a class C network (192.198.1.x) and I don't administer their network. So I think my predecessor might have set up our addressing to avoid conflict...but there's no way to tell.