You can also access the ‘new-TestCasConnectivityUse’r script from your Exchange 2010 installation folder…by default its under ‘C:\Program Files\Microsoft\Exchange Server\V14\Scripts’

If you look carefully at the “Name” column and “Device Name” columns, and then in Hyper-V Virtual Network Manager you should be able to figure out the chain of adapter usage (physical and virtual).

Note that when I have multiple NICs, I rename the objects in the “Network Connection” window so I can easily differentiate between the LAN and WAN NICs.

For me, the LAN side worked fine, but I had problems with the WAN connection (2 different servers, identical problem). Through trial and error, I needed to change the “Virtual WAN” adapter – this would be the adapter that actually has the WAN IPv4 address (as Neil describes: the virtual adpater). From some other threads, I disabled anything to do with Offload, then re-enabled all except the IPv4 Checksum Offload property – problem *finally* solved!

This applies to the host server, but I suspect if I had a VM using the Realtek I would have to make a similar change in the VM.

Thanks for the post. I had a simialr problem however i stumbled into not being able to run the script. Followed michael_f’s steps below and creating the account worked a treat.

http://social.technet.microsoft.com/Forums/en/operationsmanagermgmtpacks/thread/a134dcd1-2678-406e-8937-584b36746bf2?prof=required