This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 14.000000000000002%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hello, I have been working trying to set up a Hyper-V test lab that I can connect to wireless networks. I finally was able to connect my DC to have internet access. I was then going to see if I could connect one of my test computers to the network using the same External Virtual Switch and configuration as the DC, it says Default Gateway is not available. the IP configuration is as follows:
192.168.2.11
255.255.255.0
192.168.2.1
My goal is to be able to get 2 Test PC's talking to the DC that is on the internet. I was just trying to test the theory of using different default gateways and networks when I need to. Let me know if anyone can help and what additional information we need. Thanks.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
In both cases the router (192.168.123.1) is not reachable. Might try deleting / recreating the external vSwitch.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Make sure the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
Hi Dave,
This is how I set my IP's and when I tried to ping the DC from Test PC 1 I got destination unreachable. Let me know if this is wrong.
DC set to:
192.168.123.10
255.255.255.0
192.168.123.1
DNS:
192.168.123.10
PC1 set to:
192.168.123.11
255.255.255.0
192.168.123.1
DNS:
192.168.123.10
Thanks.
On the both run, then attach the two files here in a reply.
ipconfig /all > C:\%computername%.txt
tracert 8.8.8.8 >> C:\%computername%.txt REM (wait until it finishes)
Here are the 2 files, I ran the second command with REM after it. TESTPC1.txt WSUS-DEMO.txt
I believe you helped me to get the DC on the internet. That is the default Gateway that work when I am at a coffee shop with their wireless. Should I run these same reports when I'm there that may give us some answers?
Yes, if that's the location where you will run from.
I tried to connect to a different network today so I would understand how to do that and not be tied to one place to see if I could get the DC on the internet elsewhere. There doing construction on the coffee shop! I set the DC to the same static IP configuration above, except the DG is .50. Restarted the DC. And, The DC did not connect to the internet. The Hyper-V External switch should not need to be changed at all, right? Said DNS server may be unavailable? Set the DNS same as DC 192.168.50.10.
The vSwitch doesn't need to change as long as the same physical adapter is being used. Sorry, no clue really without some log files. Also note it the subnet changes then the DNS reverse lookup zone should also be recreated. Please run;
Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
repadmin /showrepl >C:\repl.txt (run on any domain controller)
ipconfig /all > C:\%computername%.txt (run on EVERY domain controller)
ipconfig /all > C:\problemworkstation.txt (run on problem pc)
Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found. (no evtx files)
then put unzipped text files up on OneDrive and share a link.
So I need to go onto to the DC and create a new DNS reverse lookup zone? And once that is created it will be there for future use if I were to switch to another network and the back? Thx.
Domain controllers do not typically move around like that. The normal flow would be to delete the old, add the new and be done with it. Not saying that's causing your issues, just more of a side note.
Ok, Thanks. I will give these concepts a try and let you know.
I’m going to use the 192.168.123.1 network as a base until I can understand how to connect the test PC’s to the domain. The DC is now set as this: 192.168.123.10 255.255.255.0 192.168.123.1 DNS: 192.168.123.10 When I set it back to this it did not connect to the internet and here are the reports. https://drive.google.com/drive/folders/1mJTsaFDkmgVg_loWpwO4ZH-HyjUfwO8e?usp=sharing
Going to try to get the DC on back on the internet at City Brew (DG 192.168.123.1). The DC connected to the internet automatically using DHCP. I gave the DC a statice IP for the test PCs to join. The test PC has a static IP of 192.168.123.11 and the DC is “unreachable.” My test PC says default gateway unavailable. I will try adding this IP config as a DNS reverse lookup on the DC. When I tried to add a new pointer record it said IP invalid (192,168,123)? Here are the current reports. The first two reports will not run on the test PC. https://drive.google.com/drive/folders/1mJTsaFDkmgVg_loWpwO4ZH-HyjUfwO8e?usp=sharing
On both run, then attach the two files here in a reply
ipconfig /all > C:\%computername%.txt
tracert 8.8.8.8 >> C:\%computername%.txt REM (wait until it finishes)
Here is the link to the latest logs. https://drive.google.com/drive/folders/1mJTsaFDkmgVg_loWpwO4ZH-HyjUfwO8e?usp=sharing
The tracert did not produce an output. If it again reports destination unreachable, then you could try delete / recreate the vSwitch again. Continually moving a hyper-v host to different networks is not really a normal operation so may be somewhat problematic.
Hi Dave, I understand that this is not best practices. I am just trying to understand how I can connect virtual computers to the internet or to each other. I am just working on the 123 subnet now that I have my DC on the internet now. Is there a way to connect the test PC to the DC without it being on the internet, or does it have to be on the same switch as the DC? If the best way to proceed is to delete the External switch and add the VM's to a newly created one, I will do that. Thanks!
I don't know because the tracert did not even start.
does it have to be on the same switch as the DC?
It just needs to be routable to the domain network with these ports flowing.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/config-firewall-for-ad-domains-and-trusts#windows-server-2008-and-later-versions
I am just trying to have the DC connected to the internet so it can receive Windows updates, and then have the test PC's on that domain to be able to approve updates for them through WSUS. Do all the ports on the attached link need to be open?
Yes, assuming the pcs get the domain firewall profile nothing further needs to be done except for perimeter firewalls and or routing devices. I probably would not install the WSUS role on a domain controller though.
I guess it would be good practice to set up a standalone WSUS server. This is going to take some time and then I will probably still have this problem of getting them on the domain. I will start building that server as soon as I can. I have not worked a lot with ports. Should ports on the attached link for Inbound and Outbound ports be listed in the local port column to know that they are open?
Again, assuming a LAN and the members all got the domain firewall profile then nothing else would need to be done, (firewall-wise)
Can I ask you something else? I realize that WSUS should be on a separate server, but I should still be able to add the test PC's to the domain, which I did at one point, and be able for them to ping each other, right (or wrong)? Even though the WSUS is on that server.
Yes, that's correct, but WSUS has nothing to do with this.