I didn't set this up originally, so I have to work with what's there. Owner of this system had a falling out with his prior IT support. They’re gone and I’m the new hire. I tried, but the prior guy is being obnoxious and of no help. So I’m on my own.
I shutdown and disconnected everything from this server machine so I could take it outside, open the cabinet and blow a few years of dust and dirt out of it. Took it back in, hooked everything up and powered on. After that, no one could access anything on the server from their workstations. It was then that I discovered all the data was on a virtual machine. After screwing around with the settings (yep!, this dummy changed things!) I found the error of my ways to the point of being so embarrassed; I was tempted to create a new account for this forum so folks wouldn't know who I 'really' am.
Host machine is SBS 2008 Standard and is a lone domain controller on a network of 10 workstations joined to this domain. It has four physical NICS in it, of which only one is used for a physical connection to a router for both Internet and local domain networking. DHCP is not used on this domain network, as all workstations have a manually entered IP configuration.
Seems when I connected it back up after cleaning and blowing it out, I plugged the CAT5 cable from the router into a NIC different than the one it was originally plugged into. It was only after adding/deleting virtual adaptors that I discovered/realized my ignorance.
I shut down the VM and deleted all virtual NICs, then restarted the server. Here's the setup before I get into the details.
Host Machine: SBS 2008 Standard with four physical NICS. Only one is used for physical CAT5 connection to router for both Internet and local domain network access. (I didn't originally set this up, as I'd not have done it that way)
Virtual Machine: SBS 2008 Standard set up as a file server only and joined to the domain. The VM needs to be accessible from the local domain as a file server, and a 3rd party needs to be able to remote via RDP into the VM from the Internet. Note the RDP is direct, and not through an RD Gateway. (Again, I didn't set this up originally)
Right now, in Hyper-V Manager there are no virtual NICS on either the host machine or the VM. I am using instructions obtain from these forms to install and set the virtual network up again, hopefully just as it was originally.
In the Hyper-V Manager, after confirming the VM is in the OFF state, I right click the host machine and select Virtual Network Manager. I then go through the process of adding an external virtual NIC, binding it to the physical NIC #1 I’ve actually got the CAT 5 plugged into. I click Apply and the “applying your settings” window/progress bar stays open and active forever.
I don’t think it’s freezing, because it task manager it shows status as running. I’ve left it for 30 minutes, and end up having the “end task” on it in task manager. Then when I re-open Hyper-V Manager and check in Virtual Network Manager, I see the NIC is added, but it’s not external – it’s private. I can then delete it with no problem. When I reboot the server and try again, there’s no change. I’m going around in circles here and not sure what I need to check/fix.