100th domain is giving me trouble!

[mikeylikesit5805]

Hey Guys,

I am embarrassed to say I am having trouble connecting a win 8 machine to a win2012 server domain. (Test setup) I have done this many many times with no trouble.

Here is my setup
Desktop: Win 8 PC
IP 192.168.1.39
Mask: 255.255.255.0
Gateway 192.168.1.1
DNS 192.168.1.1

Server: Win2012 on a ESXI HOST
IP 192.168.1.100
Mask 255.255.255.0
Gateway 192.168.1.1
DNS 192.168.1.1

I can ping each machine from each machine, I can also ping the DNS server and the gateway from both machines . Domain is "lucas" or "lucas.home" When I go to connect I get
The specified domain either does not exist or could not be contacted” when joining a computer the domain

I have been doing some research and I suspect that it has to do something with the FQDN. When I ping lucas.home I am getting 192.105.254.228

is that right? shouldn't it be 192.168.1.100? or I missing the point of FQDN?

 

[cyabro]

You've got DNS configured incorrectly.
The primary DNS server on both server and workstation should be pointing to the server IP address - 192.168.1.100.
Then setup DNS forwarders on the server DNS admin console to point to your router or whatver external DNS servers you choose to use.

 

[citizensmith]

^^^ this

 

[mikeylikesit5805]

That was it! Thank you so much. I feel like I have never had to do that before, is there another way to set it up?

 

[YeOldeStonecat]

That was it! Thank you so much. I feel like I have never had to do that before, is there another way to set it up?

When you have a domain controller...it is the DNS for the LAN, not the router, not the ISPs DNS servers...you always use the IP of your DC for the primary DNS ....both for the DC itself, and handed out via DHCP to clients. Your server should run DHCP, disable DHCP on the router.

This guide I wrote years ago is old...very old...but the principles still hold true.. http://www.speedguide.net/articles/server-based-network-guide-1660

 

[YeOldeStonecat]

So in your case...the server, if it has an IP of 192.168.1.100
Servers TCP/IP properties.
IP: 192.168.1.100
SNM: 255.255.255.0
GTWY: 192.168.1.1
Primary DNS: 192.168.1.100 (or sometimes you'll see 127.0.0.1..which is the same thing...loopback...itself)

For clients...
IP: 192.168.1.101, or 192.168.1.102, or 192.168.1.103, etc etc.
SNM: 255.255.255.0
GTWY: 192.168.1.1
Primary DNS: 192.168.1.100

Generally...for DHCP, we set a handout range of say...192.168.1.100 and on up.
We typically put "static" devices down in the low range...I typically do servers having a last octect starting at .10, like 192.168.1.10, 192.168.1.11, etc. And printers starting in the .20's.

Although for businesses try to stay away from the common home router subnets like 192.168.0.x or 192.168.1.x because those are most common for residential routers, and for businesses...some people VPN in. And VPN doesn't like same IP ranges on both sides. So I'll typically do 192.168.10.x or 192.168.15.x or...you get the point.

 

[mikeylikesit5805]

Thanks for the help,

thats make perfect sense. I really appreciate the help, ive been in IT for a while now, more on the support side, and not much on the initial setup. I honestly don't get that much experience with best practices and what not.