Windows 8 Hyper-V Networking Problem

Hi,
after I installed the Hyper-V Feature on my Windows 8 RTM machine, my plan was to install a Win7 virtual machine via network-install.
The problem is after configuring the virtual switch, my host-system has no connection to the network anymore and the network-boot isn't possible too.
After configuring the virtual switch a new network adapter appears in the networkadapter management. The physical adapter has no properties activated except the virtual switch-property. The new adapter is configurerd like the old physical adapter. The adapter
is configured to use DHCP. Even changing it to a static IP doesn't change anything. There are also no changes (for the guest-machine) if I disable the shared use of the network-card in the virtual switch management.
If I use my WLAN-Adapter instead of my Ethernet-Adapter it is the same except there is a network bridge in the networkadapter management more compared to my Ethernet-Adapter (so there are two more adapters).
Configuring the virtual switch with my UMTS-Card is like the Ethernet-Card.
The Ethernet-Driver is updated to the newest driver by Microsoft.
Has anyone an idea what is happening there and how to solve that issue?
www.krifi-ware.de www.nless.de

I am in basic agreement that Microsoft has failed in a major way with this virtual switch configuration and I would very much like to have back the many hours that I have spent trying to figure out why this seemingly simple thing does not work as expected.
I followed the instructions I saw from a Microsoft employee on a youtube video for setting up a virtual switch on his laptop. It just so happens that the desktop I am using to run Windows 8 with Hyper-V has on-board Ethernet and I added a PCI wireless
NIC that I had laying around (not for use with Hyper-V, but because I was thinking about re-locating the desktop). Needless to say, after following youtube guy's instructions, I discovered that both the wired and wireless connections have to be connected
in order for the host and the VMs to function.
So how you can make this work with a single NIC is still beyond me. I started this whole exercise while prepping for exam 70-646 (Windows Server 2008) because I would like to set up multiple virtual machines to complete the exercises in the Microsoft
exam prep book. This issue, while interesting, has been an extra delay in achieving my training goal.
And here is a dumb question: Why must the virtual switch have an IP address of 192.168.137.1? I should be able to give this virtual switch any address that I choose. Not that it is a big deal, but it just seems weird and like a really strange
restriction.
Also, even with the two-NIC setup, and following the exact instructions provided by Mr. Microsoft Employee on youtube, I notice some odd symptoms on the Windows 8 host now. Sometimes the browser takes longer to bring up sites than it should.
And here is something really interesting, the Windows 8 Store now thinks that I have no internet connection, so I cannot install any apps from the store now. I suppose I cannot update any apps, either.
With two NICs to work with, you would think that Hyper-V would at least leave me with one working NIC, but instead, it appears to break both of them.

Similar Messages

Windows Vista and WiFi networking problem with MackBook Air

Hi, everyone!
Thanks in advance for the following help.
For some specific programms I need Windows Vista to be set up on my MacBook Air.
The problem with Broadcom WiFi adapter.
While moving large files over home network it hangs and looses the wifi network. It works OK while surfing the internet or doing other low traffic job. But when it comes to 2 MB/sec transfer it doesn't work. I tried two different routers, no positive result. PC works propely on any file sizes. After booting the Leopard the problem goes away. So it is onle Windows Vista problem.
May be drivers? I tried 4.170.25.19 Windows Vista drivers from Broadcom - it didn't help. But I am not goog in driver settings in Control Panel, so may be the solution is there.
Any ideas how to solve it?
Thanks for help in advance.
Andrey.

Hello Nescom. Welcome to the Apple Discussions!
I'm afraid I really don't have an answer for you but I can offer my experiences with large files transfer with Vista. My current home network is a combination of Windows PC, Windows Servers, and Macs. Large file transfers between most of them have relatively the same performance, except when transferring large files from the Vista PC to any other OS. It is demonstrably slower. Interestingly, transfers between Vista machines does not appear to be a problem. I understand that this is a known problem by Microsoft and was supposed to be fixed with Vista SP1.
So the problem might not be your network, but Vista itself. I'm curious if you have this problem when transferring large files to another Vista device?

Hyper-V VM Windows Server 2003 R2 SP2 Network Problems

Hi Guys,
I am trying to setup a new VM in my lab (I am using windows 8.1 in my host) with Windows Server 2003 R2 SP2. I already installed the integration services in that VM, the network adapter is ok (Hyper-V network adapter). Well, everything it seems to be
ok, but my W2K3 Machine keeps getting 169.xxx ip. My host is wireless , the virtual switch is ok, since I have other 4 VM (W2K8, W2K8R2, W2012, W2012R2) working fine with that switch and having access to the internet, just this VM with W2K3 is not working.
Do you guys can help ?
Thanks

Please check the properties of your NIC adapter in W2K3 if the Client for Microsoft Network is installed.
And also try to compare the network setting for other VMs NICs in Hyper-V to find the deference.
I would create new VM and install clean W2K3 for testing.
If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY
suggestion in a test environment before implementing!

Windows 8.1 Pro has error while joining domain, while windows 7 pro has no problem to join in the same network

I am having the same issue as posted in http://social.technet.microsoft.com/Forums/windows/en-US/6ea57e5f-6e9d-49bd-9dd7-832ea84c0276/windows-81-pro-will-not-join-domain?forum=w8itpronetworking
There are a few other people have the same issues. However there was no real solution provided although the post was marked as answered. I am posting it here again and hopefully I can get some help to solve this issue.
We got two new PCs, one with windows 7 and the other with windows 8.1 Pro. In the same network with domain, the windows 7 pc has no problem at all to join the domain. However the windows 8.1 Pro won't join the domain. On the windows 8.1 Pro computer,
I can ping the other computers in the network. The error message says:
An Active Directory Domain Controller (AD DC) for the domain "cmi" could not be contacted. ...
In my case, the domain name is "CMI". I am sure the DNS setting is correct. What did I do wrong? Any help is greatly appreciated. Thanks.

I tried the solution in that article.
In HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters folder, there is no
NeutralizeNT4Emulator. So I followed the instructions and created one, and set the value to 1. Then I restarted the computer and tried to join the domain again. I got the same error. Below is more from the netsetup log file:
06/04/2014 21:36:37:256 -----------------------------------------------------------------
06/04/2014 21:36:37:256 NetpValidateName: checking to see if 'XPS8700' is valid as type 1 name
06/04/2014 21:36:40:256 NetpCheckNetBiosNameNotInUse for 'XPS8700' [MACHINE] returned 0x0
06/04/2014 21:36:40:256 NetpValidateName: name 'XPS8700' is valid for type 1
06/04/2014 21:36:40:256 -----------------------------------------------------------------
06/04/2014 21:36:40:256 NetpValidateName: checking to see if 'XPS8700' is valid as type 5 name
06/04/2014 21:36:40:256 NetpValidateName: name 'XPS8700' is valid for type 5
06/04/2014 21:36:40:256 -----------------------------------------------------------------
06/04/2014 21:36:40:256 NetpValidateName: checking to see if 'cmi' is valid as type 3 name
06/04/2014 21:36:40:272 NetpCheckDomainNameIsValid for cmi returned 0x54b, last error is 0x0
06/04/2014 21:36:40:272 NetpCheckDomainNameIsValid [ Exists ] for 'cmi' returned 0x54b
----------------below is the error message from the pop up window
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.
The domain name "cmi" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain "cmi":
The query was for the SRV record for _ldap._tcp.dc._msdcs.cmi
The following domain controllers were identified by the query:
cmi-dc2.cmi
cmi-dc1.cmi
However no domain controllers could be contacted.
Thanks.

Hyper-V 2012 R2. RemoteFx. "The remote session was disconnected because there were network problems during the licensing protocol. Please try connecting to the remote computer again."

After a Installation from Windows 8.1/windows 7 everything works fine. For example Install updates and Software. If I connect the first time a remotefx card i can use RDP as well. But if i restart the host I get the mentioned error. What can I do. These
Hosts are not in a domain configuration. I tried it too but there was no difference. I didn't discovered any errors in the eventlog, too. Only an actviex error. But same errors occurs with a succsefull rdp session.
Also strange is if i start the vm without a remotefx card it works fine again. Only session with a Remotefx card aren't possible anymore.
Is there a bug or something. I tried it many times with the same error.
Maybe someone can help me.
kind regards
Tobi

Hi Tobi,
Thank you for posting in Windows Server Forum.
For a workaround, please try to perform the two steps.
1. Do NOT enable RDP 8 on the Windows 7 SP1 VM. You should install RDP 8 and update the ICs though.
2. Change the connection setting on the client from "Automatically detect" to "LAN"
Please check again below thread for information.
a. "The remote session was disconnected
because there were network problems during the licensing protocol" after enabling RemoteFX Windows 8 VM
(Please recheck answer by “dgeddes”)
b. "The remote session
was disconnected because there were network problems during the licensing protocol" After Installing RemoteFX
Hope it helps!
Thanks,
Dharmesh

Error trying to mount the DVD to a network based ISO image in Windows 2008 Hyper-V RC0

Greetings,
When I try to configre the guest OS settings to mount the CD/DVD drive to an ISO image I have setting on a file share, I consistently get an error. The only time I have been able to mount an ISO since upgrading to RC0 (I don't remember if I tested this in the BETA) is when the ISO is locally on the Windows 2008 Hyper-V server.
To be specific, I get the following error:
Virtual Machine Connection (title of the window)
Inserting the disk failed.
Failed to add device 'Microsoft Virtual CD/DVD disk'.
User account does not have sufficient privelage to open attachment '\\remoteserver\share\ISONAME.ISO'.
Error: 'General access denied error'
'NEWGUESTOSNAME' failed to add device 'Microsoft Virtual CD/DVD Disk'. (VMID 26C8B66F-5D3F-47F9-9D80-474D0F778522)
'NEWGUESTOSNAME': User Account does not have sufficient privelage to open attachement '\\remoteserver\share\ISONAME.ISO'.
Error: 'General access denied error' (0x80070005). (VMID 26C8B66F-5D3F-47F9-9D80-474D0F778522)
I am not sure what credentials it is using. It looks almost like it is using the new computer name as credentials or something like that. The account I am logged in as at the time is a Domain Admin and has access to every server and every share. I can browse to the ISO just fine through the Hyper-V Insert Disk function, it just won't take.
I have checked the Hyper-V server settings and the Guest OS settings and can't find where to specifcy what account to use to connect to remote ISOs. Anyone have any clue on what I am doing wrong?

Thanks for the various replies.
Understood it is an issue with the Hyper-V server computer account getting the files, and not the actual guest OS. At this point I think I will just copy some ISO's to the server. I did note the last time I used a "local" ISO that I had to manually type out the local path to the files on the server, as when I tried to browse to the local server drives through the console I got an error about connecting to the local server (which wasn't really local) through the network drives. I don't remember the exact error, but I know I couldn't get it to point to the ISO on the D:\ drive through the browse feature, but rather I just typed out the path and it was fine. That too seems like a bit of a buy/annoyance as I should be able to browse files local to the Hyper-V server, and not have to type out the path.
I guess I would ask MSFT to consider changing the behavior of the console just a little before RTM if it is being run remotely against the Hyper-V server, versus locally on it, if the permissions being used to get to the remote files are going to be different depending. I.E. It is not intuitive that the same exact action in the same exact console would behave any differently when the console is run on the Hyper-V server versus remotely against the Hyper-V server. I.E. Add in a pop-up when remotely connected to the Hyper-V server to let the user know that some permissions may not proxy through (or whatever verbiage you want to use).
This will pop-up more and more as people like me try to deploy Hyper-V on Core servers, and they used Hyper-V on a normal Windows 2008 server previously.
Thanks!

Help with Boot Camp Assistant network problem while downloading windows support system!

I need to download Windows support software, but just keep encountering a problem which says "Can't download Windows Support Software because of a network problem." What should I do? I'm currently using Boot Camp Assistant v5.0.0, and OS X 10.8.2. Help! What can I do to solve this network problem? Please and thank you (:

I have the same problem. Anyone out there? Hello?

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking and Hyper-V.

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking!
http://www.youtube.com/watch?v=8mOuoIWzmdE
Hi thanks for reading. Now I may well have my terminology incorrect here so I will try to explain as best I can and apologies from the start.
It’s a bit of both Hyper-v and Server 2012R2.
I am setting up a lab with Server 2012 R2. I have several physical network cards that I have teamed called “HostSwitchTeam” from those I have made several Virtual Network Adaptors such as below
examples.
New-VMSwitch "MgmtSwitch" -MinimumBandwidthMode weight -NetAdaptername "HostSwitchTeam" -AllowManagement $false
Add-VMNetworkAdapter -ManagementOS -Name "Vswitch" -SwitchName "MgmtSwitch"
Add-VMNetworkAdapter -ManagementOS -Name "Cluster" -SwitchName "MgmtSwitch"
When I install Hyper-V and it comes to adding a virtual switch during installation it only shows the individual physical network cards and the
HostSwitchTeam for selection. When installed it shows the Microsoft Network Multiplexor Driver as the only option.
Is this correct or how does one use the Vswitch made above and incorporate into the Hyper-V so a weight can be put against it.
Still trying to get my head around Vswitches,VMNetworkadapters etc so somewhat confused as to the way forward at this time so I may have missed the plot altogether!
Any help would be much appreciated.
Paul
Paul Edwards

Hi P.J.E,
>>I have teams so a bit confused as to the adapter bindings and if the teams need to be added or just the vEthernet Nics?.
Nic 1,2
HostVMSwitchTeam
Nic 3,4,5
HostMgmtSwitchTeam
>>The adapter Binding settings are:
HostMgmtSwitchTeam
V-Curric
Nic 3
Nic 4
Nic 5
V-Livemigration
HostVMSwitch
Nic 1
Nic 2
V-iSCSI
V-HeartBeat
Based on my understanding of the description , "HostMgmtSwitchTeam and
HostVMSwitch " are teamed NIC .
You can think of them as two physical NICs (do not use NIC 1,2,3,4,5 any more , there are just two NICs "HostMgmtSwitchTeam and
HostVMSwitch").
V-Curric,
V-Livemigration , V-iSCSI ,
V-HeartBeat are just VNICs of host (you can change their name then check if the virtual switch name will be changed )
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Another version of Leopard - Windows network problems

Like many others, I have a networking problem after installing Leopard on my G4 Powerbook. I had a successful ethernet network previously using two Windows 98 computers, an iBook G3 running Tiger, and my Powerbook G4 running 10.3.9
Only the Powerbook was upgraded to Leopard. The Powerbook can see, connect to, and read & write to all other computers using the Finder - Go - Connect to Server command. No problems, so I am better off than many others who have reported worse problems.
BUT, my Windows PC's cannot see the Leopard machine. I have done what I thought I should in the System Preferences - sharing pane. I have tried setting both folders and drives to shared, and have tried deselecting them and then selecting them again as some have suggested. My Powerbook with Leopard is still invisible to the PC's, both trying to use the "Open" command from a program, or the "Network Neighborhood" command from Windows Explorer.
Any suggestions? I know that some users cannot talk between PC's and Leopard at all, so I am glad I can at least read & write from the Leopard end!

Spoke too soon. For the past few weeks since installing Leopard, network connections have been erratic. The Powerbook with Leopard was working well yesterday, but then suddenly ceased to see the Windows computers. For the time being I have gicen up and reinstalled Tiger.
I will keep checking this forum and give Leopard another try when it seems to work better with networking.
Makes those Apple TV spots poking fun at Vista users going back to XP seem a little amusing.

Can't download Windows spupport software because of a network problem?

Hi all,
Here is my question: I have MBP early 2011 and was trying to download Windows supporting software’s using Bootcamp 5.0 but a box appears saying “Can't download Windows support software because of a network problem” so what can I do to address this problem?
Few more details:
Mountain Lion 10.8.2
Bootcamp 5.0.0
I already tried removing the proxy settings as you can see on the following picture.
Thanks

I tried to select and deselect the Passive FTP Mode to see if that helps as it is recommended by other users before posting my question here to see if that was the problem but that didn't change anytihing. I also tried it before commenting to your response if there was any change and there wasn't any
But thanks for your response.

HT4407 Is there any way to download these files manually from another source? The download from boot camp keeps stopping at around 25% and then produces the error "Can't download Windows Support Software because of a network problem". Thx!

Is there any way to download these files manually from another source? The download from boot camp keeps stopping at around 25% and then produces the error "Can't download Windows Support Software because of a network problem". Thx!

No. This issue is dicussed here frequently. The only option is to be patient and try often. Search this forum for other posts about this issue.

Another Windows 7 Network Problem

I have three Windows 7 computers (2 wired, 1 wireless) and a Mybookworld on my network at home with my Macbook Pro running 10.6.4. Before the upgrade to Snow Leopard, I had zero problems networking all of my computers together, and also never got a dropped wifi signal.
Since the installation of Snow Leopard (ordered it the day it was released), I now cannot see the windows computers in the "Network" panel. The only thing that shows up is my MyBookWorld Drive. All of the windows computers can see each other, the MBW drive, and my Macbook just fine. I can connect to the Windows computers via smb://ip but this is inconvenient and I think the reason I can't setup printer sharing.
The secondary issue is that after a short period of time, my network connection on my MBP stops responding, and I have to click "Turn Airport Off" then "Turn Airport On" (and this works in quick succession, no waiting time) and I'm good to go again. This is especially frustrating when I am away from home and want to remotely access my computer and it's offline.
I have followed the guide on about.com so please, let's not suggest that. They all have the same workgroup, smb sharing is enabled in my system preferences, my windows and mac login names are all the same (First Last).
Every once in a blue moon (read: very infrequently) my Macbook will show the Windows 7 computers.
My router's drivers all are up to date.
I'm pretty technically savvy but I can't for the life of me figure this out.

CMCSK wrote:
Have you also tried Apple's Knowledge Base?
http://support.apple.com/kb/index?page=search
Here are reasons a Windows computer might not show up:
The computer isn’t on the same local network or subnetwork as your Mac.
If the Windows computer is on a different subnetwork, you can connect to it by typing its network address in the “Connect to Server” dialog.
This is from the KB, and possibly the only thing related, because I can in fact connect by doing this.
What is a "Subnetwork" and how would I be connected to a wrong one? They're all on one router, and the Windows 7 computers are all part of a homegroup, when I dig down, they're all part of the "WORKGROUP" workgroup. In my WINS settings, WORKGROUP is currently my listed workgroup as well. This seems like it would fix that problem...

Windows Network Problems...

I have a friend and his network is all windows machines except for one Mac for video editing. They need to be able to transfer the video created to a drive on the network or directly to the computer that is going to use it. The G5 is on the internet and can see the other machines but can't access them, it gives me an error saying, "can't find the original". The windows machines can't see the G5 (and yes it has windows sharing on). I've tried to help them but I'm at a loss on this one. My network is all Macs and only 4 windows machines so for me it's windows that have to survive on my network .
There windows machines log onto a domain. Could that be an issue?
Thanks
Dave
Dual G5 2.5 Mac OS X (10.4.4)

I have a very similar issue at my workplace. I'm one of two designers using OS X, the rest of the office is on Windows.
I was having the issue discussed above. I would go through the networks in a finder window and locate the server folder I needed to get into and try to log in but I kept getting "can't find original."
I then went through the Connect to Server via 'Go' in Finder. I typed in the smb//DNSname/sharename and the login window would pop up. But when I try to log in, almost immediately it says I have the wrong name or password. I've checked it a dozen times and my password works through Mail and Entourage, but not through a direct network connection to the server.
I found a program from http://www.thursby.com/ called ADmitMac that supposedly corrects Mac OSX to Windows PC networking problems. There's a full article about it at http://www.macguild.org/reviews/review204.html.
I have not tried it considering we're a small start up and the program can get expensive compared to the cost of the Mac OS system price.
Can anyone verify that this program can correct the problem or is there another (cheaper) solution?
Could it be a setting on the windows server itself?
hope someone can help
iBook G4 Mac OS X (10.4.5)

Hyper-V Network Configuration Problem - Virtual Switch

Hi guys,
I'm looking for some help with a Hyper-V Network issues. I have been handed over a project by a client that is not fully complete and the person who built it is not available at all. The setup is a HP C7000 blade chassis and a HP SAN.
The previous guy built a hyper-v cluster with 2 nodes; HV1 & HV2 - this works fine, I can live migrate etc and all is good.
This is how it was handed over to myself, my job is to add the third node to the cluster so I have installed the OS, drivers etc. Hyper-V role and clustering role. My problem arises with the Hyper-V switch configuration.
Points;
Each node has two NIC adapters, both of these network adapters are teamed
A virtual switch is created on each node using the aforementioned NIC Team
On the existing nodes I can see the management IP for the node is set on the virtual switch adapter
On the third node (HV3) I created NIC Team using both of the NIC's, I then created an external virtual switch using this teamed network adapter. However when I try to apply a management IP address to the virtual switch adapter it won't respond and I see
a yellow triangle on the network adapter in the corner. When I remove the virtual switch and apply and IP address to the NIC Team the server is contactable and shows in the Cluster manager as up. However the problem then is I don't have a virtual switch.
If someone could help me with this that would be great - please tell me if you require further information.
Below is a screenshot of the adapter for HV1 (working fine) from failover cluster manager;
thank you advance :)

Hi Brian, thanks for the reply. This is what I tried initially. However I just restarted the server I tried it again - still no luck.
Just to clarify when I team together the two flexfabric network adapters and apply an IP address to the team for testing - the team works fine, so the team doesn't seem to be an issue.
Once I create the virtual switch and assign the team to the switch and enable management OS to share I apply the IP address to the vEthernet adapter and I can't ping the default gateway or anything for that matter.
Any other ideas ?

Bug in Hyper-V: Network Bridge's ARP proxying broken in certain scenarios

Edit
I am quite sure now this is a bug. The ARP proxying does not work for VMs if the packet-recipient is not directly attached
to the external vswitch that is bridged to the wifi-nic!
/Edit
I am running a test lab on my Windows 8.1 using Hyper-V.
My problem is, that the virtual LAN has limited connectivity, when the external vSwitch is configured to use the wifi interface, instead of the cable interface. I am troubleshooting this issue for hours now and I reached the point where I believe the Network
Bridge, that is created by the Hyper-V Virtual Switch Manager, is not forwarding packets.
Pings are delivered from 192.168.178.2 to 192.168.178.1 and back again.
Pings from 192.168.0.10 are delivered to 192.168.178.1, and the reply does reach the wifi interface …
== Trace on the WiFi interface ==
Here you see a log of the trace on the WiFi interface of the Hyper-V-Host,
while 192.168.0.10 is pinging 192.168.178.1
No Time Source Destination HW Source HW Destination Protocol Info
3 0.003340000 192.168.0.10 192.168.178.1 24:65:11:cc:c0:9e 24:65:11:2b:35:e4 ICMP Echo (ping) request id=0x0001, seq=44/11264, ttl=127 (reply in 4)
4 0.006094000 192.168.178.1 192.168.0.10 24:65:11:2b:35:e4 24:65:11:cc:c0:9e ICMP Echo (ping) reply id=0x0001, seq=44/11264, ttl=64 (request in 3)
5 0.006152000 192.168.178.1 192.168.0.10 24:65:11:cc:c0:9e 24:65:11:2b:35:e4 ICMP Echo (ping) reply id=0x0001, seq=44/11264, ttl=64
… but is never forwarded to the Network Bridge interface.
== Trace on the Network Bridge interface ==
Here you see a log of the trace on the Network Bridge interface of the Hyper-V-Host,
while the Hyper-V-Host is pinging 192.168.178.1 (#1)
and the 192.168.178.2 is pinging 192.168.178.1 (#7)
-> Note: The ping-reply from 192.168.178.1 to 192.168.0.10 is missing!
1 0.000000000 192.168.178.1 192.168.178.21 24:65:11:2b:35:e4 24:65:11:cc:c0:9e ICMP Echo (ping) reply id=0x0001, seq=9/2304, ttl=64
7 7.852500000 192.168.178.1 192.168.178.2 24:65:11:2b:35:e4 00:15:5d:b2:21:18 ICMP Echo (ping) reply id=0x0001, seq=439/46849, ttl
How do I solve this problem?

Hi,
In that article I read this :
" This is supported on wired physical NICs (by putting the NIC in promiscuous mode),
but not supported on wireless NICs since the wireless channel established by the WiFi NIC and its access point only allows Ethernet packets with the WiFi NIC’s MAC address and nothing else. In other words, Hyper-V couldn’t use WiFi NICs for
an external switch if we continued to use the current virtual switch architecture."
Based on my understanding , the prerequisite of external virtual switch is physical NIC supports promiscuous mode . The blogger's opinion is that wireless NIC do not support promiscuous mode ,so the workaround "mac bridge " arises .
(but "microsoft MAC Bridge" is designed by microsoft to support creating external Vswitch on these wireless NIC which doesn't support promiscuous mode , so I think it is not a bug , it is by design ).
Also we have not yet tested with a wireless NIC which supports promiscuous mode .
"In computer networking, promiscuous mode or promisc mode is a mode for a
wired network interface controller (NIC) or wireless network interface controller
(WNIC) that causes the controller to pass all traffic it receives to the central processing unit (CPU) rather than passing only the frames that the controller is intended to receive. "
http://en.wikipedia.org/wiki/Promiscuous_mode
Best Regards
Elton JI
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows 8 Hyper-V Networking Problem

Similar Messages

Maybe you are looking for