OK, here goes. I have a client who had a Windows 2003 server that crashed due to major hardware issues. It is a Doctors office with patient records dating back 15 years. We tried to remove the databases and move them to another server and kept running into corruption errors. We worked with the manufacturer of the software but got nowhere as the application was sold to IBM in '07 and there is no support options left. We made a VHD of the OS and put it on a Windows 2008R2 w/Hyper-V server. We demoted the OS and joined it to the new 2008 servers domain. Everything was working fine for the initial tests for access to the data. The next step was to get connectivity from the workstations to the VM OS for the application, again all worked well. The sticking point right now is that I have the VM (W2K3) configured so that everyone has access to the "old server" for the legacy software, but cannot figure out how to configure access for the 2nd nic which connects directly to the Xray machine. The hierarchy I have in mind is this:
Nic one is an Intel 82574L. It is configured with a 192.168.21.20 IP
Nic2 is a Intel 82579LM with an IP of 10.0.0.1 (the vm nic has 10.0.0.2)
This is the way the old server was connected. The first network card for the internal network and the second nic configured for 10.0.0.1 connected to the Xray machine.
This is my f1rst attempt into the virtual arena and I am getting confused as to the proper way to configure this. After playing around with the network connections naming I have attempted to name the connections for their purpose.
In the Virtual Network Manager I have 3 listings:
1: Scanner Network Connection. It is set up as external on the 82579LM card (Nic2) Allow management checked.
2: W2K3VM Connection is on the 82574L (Nic1) also as external with All management checked
3: Local area connection set for internal only. I am assuming that it was there upon installing the Hyper-V.
Within the VM I can click on the lan connection which I named "domain name" connection it shows the proper IP address 192.168.21.21.
When I try and enable the 2nd virtual nic it has an IP of 10.0.0.2 along with the proper subnet for connection to the Xray machine. The only problem is it does not connect and the connection with the workstations on the lan is interrupted.
Upon trying to connect the second nic on the host server It says there is connectivity. With the vm it shows it is also connected but the cannot access the xray machine and the workstations have no access. It is hopefully something simple that I just do not see. Any suggestions would be appreciated.
It now seems that the AD DNS which worked fine before enabling the second nic had malfunctioned. The host OS DNS gives an error now that says: The server scan could not be contacted ther error was: A security package specific error occurred.
They are using Symantec End Point Protection 12.1.2 and I have set up (as a test) rule to allow all traffic both ways for IP and UDP traffic.
I have looked at so many posts I am lost for a solution.
Sorry for the convoluted post. Thanks for the help!
Devin