Networking with Windows 2016 - Hyper-V

[Jordansco]

Howdy,

 

I'm currently trying to get all of this done on my Windows 10 Pro laptop. I'm having a lot of problems within this outline. If anyone can explain all of this word for word that would be great. I can't get any of the servers to communicate. I have my virtual switch as internal only. 

 

 

Canada - DNS/Web Server - 172.16.101.1

                                               255.255.255.0

                                                  |

                                                  |

 

                                      172.16.101.2

                                      255.255.255.0

 

Japan - DHCP Server              |

                                     

 

                                      172.16.102.1

                                      255.255.255.0

                                                  |
                                                  |

France -                        172.16.102.2

                                      255.255.255.0

 

 

 

 

Step 1: Installation and configuration of the 3 Windows Server 2016 systems All servers must be members of the group AUTOMOBILEFIRMSOFTWARE.

 

Step 2: Installation an configuration of DHCP services
The DHCP service must be configured on the JAP server; it will supply the IP 
addresses to FRA. JAP must be configured with a static IP address and FRA must always receive the same IP address upon startup

 

Step 3: Configuration of the static IP routing
Each server must communicate with the others. Since some servers or are different subnets you must configure static IP routing to facilitate communications.  The JAP server can be used for IP routing (dynamic routing protocols must not be used).

 

Note: Static routes can be configured using the command line utility ROUTE.EXE or the Routing and Remote Access Service (RRAS) console. It is much easier to create static routes using a GUI utility than with the command line utility.

 

Step 4: Installation and configuration of DNS services
The DNS services must be installed and configured on CAN; and they must service all the other servers. The DNS domain name «AUTOMOBILEFIRMSoftware.com » must be created. The host name resolution functions from an IP address and host name are required.

 

Step 5: Installation and configuration of VPNs
In order to ensure that the connections between the 3 sites are secure, you must implement site-to-site VPNs for the two connections: CAN to JAP and JAP to FRA.

 

Step 6: Implementing DFS

Shared folders must be created and configured on all 3 servers. These folders will 
contain sales specification files and data for all sites. The users must be authenticated before accessing the folders. They must not have modification rights in the folder.
To enhance the availability of this information, reduce the amount of traffic on the site-to-site connections and provide redundancy, the shares must be linked together with the Distributed Files System (DFS)

[Master Disaster]

Do your own damn homework

 

Seriously though, this is a pretty huge undertaking and would take WAAAAAAAY too long to explain completely. You need to be more specific with what exactly the problem you're having is.

[Jordansco]

I've installed all the 2016 servers on my Hyper-V. I've installed DHCP and DNS on all of them.  I can't get Japan or France on the same domain. Canada is my forest domain....but for some reason I can't ping eachother or add any of them to my domain.

[Master Disaster]

57 minutes ago, Jordansco said:

I've installed all the 2016 servers on my Hyper-V. I've installed DHCP and DNS on all of them.  I can't get Japan or France on the same domain. Canada is my forest domain....but for some reason I can't ping eachother or add any of them to my domain.

 

Go back and check the forest map you posted in the OP

 

Also you need to define a static route so the subnet can connect to the main domain. Right now you have 3 DNS servers running (which isn't actually a problem but is unnecessary) and 3 DHCP servers all fighting with each other.

 

Canada needs ADDC & DNS (DNS is a prerequisite of ADDC anyway) and should be a static IP. Japan also needs to be a static IP, it also needs DHCP and should handle IP addresses for anything below it. France should be getting its IP from Japan via DHCP. Next Japan needs a static route to Canada and finally Japan & France should be using Canada as a DNS. Once all thats done everything should connect to the ADDC on Canada.

 

Wait, I got Canada & Japan reversed, anywhere I said Japan needs to be Canada & vice versa. Fixed