Still have DHCP issues on my server

Butters

Butters

Butters

Permabanned
Joined
22 Apr 2007
Posts
1,805
Hi everyone,

I'm messing about with a WIN2K3 Server for experience and I'm having some problems.

I have a router which I have disabled DHCP on. Its 192.168.2.1

I have my server, its configured as follows:

IP 192.168.2.101
Subnet 255.255.255.0
Default Gateway 192.168.2.1

Primary DNS 192.168.2.101

This is how I've set it in Network Config too.

I have enabled DHCP and DNS on this server and my scope is 192.168.2.102 to 192.168.2.120

I have authorised DHCP and included the domain in Active Directory.

When I fire up a client I can't connect to the domain and the machine doesn't obtain an IP address from the DHCP server or the router. It ends up pulling an IP from the Cable Modem which gives no connectivity.

If I assign this client manually, I use the following in network config:-

ip 192.168.2.102
Subnet 255.255.255.0
Default Gateway 192.168.2.1

Primary DNS 192.168.2.101

If I do this manually then I can ping the server, the server can ping the client but I cant connect to the internet on the client machine, nor can I join the domian!

Any ideas?

Thanks
 
Butters said:
When I fire up a client I can't connect to the domain and the machine doesn't obtain an IP address from the DHCP server or the router. It ends up pulling an IP from the Cable Modem which gives no connectivity.
Click to expand...

Does this mean you have more than 1 DHCP server running on the network?
 
My guess to as why you can't access anything on the Internet is down to your DNS server. You specified your server as a DNS server which is fine if its a properly configured DNS server.

Either you could configure your clients to have your ISP's DNS server or you will have to play about with your servers DNS service.

You shouldn't have two DHCP servers running as that will confuse your client pc, also you say it will pull and IP address from the cable modem? What IP address is it getting? If its something like 169.x.x.x it usually means that it hasn't gotten any IP address and as you said you won't have any connectivity.
 
Hi, yes, I've activated the scope and authorised the DHCP server.

I only have one DHCP server, but obviously, my router is able to look after DHCP too. I have disabled this though as I want DHCP to come from the server.

How do I know if my server is 'properly configured' for DNS?

I want my clients to obtain all the information automatically from the DHCP part of my server.

And yes, the clients were eventually picking up a 164.x.x.x address or something
 
my 2k3 server knowledge is a little rusty, but it sounds like dns issues to me. Have you correctly set up forwarders or root hints? is the DNS ad integrated?
 
Sone said:
my 2k3 server knowledge is a little rusty, but it sounds like dns issues to me. Have you correctly set up forwarders or root hints? is the DNS ad integrated?
Click to expand...

Hi,

I'm aware that I dont really need forwarders unless the server can't resolve something for the clients.

DNS in the AD is sorted AFAIK.

Thansk
 
You need to point your server at the router for its forward DNS, it can't magic its own DNS records from nowhere.

Basically, in this post:

I have my server, its configured as follows:

IP 192.168.2.101
Subnet 255.255.255.0
Default Gateway 192.168.2.1

Primary DNS 192.168.2.101
Click to expand...

The 'primary DNS' needs to be 192.168.2.1. Hey presto, you should have a functioning network.
 
iam said:
You need to point your server at the router for its forward DNS, it can't magic its own DNS records from nowhere.

Basically, in this post:

The 'primary DNS' needs to be 192.168.2.1. Hey presto, you should have a functioning network.
Click to expand...

I believe he has his server set up as a DC, and as such it should point to itself as the primary DNS (assuming it's the only DC on the domain)

Forwarders are not essential, as a DNS server can use root hints to resolve DNS queries.
 
I got it working but the annoying thing is, I don't know how :(

My router had an option of automatically picking up DNS from my ISP so I disabled this and was given the option of entering a DNS server so I stuck 192.168.2.101 in, however, I'm sure I did this before and it didn't work.

Also,

I had to configure my client laptop manually with the following:-

IP 192.168.2.105
DG 192.168.2.1
DNS 192.168.2.101

I could then connect to the domain and once in I set the network adapater to auto detect and rebooted the laptop and it picked up these settings manually so I can assume DHCP worked too.

Tempted to restart from scratch and try things again to see if I can pinpoint exactly what I did. Thanks for the help.
 
You must log in or register to reply here.
Back
Top Bottom