DHCP & DNS

[wc2]

Just configured a LAN

Server 192.168.1.10 - 255.255.255.0 - GW & DNS 192.168.1.5
Router 192.168.1.5

DHCP Config as follows

Address Pool - 192.168.1.50 / 192.168.1.200
Scope Options -
003 - Router - 192.168.1.5
006 - DNS Servers - 192.168.1.10 - 81.x.x.x 81.x.x.x
015 - DNS Domain name - Blah.local
044 - WINS/NBNS Servers - 192.168.1.10
046 - WINS/NBT Node Type - 0x8

The DHCP Server can't be found on the network. Give a machine a static - It can see the Domain but takes a month to login.

Anyone see what's wrong ?

Ta

[EqualOpportunities]

Just configured a LAN

Server 192.168.1.10 - 255.255.255.0 - GW & DNS 192.168.1.5
Router 192.168.1.5

DHCP Config as follows

Address Pool - 192.168.1.50 / 192.168.1.200
Scope Options -
003 - Router - 192.168.1.5
006 - DNS Servers - 192.168.1.10 - 81.x.x.x 81.x.x.x
015 - DNS Domain name - Blah.local
044 - WINS/NBNS Servers - 192.168.1.10
046 - WINS/NBT Node Type - 0x8

The DHCP Server can't be found on the network. Give a machine a static - It can see the Domain but takes a month to login.

Anyone see what's wrong ?

Ta

I presume that the DHCP server has a valid address within the range you are using?

[Mordac]

Might sound silly but have you authorised the DHCP server? To prevent people accidentally installing rogue DHCP servers they must be authorised by an Enterprise Admin or they'll just sit there doing bugger all.

[errorista]

make sure that the DHCP server is giving out the domain DNS server address as the primary DNS to your windows clients.

do an ipconfig /all on a client to make sure that you see your DNS server 192.168.1.10 as the main dns address.

error

[wc2]

I can't look at it until tomorrow but..

I am sure that the DHCP is authorised.

I can't ipconfig as DHCP is not handing out IP's

I'll check the local static to see if the DNS settings are wrong.

Cheers guys

[errorista]

If its a first time up DHCP server then I like Mordacs answer

Should find 'Authorise' under the DHCP 'Action' menu.

Make sure only one DHCP server is 'visable' too. They wont co-habit.

good luck

please let us know what it was when you crack it!

error

[Mordac]

DNS (or the lack of it) won't stop you obtaining a DHCP address. DHCP doesn't use DNS, if a client requests an IP address, and one is available, it will be issued. Clients can be registered in DNS by the DHCP server (if the DHCP server is a member of the DNSUpdateProxy group, but that's a different matter). I would say your DHCP server is either wrongly configured (e.g. no lease scopes have been activated) or the server has not been authorised.

[errorista]

agree about DHCP and DNS

i was addressing the 'long login'

"...Give a machine a static - It can see the Domain but takes a month to login."

This was because wc2 set the client IP as static but did not set DNS on the client - this is why the long login time

useful to remember when setting up windows notwork


error

[Dr Evil]

Just configured a LAN

Server 192.168.1.10 - 255.255.255.0 - GW & DNS 192.168.1.5
Router 192.168.1.5

DHCP Config as follows

Address Pool - 192.168.1.50 / 192.168.1.200
Scope Options -
003 - Router - 192.168.1.5
006 - DNS Servers - 192.168.1.10 - 81.x.x.x 81.x.x.x
015 - DNS Domain name - Blah.local
044 - WINS/NBNS Servers - 192.168.1.10
046 - WINS/NBT Node Type - 0x8

The DHCP Server can't be found on the network. Give a machine a static - It can see the Domain but takes a month to login.

Anyone see what's wrong ?

Ta

If it's 2000 or 2003 it will query DNS for the DC to login to.
Either way your DHCP scope is pointing at the router as DNS.
. . . or is that too obvious?

Also try a tracert 192.168.1.10 from the client trying to log in to the domain, maybe the router doesn't know where the DC is? (What's the client ipconfig /all)

[DimPrawn]

The joys of Windows, DNS, Active Directory and all that crap.

Switch to Linux.