Win 2003 server and configure scopes [assistant network administrator] [network printers]
Q: I am an assistant network administrator at a medium sized school with a Win 2003 server with about 140 PCs, WAPs 35 and 15 + network printers connected. We currently have a scope, 10.0.0.50-10.0.0.254 (or 204 valid IP addresses). As you can see, with 190 customers, plus the few laptops that teachers and various advisors, etc. in, we are running out of IP addresses assign.
My question is: given a different room configuration, say 10.0.1.50-10.0 . 1254, should we configure the clients on that subnet mask 255.255.0.0 space instead of the current 255.255.255.0, the appropriate use? And if that is true, that those customers would be on a network other than the printers and WAPs?
***** UPDATE *****
We a new scope, 10.0.1.50-10.0.1.254, and went to all of our WAPs. We reserved IP addresses for each one and manually configure each on a specific IP address instead of getting DHCP to assign one. Until now we seem to have solved the problem to rectify any day.
There s a new issue now. After moving to the new scope, we can not log WAPs using IE (or Firefox (from any client or server machine itself)) to check the settings of the Configure logs. We used, type the IP address of the WAP, enter the password, and get it right now, when we enter the new IP 10.0.1.xx, it says it does not exist. Is there something in the servers TCP / IP properties we need to adjust?
Any aprecciated advice.
Best Answer: Setting up Active Directory only takes a few momments. However, setting up Active Directory properly can take months of planning.
If you are just trying to set up a test lab, i would first recommend that you purchase some AD books to help you.
In any case, to answer your question. Make sure of the following:
* Assign a static IP to your server that will become a domain controller.
* Configure this computers DNS config to point to itself.
* Click Start, RUN, tyep DCPROMO
* During the installation of AD, the system will detect that DNS is not installed and properly configured. Allow the system to set up DNS for you.
* After the server becomes a Domain Controller, you will be able to join your XP workstation to the domain.
* If you need DHCP services, you will need to install that on the DC, Create a Scope, and Authorize the DHCP Server.
There really is alot more than this, but it would be too difficult for me to type it all out.
Next Generation Network Marketing Handbook
Re:We'd like to be able to assign 10.0.2.xx and 10.0.3.xx more to organize things than to be able to assign 1000 addresses.
I guess tomorrow I'll start configuring all the WAPs and routers to that subnet.
Thanks so much for your help, I know I learned all this in networking class but not enough to know exactly what to do. I'll post back letting you know how it goes and if I need more help.
Getting Administrative Assistant Job
Re:if you want to use the following networks…
10.0.0.0
10.0.1.0
10.0.2.0
10.0.3.0
then your mask would be 255.255.252.0
this gives you over 1000 addresses. if you get over about 300 you may want to look into layer3 switches (routers) to cut down on the number of machines per subnet.
until then, just use the 10.0.0.0 and 10.0.1.0 networks. That is over 500 addresses.
Home Automation & Networking eBook
Re:Originally posted by: guy
if there are no routers separating those two networks 10.0.0.0 and 10.0.0.1 then yes, modify the scope to a larger subnet mask and allocate your addresses from the range 10.0.0.1 – 10.0.1.254.
We have one router between the server and the cable modem. Its IP is 10.0.0.1. The server's IP is 10.0.0.2.
We only have one server – with about 30 WAPs and routers acting as WAPs attached.
If we want to be able to assign 10.0.2.xx and 10.0.3.xx addresses too, we should configure our subnet mask to lower than 255.255.254.0 right?
Social Network Marketing 2.0 – 75% commission
Re:if there are no routers separating those two networks 10.0.0.0 and 10.0.0.1 then yes, modify the scope to a larger subnet mask and allocate your addresses from the range 10.0.0.1 – 10.0.1.254.
The Social Networking Business Plan
Re:Originally posted by: guy
there can be only one IP subnetwork per phsyical layer2 network. Otherwise you'll need a router to route between the IP subnets.
that being said it looks like you just need to increase your subnet mask. If you still want to maintain your current addressing then change the network mask for the 10.0.0.0 subnet from 255.255.255.0 to 255.255.254.0. This will give you a usable address range from 10.0.0.1 – 10.0.1.254.
Make sure you change this on the DHCP server handing out IP addresses. And if you want to make your life easier, setup DHCP reservations for the access points. That way you are centrally controling your addressing. Do the same for printers as well.
You'll also need to change the mask on any and all routers that are attached to this network.
-edit- this is all part of one scope, by creating another scope you are saying "this is a separate IP network" when in reality that is not what you have. you only have ONE IP subnetwork.
also – you have serious problems if you have to reset an access point. there is no reason one should have to do this unless something is very wrong.
You're saying that I should get rid of the 10.0.1.xx scope and modify the 10.0.0.xx scope to be 10.0.0.50 – 10.0.1.254 (and change the subnet mask to 255.255.254) and put everything (computers, printers, WAPs in it)?
I have also created another scope, 10.0.2.xx, and am experimenting with moving printers into it. Should I not do that either?
We have reserved IPs for all access points now, it seems to have solved the problems with needing to reset them. You wouldn't believe how much time I spend restting those things and how stupid I feel now that it seems so obvious.
Network For Success Business Building Intensive (online
Re:there can be only one IP subnetwork per phsyical layer2 network. Otherwise you'll need a router to route between the IP subnets.
that being said it looks like you just need to increase your subnet mask. If you still want to maintain your current addressing then change the network mask for the 10.0.0.0 subnet from 255.255.255.0 to 255.255.254.0. This will give you a usable address range from 10.0.0.1 – 10.0.1.254.
Make sure you change this on the DHCP server handing out IP addresses. And if you want to make your life easier, setup DHCP reservations for the access points. That way you are centrally controling your addressing. Do the same for printers as well.
You'll also need to change the mask on any and all routers that are attached to this network.
-edit- this is all part of one scope, by creating another scope you are saying "this is a separate IP network" when in reality that is not what you have. you only have ONE IP subnetwork.
also – you have serious problems if you have to reset an access point. there is no reason one should have to do this unless something is very wrong.
Dive in Social Network Marketing
Re:Bump, update with new issue in OP.
Extra Strength Social Networking – Sale Price
Re:I went ahead and configured another scope, 10.0.1.50-10.0.1.254 and subnet 255.255.255.0. I put 3 of our WAPs in it and we will be testing over the next week or so to see if this solves our problem.
One of the reasons we discovered this problem is because we have about 10 WAPs that need to be reset weekly, and a few that need it almost daily. If putting WAPs in their own scope/making more IPs available fixes the problem, I will be a very happy person.
NetDepict – 100% Automated Visio Network Drawings
Re:If you use the /16 mask, everything will be in the same subnet. (both 10.0.0.x and 10.0.1.x networks)
Usually you want seperate subnets for infrastructure devices like routers, switches, and WAPs, and a separate subnet for DHCP clients, etc.
Related posts
Tags: assistant network administrator, network printers