Unsurprisingly the frame rate is looooooooow…… But it was worth a try.
Archive for the ‘Uncategorized’ Category
When you first put a network card into a Windows machine it’ll ask which “profile” the network should abide by. This setting relates to which set of firewall rules to apply the machine as its connecting to the network.
Public – means you don’t trust the network you’re attaching to and firewall rules should be stronger.
Private – means you’re on something like you’re home network so the rules are more lax.
Domain – means you’re at work, so again rules are less strict.
On a client Windows machine its (fairly) easy to change these by doing a search for HomeGroup in Cortana or the search bar.
On a windows server its slightly trickier (since HomeGroup is a consumer technology and doesn’t belong on servers). In this case we use a little administrative powershell:
# Shows the current config
# sets the profile to Private ("Ethernet" is the name of the network card in this instance)
set-netconnectionprofile -InterfaceAlias Ethernet -NetworkCategory Private
I wanted to launch a couple of VMs on my test box with one server acting as a DHCP server to another on an “internal” defined network.
Its taken me a couple of days to figure out why this was happening and I’ve installed Windows/Linux, turned firewalls on and off and messed with many Hyper-V Settings down to the point where I was analysing DHCP packets using wireshark. I could see the DHCP “client” requesting an IP and the server offering one out, but the the client wouldn’t take it. After many installs and re-installs I got to the answer
The answer I found is to setup an internal network switch normally like this:
..and then on the configured network cards:
Set Protected Network on both VMs to unticked. That seems to work….