First thought is that the DHCP settings need to set the AD DNS servers as the client’s DNS servers. Then of course you’ll need to make sure the AD DNS servers are set to forward to your ISP DNS servers, or even back to the router as DNS server. Or you haven’t set a default domain suffix in the options for the DHCP zone on the router, if it has that capability. If it doesn’t, use the FQDN of the domain you’re trying to join.
Not to sound pedantic, but it could be easy to forget those things. *From:* listsadmin@lists.myitforum.com [mailto: listsadmin@lists.myitforum.com] *On Behalf Of *James Rankin *Sent:* Sunday, May 31, 2015 1:56 PM *To:* ntsys...@lists.myitforum.com *Subject:* [NTSysADM] Unable to join domain unless using static IP address In my lab, I can’t join the domain unless I switch my machines to a static IP address. Not much of an issue really, but I’m just interested in maybe finding out why it’s happening. My DHCP is handled by a cheap and cheerful home router. I was wondering if anyone has any idea why this is happening? The VMs, workstations, servers and DCs, all sit on the same host, however the router is connected to via wireless. I thought about switching the DHCP to the DCs, but thought I’d check with the minds of the list and see if there’s anything glaringly obvious anyone might be able to point me towards before I go down the route of making any wholesale changes. TIA, *James Rankin* EUC Director | TaloSys | 07809 668579 | james.ran...@talosys.co.uk One Trinity Green, Eldon Street, South Shields, Tyne & Wear, NE33 1SA Tel: 0191 481 3489 Email address: i...@talosys.co.uk Website: www.talosys.co.uk [image: phpy9YoGNAM]
