looking for someone that finish MCITP 70-640 training book using Virtual Machines

tech_leak

Hi.. I'm currently studying home for MCITP certification. I am going through 70-640 training book and i'm stuck on page 28 which is joining server core to domain.
I was hoping someone that already done this could maybe find me a solution.

Problem im getting:

"netdom join %computername% /domain:contoso.com /userd:CONTOSO.COM\administrator /passwordd:*




The specified domain either does not exist or could not be contacted"

can someone help?

method115

Can you ping the DC? Is your DNS on the server core configured with the IP of your DC?

tech_leak

my set up is, using vmware, created two separate virtual machines. 1, is Windows Server 2008 and other is the Core installation. I used bridged-connection for them and I can ping one from another.

ptilsen

How is DNS setup on each system's NIC?

Can you Ping both by hostname and FQND?

tech_leak

i am new to servers.. I've only worked on windows client so far and my network knowledge is limited to that.

Server

---

IPv4 - 192.168.1.70
Subnet Mask - 255.255.255.0
Default Gateway - 192.168.0.1
DNS Server - 194.168.4.100
194.168.8.100

Server-Core

---

IPv4 - 192.168.1.71
Subnet Mask - 255.255.255.0
Default Gateway - 192.168.0.1
DNS Server - 194.168.4.100

on server, i've only set static ip as shows above and added role "Created a New Domain In A New Forest" named contoso.com. Apart from this, I've not done anything else.

On server-core, Ive set static ip again, changed computer name and tried adding the core to domain. Everything was done according how the 70-640 training book showed.

Edit: and i don't know what you mean by "Can you Ping both by hostname and FQND?"

cyberguypr

Is that 194.168.4.100 a typo or is the DNS server is on another subnet?

FQDN (little typo by ptilsen)=Fully Qualified Domain Name, example: servername.contoso.com

cyberguypr

I just realized all those IP settings are strange. Why is your gateway in another subnet? Is 192.168.0.1 your home router?

tech_leak

yes it is... I am doing this at home. The book does say to create a domain using IP adresses in the 10.0.0.11-10.0.0.20 but as I was doing this at home, I figured this should be the way? was i wrong?

cyberguypr

Dont make it too complicated. If your router is 192.168.0.1 assign IP addresses in that subnet.

Server
IP: 192.168.0.100
GW: 192.168.0.1
DNS: 192.168.0.1

Server core
IP: 192.168.0.101
GW: 192.168.0.1
DNS: 192.168.0.100

This way Server Core resolves DNS against Server and will still be able to get out to the web for updates etc.

method115

Your DNS server should always have the IP address of your domain controller.

tech_leak

I've changed ip's and tried again but no luck. I've done a wide research specifically about this problem and few people came across the exact same problem but for most people, it was just a typo with the command. in my case, i have tried every possible way for the command bu all I've getting is "The specified domain either does not exist or could not be contacted"

cyberguypr

You must be able to ping contoso.com from both servers. If that doesn't happen you definitely have a misconfiguration in IP or DNS. Can you ping contoso.com at least from SERVER?

tech_leak

yes, i can ping contoso.com from server

tech_leak

I have also disabled firewall from both server and core but hasn't changed anything. I don't think its IP problem as I can ping between machines.

ptilsen

Neither NIC should point to your router for DNS. both should point to your DNS server. Your DNS server should be set to forward either to your router, ISP, or another Internet DNS source such as Google public DNS or OpenDNS. Really, you want to get away from the mentality of a "router" providing DNS.

You will want to check your SoA record for the contoso forward lookup zone. Normally, this works automatically, but with your DNS configuration it has probably gotten a bit messed up.

tech_leak

how will i do that? Let me be more open... the 70-640 book I'm following said,

"The remaining......... will create a domain using IP addresses in the 10.0.0.11 - 10.0.0.20 range, with a subnet mask of 255.255.255.0. If these addresses are used in your production environment and if the server is connected to your production environment, you must change the IP addresses in this book accordingly so that the contoso.com domain you create in these practises does not conflict with your production network."

then it goes on tells me to enter;

IP Address: 10.0.0.11
Subnet Mask: 255.255.255.0
Default Gateway: 10.0.0.1
Preferred DNS server: 10.0.0.11

the reason why I've set my IP's the way I did is because I figured, I am connecting my server to my home environment which is through router.

(and both the NIC's on VM is set to bridged.) Now, I don't know how to work around this...

certhelp

tech_leak wrote: »

my set up is, using vmware, created two separate virtual machines. 1, is Windows Server 2008 and other is the Core installation. I used bridged-connection for them and I can ping one from another.

tech_leak wrote: »

the reason why I've set my IP's the way I did is because I figured, I am connecting my server to my home environment which is through router.

(and both the NIC's on VM is set to bridged.) Now, I don't know how to work around this...

If you just want to ping from one another, Host-only virtual network type is enough but virtual machines will not be able to access the Internet. If you don't want to access the virtual machines from outside the virtual environment or the host machine then NAT is enough. NAT allows Internet access to the virtual machines.

If you use bridged virtual network type, the virtual machines have to use the settings of the your actual network -- non virtual. Using host-only or NAT gives you flexibility in configure IP addresses, gateway, DHCP server.

Your problem might have to do with setting up and configuring VMware Virtual Networks (using VMware Virtual Network Editor). What are the settings for Vmnet0 (or whatever is for Bridged virtual network type). You can get to virtual network editor using menu Edit -> "Virtual Network Editor..." from VMware Workstation.

tech_leak

Your problem might have to do with setting up and configuring VMware Virtual Networks (using VMware Virtual Network Editor). What are the settings for Vmnet0 (or whatever is for Bridged virtual network type). You can get to virtual network editor using menu Edit -> "Virtual Network Editor..." from VMware Workstation.

Vmnet0 is Auto-Bridging.

I've also set my dns server to forward to OpenDNS and changed auto-bridging from auto to Marvell Yukon etc... and I still can't ping contoso.com from Core.

certhelp

tech_leak wrote: »

Server

---

IPv4 - 192.168.1.70
Subnet Mask - 255.255.255.0
Default Gateway - 192.168.0.1
DNS Server - 194.168.4.100
194.168.8.100

Server-Core

---

IPv4 - 192.168.1.71
Subnet Mask - 255.255.255.0
Default Gateway - 192.168.0.1
DNS Server - 194.168.4.100

Just for pinging by IP addresses, the DNS server and gateways don't matter. Are you able to ping from each VM the other VM using IP address?

Are you able to ping by IP address? Is AD installed on the Server?

EDIT: I see you can ping by IP and ping contoso.com from Server.

certhelp

cyberguypr wrote: »

I just realized all those IP settings are strange. Why is your gateway in another subnet? Is 192.168.0.1 your home router?

That's because bridged virtual network type would set the DNS to whatever the DNS parameters are sent by the router or they are left over from some other lab. If they are from the router, they would be public IP addresses though.

Oops... The rotuer supplied DNS server IP seems to be 194.168.4.1 which is public. Didn't read carefully.

certhelp

tech_leak wrote: »

how will i do that? Let me be more open... the 70-640 book I'm following said,

"The remaining......... will create a domain using IP addresses in the 10.0.0.11 - 10.0.0.20 range, with a subnet mask of 255.255.255.0. If these addresses are used in your production environment and if the server is connected to your production environment, you must change the IP addresses in this book accordingly so that the contoso.com domain you create in these practises does not conflict with your production network."

then it goes on tells me to enter;

IP Address: 10.0.0.11
Subnet Mask: 255.255.255.0
Default Gateway: 10.0.0.1
Preferred DNS server: 10.0.0.11

the reason why I've set my IP's the way I did is because I figured, I am connecting my server to my home environment which is through router.

(and both the NIC's on VM is set to bridged.) Now, I don't know how to work around this...

If you want to use those IP ranges, you need NAT or Host-only network type.

tech_leak

I can ping between VM using "ping 192.168.0.70" and 71 no problem. I can ping contoso.com from Server but not core. Two roles are installed on the server. AD DS and DNS Server.

certhelp

tech_leak wrote: »

I can ping between VM using "ping 192.168.0.70" and 71 no problem. I can ping contoso.com from Server but not core. Two roles are installed on the server. AD DS and DNS Server.

Change TCP/IP settings on Server and Core to following:

Server

---

IPv4 - 192.168.1.70
Subnet Mask - 255.255.255.0
Default Gateway - 192.168.1.1
DNS Server - 1912.168.1.70
194.168.8.100

Server-Core

---

IPv4 - 192.168.1.71
Subnet Mask - 255.255.255.0
Default Gateway - 192.168.1.1
DNS Server - 192.168.1.70

Try pinging using names (host and FQDN).

Is your default gateway (on your home network) address is 192.168.1.1 and your home network IP range is 192.168.1.1-255?

tech_leak

Default gateway on home network is 192.168.0.1 and network ip range is 192.168.0.1-254. To be 100% honest, my knowledge about networking is limited so I dont really know much about ranging. (got the range details from router)

sorry for the typo earlier too... I did mean 192.168.0.1 and not 1.1

certhelp

tech_leak wrote: »

Default gateway on home network is 192.168.0.1 and network ip range is 192.168.0.1-254. To be 100% honest, my knowledge about networking is limited so I dont really know much about ranging. (got the range details from router)

sorry for the typo earlier too... I did mean 192.168.0.1 and not 1.1

Then the default gateway in the above should be 192.168.0.1 instead of 192.168.1.1. You should also change the IP address of the server and server core to 192.168.0.70 and 192.168.0.71.

tech_leak

I have and it worked... I can't thank you guys enough for this. Now I don't fully understand what the problem was... it worked after changing DNS Server to 192.168.0.70 on both Server and Core but I had both same before. Does that to do with ranging? if so, how is having 192.168.0.70 different from any other I tried?

certhelp

tech_leak wrote: »

I have and it worked... I can't thank you guys enough for this. Now I don't fully understand what the problem was... it worked after changing DNS Server to 192.168.0.70 on both Server and Core but I had both same before. Does that to do with ranging? if so, how is having 192.168.0.70 different from any other I tried?

That's because you installed DNS and AD DC on server which looks up computers by name. But your DNS is pointed to your ISP (virginmedia) DNS (supplied by your router). So when Server core goes to search for contoso.com, it uses your ISP DNS server at 194.168.4.100 instead of 192.168.0.70. You didn't configure the TCP/IP addresses like in the book. Your preferred DNS server IP should be 192.168.0.70 not the one from your router.



You had the DNS set to 194.168.4.100 originally not 192.168.0.70.

tech_leak

That makes more sense now.. like I mentioned above, my networking knowledge is limited and when I seen in the book 10.0.0.1 etc, and changed them so it suits my home environment, I didn't realise how much specific I needed to be. Anyway, I really appreciate all the help certhelp. I am really really thankful

certhelp

tech_leak wrote: »

That makes more sense now.. I am really really thankful

You are welcome.