Problems setting DHCP scope 3

[bookser]

I am having problems setting the scope on my DHCP server. Here is the scenario. I am running a WIN2K server on my LAN. I have a block of 25 IP addresses provide by my DSL provider. The server was given the first IP in this block x.x.x.162. When I go into the Scope properties to set the DHCP scope of x.x.x.163 (Start) to x.x.x.187 (End, I get the following error. "The specific range either overlaps an existing range or in not valid." Why am I getting this error? Any help would be greatly appreciated. Thanks

Brad

 

[FaiTHLeSS]

Set the 1st IP of the scope to x.x.x.162 then put an exclusion range in that contains the x.x.x.162 and maybe a couple of other IPs this allows you to have static IPs on your network aswell and it wont conflict with your scope.

 

[bookser]

I'm still getting the same error.

The specific range either overlaps an existing range or is not valid.

 

[GrnEyedLdy]

What subnet mask are you using?

Just curious, but why are you handing out Public IP addresses. Why not use Internal addressing with NAT or ICS.

Patty

 

[bookser]

I want to setup an internal Domain for my organization.

 

[GrnEyedLdy]

What subnet mask are you using? You are obvioulsy overlapping two address ranges.

Patty

 

[bookser]

SNM 255.255.255.252

 

[GrnEyedLdy]

With that subnet mask your Network ID will only accommodate 4 client addresses. You are trying to put in 25.

 

[bookser]

Thanks Patty. I changed the scope SNM mask to 255.0.0.0. It works now. Thanks again

 

[Whoheard]

Patty nailed it perfectly...BRAVO. Basic subnetting is the rule here.

You can have a scope of any range within your assigned subnet, but you cannot cross subnet boundaries. For example: Network ID 192.168.1.0 SNM 255.255.255.0, range of addresses available is only 192.168.1.1-254. You cannot have an address above or below that range without changing SNM.

The range of IP's and the SNM you specified covers 8 network IDs: 160, 164, 168, 172, 176, 180, 184, and 188.

You would need a SNM of at least 255.255.255.224 to cover that range. Ask you ISP to verify the SNM again. They could be doing something weird, but I doubt it.

As for your network range in the scope, you do not have to use all the addresses in the scope. Using the same example as above, you can: 1.) choose 50-100 or 100-200 or whatever you need; 2.) put all the addresses in the scope and then exclude any that need to be excluded. And, you cannot have more than one scope from the same network ID, ie. 50-100 and then 110-150.

FYI...

Like Patty said...Why are you using public IP's when it is not necessary?


Hope this helps.

bob


I know what I know and that's all I know.

 

[ricpinto]

STAR for you Patty, you deserved it.

 

[GlenJohnson]

Patty strikes again. Way to go.



Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us


Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Ask a question and you are a fool for one minute. Don't ask a question and you are a fool forever."
Chinese Proverb.

 

[bookser]

I'm still learning, so coming to tek-tips has been very helpful. Thanks everyone.

 

[tonyynot]

Can someone please explain this to me: "you cannot have more than one scope from the same network ID, ie. 50-100 and then 110-150."

I've noticed this, but I can't think of a reason why it would be this way. Thanks.

 

[Whoheard]

If you try and configure a second scope using the same network ID with MS, you will get a message telling you that it already exsists. Try it.

If you already have a scope for a network ID on a server, why would you want to create another one?

You can create a second scope on another server for redundancy, but it cannot have the same range of addresses available. This can lead to duplicate address being on the network--not good.


bob

I know what I know and that's all I know.