Windows Server 2008 R2 No Leases

steve498 · Nov 3, 2014

Hi,

I'm trying to setup a DHCP scope on a local domain controller through the starting IP addresses of 192.168.1.64 - 192.168.1.100. I have successfully configured this however, when I right click on the Address Leases and refresh, I cannot see any computers leasing any ip address although my domain controller has the IP. 192.168.1.66 (preferred)?

Any ideas? I really really need help here ):

Thanks.

cowboydude99 · Nov 3, 2014

Hi,
Have you activated the scope? Right-click on it, is Activate an option or Deactivate?

Click onto the server name, then right-click it. Did you Authorize the DHCP server?

steve498 · Nov 3, 2014

cowboydude99 :

Yes I have done this. It is active.

Sorry to be cheeky but is it possible to ask if we can instant message on skype and possibly teamviewer the issue? I know this is a lot to ask :$

Thanks!

cowboydude99 · Nov 3, 2014

Hi- I'm sorry, I can't do that. You can private message me on here if you need.

steve498 · Nov 3, 2014

cowboydude99 :

That's fine. I just connected to the domain via a client PC and the IP address given was 192.168.137.X so I have adjusted the scope to search from 192.168.137.1 -> 192.168.1.254. However, the ip address is still not in the leases?

I hope you kind of get the jist of this.

Thanks

cowboydude99 · Nov 3, 2014

Okay, but before we go any further, do you understand basic networking or DHCP? If not that is okay, I just want to know what level you're on.

Sounds to me like you already have either an existing DHCP server (giving out those 192.168.137.x addresses or you have the clients set for static IP.

When the client PC boots it broadcasts a dhcp discovery packet. When a DHCP server gets this packet it responds. Now if there are multiple requests sent back to the client (from multiple DHCP servers) the desktop will take the first offer it gets.

If I client is getting 192.168.137.x then it sounds like the ip subnet isn't what you think it is.

Give me some background, maybe I can help.

cowboydude99 · Nov 3, 2014

Also- what server/dhcp are you using? Windows? If so, what version?

steve498 · Nov 3, 2014

No I'm completely new haha I thought this would be simple so apologises. There is one DHCP running on a Windows Server 2008 R2 server and the client PCs are Windows 7 Ultimate.

I have the network adapters on the client PC's configured to a static local IP address of 192.168.1.66.

I hope this helps ish.

cowboydude99 · Nov 3, 2014

Statically set clients will never use a DHCP server. They have no reason.

Set the clients to "Obtain and IP Address Automatically".

Then check your DHCP server.

One question- how do the clients and server connect to the network?

steve498 · Nov 3, 2014

cowboydude99 :

The client's network adapters only have their DNS set to the domain controller's IP other than that, they obtain the IP automatically.

The client PC's are obtaining IP addresses via ethernet connections.

To cut a long story short, I am trying to boot from the network to install operating systems but I need a DHCP server setup for this.

cowboydude99 · Nov 3, 2014

Okay, before you can use DHCP you need to have the clients connecting to the same subnet.

Are they connecting to the same switch? Is there a firewall or router between your clients and server?

steve498 · Nov 3, 2014

cowboydude99 :

I assume there is only my router's firewall and window's firewall. There is a switch between the computers yes this is a Netgear Eight port switch.

How would I adjust the subnet? Thanks

cowboydude99 · Nov 3, 2014

So all desktops and server(s) are connected to this switch?

Is the netgear giving out IP Addresses? Log on to it and check what the scope is on the Netgear.

steve498 · Nov 3, 2014

Not all of the machines. The machines that will be connecting to this domain controller will be directly connecting to the router but as of currently, the domain controller is connected via a switch as I have it in my office to configure etc.

I do not believe the switch can be logged on too. All I see on the network map is "Switch". I don't see any IP addresses linked to it?

Ijack · Nov 3, 2014

You are sure that the router isn't also a DHCP server? What make and model is it? Note that your server's IP address should not be in the DHCP range; you need to correct that before proceeding.

steve498 · Nov 3, 2014

Ijack :

Well the router gives out 192.168.1.X Ip addresses and it is a BT HomeHub v4.

cowboydude99 · Nov 3, 2014

This is getting a bit confusing.

1. Are the client PCs and server connected to the same switch right now?

2. If not- make sure they are.

3. Disconnect them from the router, as it is not needed just yet.

4. Reboot your server and once it is back up and running verify that your server is on the same IP subnet it is trying to give out address for- 192.168.1.0/24. /24 = subnet mask 255.255.255.0

Ijack · Nov 3, 2014

Also, read my edit to my last post - your server address is in your DHCP zone; this is wrong.

Two DHCP servers is going to cause you headaches. I think you need to do some reading about how to configure a network and start over.

steve498 · Nov 3, 2014

cowboydude99 :

Okay this is how the CURRENT setup is.

There is a router that is connected to the phone line and providing internet access. An ethernet cable is plugged into this and runs into an eight port switch that splits the connection between eight different ethernet cables. Two of these cables are plugged (one each) into a Client PC and the Server.

So they are going from the PC -> Into a splitter switch -> Router -> Internet.

If I disconnect the router, they will all loose internet access.

Does that make any sense?

#

Edit: I will attempt the DHCP server once I am not using a switch and have done some more research. I appreciate the help.

cowboydude99 · Nov 3, 2014

Your physical connections are good. This is the first step.

Since they're all physically connected, disable the DHCP server in the router.

If you do not know how to logon to your router consult the manual. Normally the address is: http://192.168.1.1

Once you disable the DHCP in the router you will no longer have any DHCP conflicts.

steve498 · Nov 3, 2014

cowboydude99 :

Okay this is what I have in my router: http://i.imgur.com/Edlh0Zv.jpg

If I disable the DHCP, as no IP addresses will be assigned through the router, will this affect other computer's not connecting to the domain controller?

Thanks

cowboydude99 · Nov 3, 2014

In order to access network resources over TCP/IP each host/client needs an address.

If you disable it here, your server should start giving out IP addresses. I only have limited knowledge of your network, so I can't say if anything else will prevent your server from giving out addresses.

Now if your server is mis-configured and you disable the DHCP in the router, then once users reboot (or their DHCP lease expires) they will not be able to access network resources because they would no longer be able to get an address.

steve498 · Nov 3, 2014

cowboydude99 :

Okay I understand. I will perform this tomorrow when I am on the business router rather than a personal as I wouldn't like to loose connection on my devices.

I appreciate everybody's help and I'm sure disabling the router's DHCP and removing switches, will solve the issue.

Thanks again!!

Windows Server 2008 R2 No Leases

Reputable

Honorable

Reputable

Honorable

Reputable

Honorable

Honorable

Reputable

Honorable

Reputable

Honorable

Reputable

Honorable

Reputable

Splendid

Reputable

Honorable

Splendid

Reputable

Honorable

Reputable

Honorable

Reputable

Share this page