Hi Sir,
To narrow it down , please remove external virtual switch which binding to teamed NIC .
After that , Please test that teamed NIC and check the enabled protocol through following powershell command :
Get-NetAdapterBinding -Name "ethernet"
("ethernet" is the name of teamed NIC)
By the way , please change teaming configuration to "switch independent/hyper-v port" if you didn't change anything on the physical switch that the IBM server is connecting to .
If the teamed NIC works fine , you may create an external virtual switch again .
Further information please feel free to let us know .
Best Regards,
Elton Ji
Thank for your reply. Current NIC teaming configuration "switch independent/dynamic" . I think problem issue when I create virtual switch .Some delay network , I have disable VMQ, turn off TCP offload, change MAC NIC teaming because MAC conflict (NIC teaming and vEthernet have same MAC). I still can't remote desktop, DNS bounce, request time out 2 second. If I remove Hyper V role , DNS and remote desktop working .My NIC server is IBM I350
Hi Sir,
After you binding virtual switch , please run the following command and post the command output :
Get-NetAdapterBinding -Name "ethernet"
("ethernet" is the name of teamed NIC)
Best Regards,
Elton Ji
Here is result command output
DisplayName --- Enable
Link-layer Topology Discover Responder --- True
Link-layer Topology Discover Responder Mapper I/O --- True
Microsoft Network adapter Multiplexor Protocol --- True
Clients for Microsoft Network --- True
Microsoft MAC Bridge --- False
Microsoft Load Balancing/failover Provider ---True
Qos Packet Scheduler---True
File and Printer Sharing for Microsoft Networks ---True
Internet Protocol version 4 TCP Ipv4---True
Internet Protocol version 6 TCP Ipv6---False
- Edited by ghost9119 2 minutes ago