MCITP 70-640: Installing Active Directory on Server Core

[jenskepense]

@itfreetraining

I managed to fix my issue.

Apparantly I had to set both of my network adapters of my virtual machines to "Internal network", similar to what you said.

I'm so glad I finally found the problem after hours of struggling... :D

[itfreetraining]

@jenskepense Excellent good to hear.

[jenskepense]

I have configured my dc1 like this now:

192.168.1.3

255.255.255.0

192.168.1.1

127.0.0.1

I have added 192.168.1.3 as the DNS server for my dc2, but it still fails to find it. Seems like my dc1 and dc2 are not finding each other.

Should I be able to use the ping command in the command prompt to reach each other?

Like if I type ping dc2 in the command prompt of my dc1, should I get a response?

Also, should I be able to use "net use * \\dc1", cause I can't as well. :s

Thanks!

[itfreetraining]

@jenskepense Servers should be able to ping each other. Make sure the DC's are on the same subnet. DC2 should have an IP address 192.168.1.*

When using virtual machines ensure that both computers are on the same virtual network. They should be by default.

The command net use * \\dc1 will connect to the IPC share. The IPC is used for communication. This is used to browse the computer and show shares and printers. If you run net use this will show shares that are connected. So this should work.

[jenskepense]

@itfreetraining

Yea that seems to be the problem somehow.

My DC1 is 192.168.1.3

My DC2 is 192.168.1.2

I let them use 192.168.1.1 as the default gateway.

Afaik my virtual machines are using the same virtual network as you say.

I can't really test it out without using Virtual Machines though, I'll try starting from scratch again and see if I did something wrong.

Thanks for your efforts! These vids are really helpful!

[jenskepense]

I also get an error message when I add the first DNS server with the address of 192.168.1.1

"The configured DNS server is oncorrect or does not exist."

[itfreetraining]

@jenskepense What is the IP address of your DNS server? If it is not 192.168.1.1 you will need to change the IP address. If you are using the local server as a DNS you can use the loopback address of 127.0.0.0.1

[jenskepense]

@itfreetraining

I'm using VirtualBox and configured the first Windows 2008 Server using your Video 6 tutorial where you create dc1 and give it a static IP address of 192.168.0.14.

Now I made a second Virtual PC and am following your 7th Video.

I thought I needed to set the DNS server to the dc1 machine I have just created in the previous video.

[itfreetraining]

@jenskepense O.k, I see the problem now. It is something we need to address in future courses. The video are designed to stand alone so your should not have to refer to previous videos. The problem is when people do follow on along like you did and we have changed the network around from video to video. We basically need to have the same network for all videos to make it easier

In your case use the DNS address of 192.168.0.14 assuming you installed DNS on dc1. This should also fix the net use

[jenskepense]

When I try to execute the command:

Net use * \\dc1\it

It says:

System error 53 has occurred

The network path was not found.

[itfreetraining]

@jenskepense This maps a drive to a share called IT on server DC1. This share is not there by default and needs to be created. You are free however to use any share on the network that you want.

[VidsJust]

Hi, first thanks for these very good videos.

I just want to point out that following your series and in the last one where you configured the IP address of DC1(Which is a DNS Server too) you gave it an IP address of 192.168.0.14.But here you pointed to completly a gateway address instead of DNS Server. Thanks for checking again.

Regards