Computing.Net > Forums > Windows Server 2003 > DHCP and DNS Problem HELP

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

DHCP and DNS Problem HELP

Reply to Message Icon

Name: dubsdjb
Date: October 26, 2006 at 07:58:22 Pacific
OS: Windows XP / 2003
CPU/Ram: 2gb
Product: ASUS
Comment:

Hello can anybody help me
I have set up a windows server 2003 domain. I have set the scope to: 192.168.1.10 - 192.168.1.254
I have set the DNS forward to: 192.168.1.1 (Which is my internet router)

I have set up a static ip address for the server:
Ip address: 192.168.1.9 (outside of scope)
Subnet: 255.255.255.0
Default Gateway: 192.168.1.1 (Router)
Primary DNS: 192.168.1.9
Secondary DNS: 192.168.1.1

I have run DHCP and authorized it and it says its running etc..

I have even added a rule in DNS 003 router with the ip address of my internet router 192.168.1.1

But when I go to one of my client machines and set ip to automatic resolve. I receive a message saying the Network has limited or no connectivity??? I can ping the server from the client machine and I get a reply, but DHCP does not seem to be assigning the clients with addresses.

Also I have managed to log onto the domain with a static ip address but it seems to take about 10 mintues to log on..?? Is this something I'm doing wrong with DNS?

Please can somebody tell me what or where I'm going wrong, I would very much appreciate. Thanks



Sponsored Link
Ads by Google

Response Number 1
Name: Curt R
Date: October 26, 2006 at 08:32:33 Pacific
Reply:

The DNS on the DC needs to be forwarded to your ISP's DNS server(s), not the router (192.168.0.1).

Your DHCP scope should supply the DC's IP as the DNS address to clients. They have to authenticate to your DC and will do so if you have the correct DNS address in there (ie: your DC at 192.168.0.9).

DHCP scope should be as follows:

Scope: 192.168.0.10 - .254
DNS: 192.168.0.9
Gateway: 192.168.0.1
SM: 255.255.255.0

Ensure you have DHCP shut off on your router so there's no conflict.


0

Response Number 2
Name: dubsdjb
Date: October 26, 2006 at 09:38:28 Pacific
Reply:

ok I have changed the scope to:

192.168.0.10 - .254

I have changed the static ip of the Server to: 192.168.0.11

I have changed my router ip to: 192.168.0.1

I have checked that DHCP is not enabled on the router (it is not)

I have created a static ip on one of the client machines as following:

ip: 192.168.0.12
SM: 255.255.255.0
DNS: 192.168.0.11 (The server)
Gateway: 192.168.0.1 (The router)

I have then checked that DHCP is running, says it is...

Then I select a client machine, tell it to automatically recieve IP from DHCP.. and still Limited or no connectivity.

I try pinging the server and the server replies so it is definetly not the network equipment thats at fault.

I noticed that if I set the DNS ip on the client machines to: 192.168.0.11 (the server) The internet wont work. The only way I can make the internet to work is to set the DNS and default gateway to the router (192.168.0.1)

Anyone know what I'm doing wrong?

I have tried running the DHCP wizards, DCPromo etc but I'm sure somewhere along the line I'm entering the wrong DNS settings.


0

Response Number 3
Name: Curt R
Date: October 26, 2006 at 10:41:36 Pacific
Reply:

I noticed that if I set the DNS ip on the client machines to: 192.168.0.11 (the server) The internet wont work.

Have you enabled forwarding in your DC's DNS server and pointed it at your ISP's DNS servers? If not, do so and test again with a client pointing at your DNS server.

The reason it's working with you router is that your router already know's to go to your ISP's DNS servers for resolution. Once you forward your DNS on the DC, it will know too and clients pointed at the DC for DNS will also resolve properly.

The way it works is, a client makes a request, it goes to your DNS server. If it's within the local zone, your DNS server resolves it and sends it back to the client. If it's outside the local zone, your DNS server forwards the request on to whatever DNS server is entered in the forward section of the DNS setup. That DNS server performs the resolution, or forwards it to another. Eventually, it's resolved and sent back to the client.

You HAVE to have your clients point at your DC's DNS server for authentication purposes. This is most important. If you point the clients at your gateway, you'll be lucky to have any of them be able to log into your domain as they won't get authenticated to your DC. They can't since your DNS points at the wrong server. This is why it's so important to setup forwarding on your DNS....so your clients can authenticate to the domain AND have resolution for requests outside the local zone.


0

Response Number 4
Name: dubsdjb
Date: October 26, 2006 at 16:38:44 Pacific
Reply:

When I run the DHCP server wizard I get to a sticky point where I'm a little bit lost. It says "configure DHCP options"

It starts asking me for a parent domain, DNS server etc.

But I just want the same server that I'm running the wizard on to be the DNS server, and what is this parent domain thing all about? I think I might be going a bit wrong somewhere here..


0

Response Number 5
Name: dubsdjb
Date: October 27, 2006 at 05:08:35 Pacific
Reply:

Aha done it! I just needed to add some rules in the DHCP program

just want to say thanks to Curt for your useful advice, cheers



0

Related Posts

See More



Sponsored Link
Ads by Google
Reply to Message Icon

No Desktop Items for One ... Mom 2005



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: DHCP and DNS Problem HELP

DHCP and DNS www.computing.net/answers/windows-2003/dhcp-and-dns/6766.html

Domain Controller and DNS problems www.computing.net/answers/windows-2003/domain-controller-and-dns-problems/2117.html

deleting DNS and DHCP from 2003 www.computing.net/answers/windows-2003/deleting-dns-and-dhcp-from-2003/4586.html