471,071 Members | 1,516 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,071 software developers and data experts.

DHCP & DNS

114 100+
Guys, i have around 8 machines in my office. i do have a server with Windows Server 2003 installed. My server have two NIC- one for the internet and one for my local LAN. I have assigned static address of 192.168.0.1 to one adapter and have configured the global ip in the other adapter. Now i want to configure the server to act as both DHCP & DNS Server.

What i have done so far is that i have assigned default gateway as 192.168.0.1 and dns server also as 192.168.0.1 (pointing to the same machine) while configuring the dhcp server. And while configuring dns i have given the isp's dns address as the forwarders.

So, this is all i have done. And the problem is that the clients do not get ip assigned. it get some other auto ip instead.

Thus, please help me where i am gone wrong!
May 4 '08 #1
2 2029
Guys, i have around 8 machines in my office. i do have a server with Windows Server 2003 installed. My server have two NIC- one for the internet and one for my local LAN. I have assigned static address of 192.168.0.1 to one adapter and have configured the global ip in the other adapter. Now i want to configure the server to act as both DHCP & DNS Server.

What i have done so far is that i have assigned default gateway as 192.168.0.1 and dns server also as 192.168.0.1 (pointing to the same machine) while configuring the dhcp server. And while configuring dns i have given the isp's dns address as the forwarders.

So, this is all i have done. And the problem is that the clients do not get ip assigned. it get some other auto ip instead.

Thus, please help me where i am gone wrong!

Hello,
Leave the DNS, we will try to find out what is the problem with DHCP.

1. Check the DHCP server is properly started and running.
2. If it is proper, check your clients are properly configured DHCP client.
3. If point 2 is proper then issue "ifconfig /renew" cmd in command prompt and verify is there any traffic for DHCP is going on the network( you can use Ethereal).
4. If there is no traffic then, the problem could be with your client.
Normally Windows M/Cs uses 3 ways to address configure.
(i) Default method( where in, it just assign a private IP address, which is not assigned in any other machine with in your network)
(ii) DHCP method.
(iii) Static IP assign Method.

Check you computer that how it assigns IP address...

5.If there is a traffic then the problem could be your server.
Possible problems:
(i) Problem could be your DHCP configuration. Check your configuration
(ii)You told there are NIC one for public and other for Private right??.., check your DHCP server that, which interface it is offering DHCP service?. There can be chance that your DHCP server may offer service on Public interface, so you may not get the IP address to private network, and it is very danger, plz be careful.
(iii) If your interface is listening the right interface, check the DHCP server response for the client( this also can be viewed using ethereal).

I think with this you could isolate the problem, still not get back me with what you have tried and what was the results.

Regards,
Arul
May 5 '08 #2
raaman rai
114 100+
i am not sure whether you got my earlier post as a reply to your post below. well i think your point 5(ii) is the problem in my case. Cause i dont have any other computers (clients) which are dhcp configured but i find the clients machine getting dhcp ip assigned which i am not sure where it comes from. The ip achieved by my clients are out of the scope i have defined. And above all i dont have any idea as how to resolve the problem of my clients getting ip assigned in public interface. So, please help me! I am waiting long for your answer.

'
Hello,
Leave the DNS, we will try to find out what is the problem with DHCP.

1. Check the DHCP server is properly started and running.
2. If it is proper, check your clients are properly configured DHCP client.
3. If point 2 is proper then issue "ifconfig /renew" cmd in command prompt and verify is there any traffic for DHCP is going on the network( you can use Ethereal).
4. If there is no traffic then, the problem could be with your client.
Normally Windows M/Cs uses 3 ways to address configure.
(i) Default method( where in, it just assign a private IP address, which is not assigned in any other machine with in your network)
(ii) DHCP method.
(iii) Static IP assign Method.

Check you computer that how it assigns IP address...

5.If there is a traffic then the problem could be your server.
Possible problems:
(i) Problem could be your DHCP configuration. Check your configuration
(ii)You told there are NIC one for public and other for Private right??.., check your DHCP server that, which interface it is offering DHCP service?. There can be chance that your DHCP server may offer service on Public interface, so you may not get the IP address to private network, and it is very danger, plz be careful.
(iii) If your interface is listening the right interface, check the DHCP server response for the client( this also can be viewed using ethereal).

I think with this you could isolate the problem, still not get back me with what you have tried and what was the results.

Regards,
Arul
May 7 '08 #3

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

reply views Thread by m.anwar | last post: by
5 posts views Thread by Steve | last post: by
2 posts views Thread by WhatHappend | last post: by
5 posts views Thread by Richard | last post: by
reply views Thread by GHUM | last post: by
1 post views Thread by Screenbert | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.