Newbie DHCP w/ wireless router setup question

Hello all,

I'm working for a non-prof -- so you can imagine our budget is limited
-- and I'm in the middle of setting up Windows Server 2008
Enterprise. We are moving from a workgroup to an internal AD domain
(we will not have a public name server). I've already installed the
OS and added Active Directory, DNS, and DHCP. My problem is getting
all the components on the network to talk to each other. I imagine
these are all configuration settings somewhere, but I'm not sure what
to tackle first.

Basically, I have a wireless router that currently acts as the DHCP,
firewall, and WAP. (FYI, it has 4 ports besides wireless
capability.) I'd like to set up a 10.0.0.x-type scope with the server
providing DHCP instead of the router. I'd also like to retain
wireless capabilities.

I've tried to turn off DHCP on the router, but then nothing can get to
the Internet. So, here are some more specific questions:

1. I assume I turn off DHCP on the router, correct?
2. In the router admin, what IP address do I give it?
3. In Windows Server, what static IP do I give it?
4. Can I plug in a wired client to one of the router ports and it have
the server assign it an IP?
5. How does a wireless client get on the domain?
6. Do any manual configurations about gateways, DNS's, forwarding,
etc. need to take place on the server? On the client?

That should give me a start!

Thanks!
Tom

Hello Tom,

Do you have any experiemce about networking and active directory and dns/dhcp
and wireless access? Your question doesn't sound like that. This all works
together with a lot more configuration part when building a domain.
Installing is more or less some mouse clicks but then the work is starting
with maintaining and configuring.

A network like 10.0.0.x should use subnet mask 255.255.255.0, this gives
you 254 useable addresses in that subnet:

Host address: 10.0.0.0 (This is a network, not a host)
Network: 10.0.0.0 (Class A, CIDR/8, 254 hosts)
Network mask: 255.255.255.0
Broadcast address: 10.0.0.255
First host address: 10.0.0.1
Last host address: 10.0.0.254

Remove DHCP from the router, that's good. Also DNS should not be run on it
or should use the router.

So in your case use the x.x.x.1 for the router and the x.x.x.10 for the Domain
controller.

On the DC create a DHCP scope starting by x.x.x.50 to x.x.x.80, so you can
provide 30 workstations an ip address. In the scope options configure set
the default gateway to x.x.x.1 and the DNS server to x.x.x.10.

On the server the ipconfiguration of the NIC set like this:
ip 10.0.0.10
sm 255.255.255.0
dg 10.0.0.1
pref. dns 10.0.0.10

DNS for internet access on the server configure according to this one:
http://support.microsoft.com/kb/323380

1. Yes.

2. 10.0.0.1 subnet mask 255.255.255.0

3. see above

4. Yes, if the switch of the router is also connected with the switch where
the server is

5. You need an access point connected to the switch of the LAN

6. Server and client see above

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello all,
>
> I'm working for a non-prof -- so you can imagine our budget is limited
>
> Basically, I have a wireless router that currently acts as the DHCP,
> firewall, and WAP. (FYI, it has 4 ports besides wireless
> capability.) I'd like to set up a 10.0.0.x-type scope with the server
> providing DHCP instead of the router. I'd also like to retain
> wireless capabilities.
> I've tried to turn off DHCP on the router, but then nothing can get to
> the Internet. So, here are some more specific questions:
>
> 1. I assume I turn off DHCP on the router, correct?
> 2. In the router admin, what IP address do I give it?
> 3. In Windows Server, what static IP do I give it?
> 4. Can I plug in a wired client to one of the router ports and it have
> the server assign it an IP?
> 5. How does a wireless client get on the domain?
> 6. Do any manual configurations about gateways, DNS's, forwarding,
> etc. need to take place on the server? On the client?
> That should give me a start!
>
> Thanks!
> To

> Do you have any experiemce about networking and active directory and dns/dhcp and wireless access? Your question doesn't sound like that.

Not too much, but I've done some basic things. We can't afford
anyone, at least no now. So it's on me. I wish I didn't have to ask
these newbie questions, but we gotta do what we gotta do!

> Installing is more or less some mouse clicks but then the work is starting with maintaining and configuring.

As I've discovered!

> A network like 10.0.0.x should use subnet mask 255.255.255.0, this gives you 254 useable addresses in that subnet:
>
> Host address: *10.0.0.0 *(This is a network, not a host) *
> Network: *10.0.0.0 *(Class A, CIDR/8, 254 hosts) *
> Network mask: *255.255.255.0 *
> Broadcast address: *10.0.0.255 *
> First host address: *10.0.0.1 *
> Last host address: *10.0.0.254 *

Is this the configuration for the router, or the server? If the
router, do I really put in 10.0.0.0 as the host address? How does the
server know what the default gateway is? Or how does the router wind
up with the IP address of 10.0.0.1?

> Remove DHCP from the router, that's good. Also DNS should not be run on it or should use the router.
>
> So in your case use the x.x.x.1 for the router and the x.x.x.10 for the Domain controller.

Ok, but where do I assign the router the IP address?

> On the DC create a DHCP scope starting by x.x.x.50 to x.x.x.80, so you can provide 30 workstations an ip address. In the scope options configure setthe default gateway to x.x.x.1 and the DNS server to x.x.x.10.

I'll probably do x.x.x.100 to 254 (just preference), and leave room in
the first 100 for servers (we will have 3 to start). But I do not
need to create scopes for the servers, correct?

> 4. Yes, if the switch of the router is also connected with the switch where the server is

So do I need switches so that my PC can get its IP from server?
Because all I have is my wireless router with 4 ports.

> 5. You need an access point connected to the switch of the LAN

And then the server and wired workstations are also on the switch,
correct?

> 6. Server and client see above

What configuration needs to made on the client? Some folks will be
using their laptops at home and I don't want them to have to
reconfigure their settings once their off our network.

> Best regards
>
> Meinolf Weber

Meinolf, thanks very much for your timely reply. I appreciate it.
Tom

Hello Tom,

It is not a problem with asking the questions, but you have really to understand
what you are doing and not just following steps on steps.


This is NO configuration for the router. As i wrote "network" the list with
the ip addresses is the OVERVIEW over the 10.0.0.0 network with the usable
addresses 1-254, just read the output, that is a sinple overview of what
addresses the netwrok consist.

The router has to be configured on the LAN as decribed in it's manual, i
assume via webbrowser.

The server know's the default gateway over the configured NIC settings.

Servers should always get fixed ip addresses not DHCP. Also they should not
be from the DHCP scope to prevent conflicts.

For wireless clients see here:
http://technet.microsoft.com/en-us/l.../dd183697.aspx

All machines that should work together need physical(wireless) connection
in the same LAN.

If the user workstations use DHCP they can also be used at home from them.
So they can get ip's from there home DHCP without problems.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


>> Do you have any experiemce about networking and active directory and
>> dns/dhcp and wireless access? Your question doesn't sound like that.
>>
> Not too much, but I've done some basic things. We can't afford
> anyone, at least no now. So it's on me. I wish I didn't have to ask
> these newbie questions, but we gotta do what we gotta do!
>
>> Installing is more or less some mouse clicks but then the work is
>> starting with maintaining and configuring.
>>
> As I've discovered!
>
>> A network like 10.0.0.x should use subnet mask 255.255.255.0, this
>> gives you 254 useable addresses in that subnet:
>>
>> Host address: 10.0.0.0 (This is a network, not a host)
>> Network: 10.0.0.0 (Class A, CIDR/8, 254 hosts)
>> Network mask: 255.255.255.0
>> Broadcast address: 10.0.0.255
>> First host address: 10.0.0.1
>> Last host address: 10.0.0.254
> Is this the configuration for the router, or the server? If the
> router, do I really put in 10.0.0.0 as the host address? How does the
> server know what the default gateway is? Or how does the router wind
> up with the IP address of 10.0.0.1?
>
>> Remove DHCP from the router, that's good. Also DNS should not be run
>> on it or should use the router.
>>
>> So in your case use the x.x.x.1 for the router and the x.x.x.10 for
>> the Domain controller.
>>
> Ok, but where do I assign the router the IP address?
>
>> On the DC create a DHCP scope starting by x.x.x.50 to x.x.x.80, so
>> you can provide 30 workstations an ip address. In the scope options
>> configure set the default gateway to x.x.x.1 and the DNS server to
>> x.x.x.10.
>>
> I'll probably do x.x.x.100 to 254 (just preference), and leave room in
> the first 100 for servers (we will have 3 to start). But I do not
> need to create scopes for the servers, correct?
>
>> 4. Yes, if the switch of the router is also connected with the switch
>> where the server is
>>
> So do I need switches so that my PC can get its IP from server?
> Because all I have is my wireless router with 4 ports.
>
>> 5. You need an access point connected to the switch of the LAN
>>
> And then the server and wired workstations are also on the switch,
> correct?
>
>> 6. Server and client see above
>>
> What configuration needs to made on the client? Some folks will be
> using their laptops at home and I don't want them to have to
> reconfigure their settings once their off our network.
>
>> Best regards
>>
>> Meinolf Weber
>>
> Meinolf, thanks very much for your timely reply. I appreciate it. Tom
>

On Feb 18, 4:00*pm, Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>
wrote:
> Hello Tom,
>
> It is not a problem with asking the questions, but you have really to understand
> what you are doing and not just following steps on steps.

Yup, learning as I go.

> This is NO configuration for the router. As i wrote "network" the list with
> the ip addresses is the OVERVIEW over the 10.0.0.0 network with the usable
> addresses 1-254, just read the output, that is a sinple overview of what
> addresses the netwrok consist.
>
> The router has to be configured on the LAN as decribed in it's manual, i
> assume via webbrowser.

Right. So I set the router's IP address (10.0.0.1) in the router
admin (yes, it's web-based) and disable its DHCP service. Right? Any
other router config you can think of?

> For wireless clients see here:http://technet.microsoft.com/en-us/l.../dd183697.aspx

Ok, from what I'm gathering, once I disable DHCP on the router, I will
be unable to use it as a WAP. I'll need to but another one.

> All machines that should work together need physical(wireless) connection
> in the same LAN.
>
> If the user workstations use DHCP they can also be used at home from them..
> So they can get ip's from there home DHCP without problems.

Ok, so by "client configuration" you just meant that DHCP had to be
configured. This is already the default, so I shouldn't have to do
anything.

Thanks again!
Tom

Hello Tom,

The best option is to use the server for DHCP, you have more functionality
with scope options and registering DNS records.

You CAN use the router DHCP when stopping the server, if you have no other
option to provide wireless machines with DHCP addresses.

Make sure the DHCP server is authorized in AD, rightclick the servername
and choose authorize. Takes some seconds maybe press F5 to refresh and after
that rightclick the scope and choose activate.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> On Feb 18, 4:00 pm, Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>
> wrote:
>
>> Hello Tom,
>>
>> It is not a problem with asking the questions, but you have really to
>> understand what you are doing and not just following steps on steps.
>>
> Yup, learning as I go.
>
>> This is NO configuration for the router. As i wrote "network" the
>> list with the ip addresses is the OVERVIEW over the 10.0.0.0 network
>> with the usable addresses 1-254, just read the output, that is a
>> sinple overview of what addresses the netwrok consist.
>>
>> The router has to be configured on the LAN as decribed in it's
>> manual, i assume via webbrowser.
>>
> Right. So I set the router's IP address (10.0.0.1) in the router
> admin (yes, it's web-based) and disable its DHCP service. Right? Any
> other router config you can think of?
>
>> For wireless clients see
>> here:http://technet.microsoft.com/en-us/l.../dd183697.aspx
>>
> Ok, from what I'm gathering, once I disable DHCP on the router, I will
> be unable to use it as a WAP. I'll need to but another one.
>
>> All machines that should work together need physical(wireless)
>> connection in the same LAN.
>>
>> If the user workstations use DHCP they can also be used at home from
>> them. So they can get ip's from there home DHCP without problems.
>>
> Ok, so by "client configuration" you just meant that DHCP had to be
> configured. This is already the default, so I shouldn't have to do
> anything.
>
> Thanks again!
> To

Great -- thanks for all your help!
Tom

Hello Tom,

You're welcome.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm