Yes, it definitely looks DNS-related – appears there’s no way to get this router to hand out any custom DHCP DNS server addresses, unless there’s something hidden in the interface I’m missing.
Might be easier just to segregate my VMs on a separate subnet and use AD DHCP for those, whilst keeping all of the “home” devices on the router-provided DHCP. I generally fire my DCs up first in the lab anyway. I usually find all roads eventually lead to DNS anyway when it comes to weird issues ☺ From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Kurt Buff Sent: 31 May 2015 20:54 To: ntsysadm Subject: Re: [NTSysADM] Unable to join domain unless using static IP address OK - that's very strange. I use the full domain.tld at work, because it's actually faster than using the bare domain name. Oh, yes - what does your DHCP server hand out for DNS servers? At base, if your DHCP server hands out the default domain.tld of your AD infrastructure and points DNS to same, you should have no problems joining machines to the domain with a DHCP address. If you've done that, and you're still having problems, I'd break out wireshark to figure out what's going wrong. Of course, putting DHCP on your router means you won't get the benefit of integration with AD, but in a small lab that might not be a big priority. Kurt Kurt On Sun, May 31, 2015 at 12:19 PM, James Rankin <james.ran...@talosys.co.uk<mailto:james.ran...@talosys.co.uk>> wrote: Have to use the short one…it bombs on the FQDN even with a static address From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com>] On Behalf Of Kurt Buff Sent: 31 May 2015 20:05 To: ntsysadm Subject: Re: [NTSysADM] Unable to join domain unless using static IP address When joining, are you using the short name for the domain, or the full name - that is, domain vs. domain.tld? Perhaps more importantly, does your DHCP server hand out a default domain (domain.tld) with the lease, and if so, does it match the domain of your AD infrastructure? Kurt On Sun, May 31, 2015 at 10:55 AM, James Rankin <james.ran...@talosys.co.uk<mailto:james.ran...@talosys.co.uk>> wrote: 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<mailto: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<mailto:i...@talosys.co.uk> Website: www.talosys.co.uk<http://www.talosys.co.uk> [phpy9YoGNAM]
