Server 2000 - 2003 DHCP Valid Scope IPs

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I used this page
"http://technet2.microsoft.com/WindowsServer/en/Library/150ddc41-a7e3-4c86-96d1-d706e27116f21033.mspx"
to learn how to create scopes on Windows 2000 servers and set up scopes with
IP ranges of start IP 10.xxx.2.1 to end IP 10.xxx.6.254. This has worked fine
for several years. Last year or so we moved to Server 2003 severs to replace
the old desktop computers being used as Server 2000 servers. Today one of my
co-workers notices that computers are being assigned IPs of 10.xxx.aaa.0 and
10.xxx.aaa.255 (aaa being the respective 3rd octet from 2-6 for the scope).
He literally had a fit and told me that those IPs were not valid IPs I
pointed out to him that they have been working for several years and that the
TechNet document said noting about having to exclude these IPs, I also told
him I would more than happy to change the scopes if it was necessary. So,
what should I do? I have 14 DHCP servers with the same scope per their second
octet gateway.
 
If your subnet mask were 255.255.255.0, then a 4th octet value of 0 or 255
would not be a valid host address. However, where the host portion of the
address includes part of the 3rd octet as is the case for your scopes, then
the 4th octet may have a value of 0 or 255 - ie. when dealing with such
scopes, a 4th octet value of 0 or 255 does not necesssarily mean that the
host portion of the address in binary will be all 1s or all 0s.

I don't quite see the relevance of the super scope article.

Doug Sherman
MCSE, MCSA, MCP+I, MVP
 
KoJawn said:
I used this page
"http://technet2.microsoft.com/WindowsServer/en/Library/150ddc41-a7e3-4c86-9
6d1-d706e27116f21033.mspx"
to learn how to create scopes on Windows 2000 servers and set up scopes with
IP ranges of start IP 10.xxx.2.1 to end IP 10.xxx.6.254. This has worked fine
for several years. Last year or so we moved to Server 2003 severs to replace
the old desktop computers being used as Server 2000 servers. Today one of my
co-workers notices that computers are being assigned IPs of 10.xxx.aaa.0 and
10.xxx.aaa.255 (aaa being the respective 3rd octet from 2-6 for the scope).
He literally had a fit and told me that those IPs were not valid IPs I
pointed out to him that they have been working for several years and that the
TechNet document said noting about having to exclude these IPs, I also told
him I would more than happy to change the scopes if it was necessary. So,
what should I do? I have 14 DHCP servers with the same scope per their second
octet gateway.
Click to expand...

1. What is the mask? Telling us the IP# Range means nothing without knowing
the mask. There is no way to get 10.xxx.2.1---10.xxx.6.254 to be in the
same subnet and begin and end at that exact point. Your co-worker's "fit"
was probably very well justified.

2. 14 DHCP Servers? Why? What is a "second octect gateway"? Please use
accuarte terminology so that we know what you mean by what you say,...we
cannot see your system like you can,..all we have are words on a screen.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
-----------------------------------------------------
 
Back
Top