Problem with NAT is:

Office and the OS won’t find the KMS server and will inactivate.  You’ll have to run the VPN from within the VM and manually run the KMS activation scripts for both products when that happens.  I’m not even positive that doing so will work

AEH

> On Oct 1, 2015, at 4:31 PM, Ernie Buford <[log in to unmask]> wrote:
> 
> I believe it is set to "auto"... and I have been using wifi today (although I often plug in when at my desk). DNS problems were indeed among the symptoms this morning. Absent those issues, I can live with NAT (if it functions) ... as I plug in often enough to take care of M$ auth issues.
> 
> On 10/1/2015 3:45 PM, J. Greg Mackinnon wrote:
>> Bridged does not work very well with Wi-Fi, if I recall correctly. Have you configured bridging to use your Ethernet connection, or is it set to "auto"?
>> 
>> NAT with work regardless of the host machine NIC that is used behind the scenes, but can cause some problems with name resolution, amongst other potential problems.
>> 
>> -J. Greg Mackinnon | ETS Systems Architecture and Administration | x68251
>> 
>> On 10/1/2015 3:42 PM, Ernie Buford wrote:
>>> It can be trouble diagnosing network problems on a day when the network itself is having problems, so I bring my current network issue here....
>>> 
>>> A Windows 8.1 VM running in Fusion on a Macbook Pro could only get "limited" (i.e., worthless) network connection this morning. I noticed that the adapter for this VM was set to NAT. Recalling that Bridged was the preferred setting, I changed it to Bridged, which helped initially. That was at home this morning. Now, back on campus, the connection is not working in Bridged mode, but *does* work if I change it to NAT.
>>> 
>>> Does this make sense? Is there some other config I should be adjusted to make this work in Bridged mode?
>>> 
>>> Ernie

Andrew Hendrickson
CAS IT Administrator
UVM, College of Arts & Sciences

802-656-7971

[log in to unmask]

To submit a request for service please use:
http://footprints.uvm.edu/ashelp.html