Hi, guys how are you doing?

I am new for linuxquestions website and i have several questions regarding WINDOWS server 2003 and i have no experience about how to configure DHCP server with GateWay

1. during the configuration of DHCP from the server, can i include the server IP Address in the Range of address that the scope Distributes? and what if i exculde from the range of IP Address that the scope distrubites?
2. My server IP Address is 10.62.0.1 ( calss A ) and the Router to be configured IP Address is 192.168.1.1 ( calss C ) that is (G.Way) which is DYNAMIC IP-ADDRESS. SO, is it possible to configure this class C gateway in to calss A, IP Address?

3. If the DHCP is already configured from the server, and Aoutorized that means i have now DHCP server and DHCP client. so, what would happen to the client if i removed and reinstalled again the DHCP?

Please Guys i need your help?


THANK YOU VERY MUCH AND GOD BLESS YOU

This is a LINUX forum, you might want to try a Windows forum!

1. In general terms you must exclude any IP addresses within the scope that you have manually configured onto devices.
2. No you can't give a class A host a class C gateway, it breaks the basic rules of IP. The configured gateway must belong to the same IP network as the host, with the same mask.

3. If you remove and re-install the DHCP, the client will retain the IP it was given until it is reset or its lease expires. When it renews the new server will learn about it.
Other devices will ping the offered address before accepting it, so it shouldn't matter that the new server is unaware of existing leases until they are renewed.

1. You can include the server address in a DHCP range, but why would you? You should have a separate range of addresses blocked off for static use (things like printers, servers, etc., which need to stay the same).
2. Yes, addresses can be routed wherever you'd like, as long as you have a path.
3. The client would keep the address, until the lease time expired. It would then try to renew the lease, by contacting the DHCP server. If it couldn't find it, bad things happen.

Also, this is LINUX questions....you say you're running a WINDOWS server. You may want to contact Microsoft for help with their DHCP offerings.

Thank you very much Guys, but for question number 2, TBOne says i can configure any calss gateway as long as i have a path. so, do you think that the G.Way will work in DHCP CLIENT?

Well, I said you can configure what you want, but you need a PATH from point a to point b. But baldy3105 is right on the money with his answer to point 2.

And again, this is LINUX QUESTIONS...you're asking questions about a WINDOWS server. Try a Windows forum.

Well, we're both right, two halves of the same story. To clarify, you can route packets to anywhere from your client, as long as you have a route that points the way. For the client the default-gateway is the first hop in any path to anywhere except the local ip network which the client accesses directly. The client must be able to communicate with the gateway to send packets to it for routing, so the gateway (or router, under IP they are the same thing) MUST share an ip subnet with the client, so that the client can give it packets which it has to forward on to other networks.

So for a network of 10.2.2.x you might define a dhcp scope of 10.2.1.1 to 10.2.1.254 for your DHCP scope. If your gateway on this network is 10.2.1.1 then this would need to be excluded from this scope. Different kit does this in different ways. In Cisco you define a network and exclude static addresses for example. If you have lots of network to play with you might keep 10.2.0.x for routers, 10.2.1.x for servers 10.2.2.x for DHCP clients etc.

So in my example if your client is going to be offered an address of 10.2.1.2, the gateway 10.2.1.1 that I assigned must be specified in the scope as the default gateway, so that the host can find it, and its address must be excluded from the DHCP range to be offered to the clients. The gateway, (be it a router or a server which also routes or a L3 switch or whatever) then needs to have routes to the other networks to which that hosts wants to communicate.

Obviously for another host on the opposite side of the router the whole configuration must be similar for bidirectional routing.

Just remember all hosts on a subnet must share the same mask. The default gateway must be in the same network as the clients it needs to route for.

There are (as always) exceptions to these rules, but you need to know what you are doing if you try to invoke them or you will kill the network dead.