Jump to content

Recommended Posts

Posted

Hi, hoping someone can help. Have barely any networking knowledge.

If the server IPv4 address is 192.168.0.1, the start and end would be 192.168.1 and 192.168.1.254, The subnet i assume is 255.255.255.0.

I don't think i need to add exclusions or delays.

Default gateway I'm not sure what I should put for this. Bare in mind the server I'm using is on a virtual machine.

Not sure if i need to fill the domain name and DNS Servers part?

 

dhcp error.PNG

 

I have had a play around and just cant get the DHCP to work. The DHCP post-install configuration wizard keeps throwing an error about registry key and an error.

Posted (edited)

Depends if this is the only domain controller on your domain. If you have another DC running DNS services, then you will need to add this IP and the default gateway will usually be the IP of your router unless you have vLans. If you have no other DC on the domain, you will also need to install DNS.

 

There are quite a lot of unknowns with your existing domain/server set-up so it will be difficult for members to assist.

Edited by djm968
Posted
So, its hard for me to explain. Long story short i'm on a Virtual Server. There is no other domain controller. There is no physical router (Cant see one). DNS has been installed. Sorry for being so Vague its hared to explain when i don't really understand
Posted (edited)
Default gateway is your router, or Vlan address if you use vlans

 

This ++ . The default gateway will be the default gateway for the vlan/scope you are configuring.

 

For example say you had vlan 50 with IP range 10.1.50.0/24 and last usable IP address is 10.1.50.254 is being used as gateway on that vlan then on your DHCP scope you would set 10.1.50.254 as the default gateway. As long as you have the dhcp helpers on the vlan (normally on the layer3 switch where the vlan is being routed) and there are no firewall or access lists in place that should work. Hope that not too much info overload.

 

Even if you have not configured any vlans there will prob be managed/smart switches set on the default of vlan 1.

 

Are you running the config wizard from the server running the actual DHCP service??

Edited by Davit2005
Posted
Ok the DNS server entry for your DHCP scope will be IP of the DNS server (itself) You should have a router somewhere on the network, check the IP settings of the physical host and the server you are building for a default gateway IP address and use this.
Posted
This ++ . The default gateway will be the default gateway for the vlan/scope you are configuring.

 

For example say you had vlan 50 with IP range 10.1.50.0/24 and last usable IP address is 10.1.50.254 is being used as gateway on that vlan then on your DHCP scope you would set 10.1.50.254 as the default gateway. As long as you have the dhcp helpers on the vlan (normally on the layer3 switch where the vlan is being routed) and there are no firewall or access lists in place that should work. Hope that not too much info overload.

 

Even if you have not configured any vlans there will prob be managed/smart switches set on the default of vlan 1.

 

Are you running the config wizard from the server running the actual DHCP service??

 

Get that, but how do i find the address when there is no physical router.

Posted
No if you have no vLans, the default gateway would be 192.168.0.250. The DNS setting will be IP address of the server 192.168.0.1 (127.0.0.1 is the local host address, basically saying use itself for DNS)
  • Thanks 1
Posted (edited)

Use the same address that the server is set to in the scope, in that screen shot, if that is currently working and you have no vlans.

 

The DHCP scope should be set to use the DNS server IP address (the local (LAN) IP address of the server running DNS) so clients use the DNS server, otherwise you will get AD issues on the clients.

Edited by Davit2005
Posted (edited)
Right so i think ive followed everyones instructions correctly. This is what ive got.

 

[ATTACH=CONFIG]59847[/ATTACH] [ATTACH=CONFIG]59848[/ATTACH] [ATTACH=CONFIG]59849[/ATTACH]

 

Thanks for the help so far!

 

Youl want to set an exclusion range on the scope.

 

Exclude any addresses that you set static including the server and the default gateway.

 

Give your self a bit of room for manoeuvre for future other static devices, i.e. printers and other servers, etc. If you can, you will have to make the call on how many IP addresses you will need but try to make it big enough either way with some room for future it is easier to do this at this stage.

Edited by Davit2005
Posted
Youl want to set an exclusion range on the scope.

 

Exclude any addresses that you set static including the server and the default gateway.

 

Give your self a bit of room for manoeuvre for future other static devices, i.e. printers and other servers, etc.

 

Im trying to add the server ip and also the default gateway to exclusion but im getting this.

 

exclusion.PNG

Posted (edited)
You don't need to add the IP of the gateway to the exclusions, this is in a different subnet.

 

If it is a different subnet that subnet will have its own gateway which should be excluded if the whole IP range (all available IP addresses) are being set in the scope.

 

If using a 192.168.1.1/24 and you have set the scope to give out 192.168.1.1 to 192.168.1.254 then you will need to set exclusion for any static ip addresses. Or alternatively address reservations could be used even if the devices are set statically. You need something that prevents a DHCP server giving out a IP address that has been set statically. I don't think Windows dhcp (or any dhcp server) for that matter is that intelligent yet.

Edited by Davit2005
Posted
So dont think ill haven any static ip's, im not going to be connecting printers etc. My goal is to get AD, DHCP and DNS setup. Open hyper-V on the server create 3 desktops and connect them to the domain, create some users and groups. Hopefully its as easy as that!
Posted (edited)
No that's fine, you can't add the address of the the IP address of the server as an exclusion to your scope because it's in a different subnet which is why it gave you an error. Ignore my post about the range. Edited by djm968
  • Thanks 1
Posted (edited)

Ok gotcha, thanks. I know im being a pain and really appreciate the help, ive got my Virtual machine PC and its not picking an ip up from the dhcp. Im almost positive ive setup the virtual switch correctly. Also is this normal?

 

error 1.PNG error 2.PNG

error 3.PNG

Edited by Techuser2456

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...