![]() ![]() If that's the only solution then I have another NIC I can enable and dedicate to VMware. I am going to try again with a custom adapter and network bridge as in this post - this has worked once before but I removed it when I upgraded to Workstation 7, and I would like to avoid the bridge in Windows. The testing above was done on VMware Workstation 7.0.0 on Windows 7 圆4 RC1, but I am having similar issues with bridged networking on VMware Workstation 6.5.3 on Windows 7 x86 RTM, on my work laptop. UDP connections to ports 52, generated packets as expected - lots of traffic both ways. UDP conncetions to port 53 generated an ARP request (and response from the router), then silence. TCP connections to port 53 generated packets as exepected - 3-way handshake, lots of traffic both waysI, 3-way teardown at the end. At the same time I captured traffic with Wireshark ( ) on the host PC and filtered for the VM's hardware address. I used the tool pcattcp.exe ( ) to test sending both UDP and TCP traffic to port 53 on my router as well as other random ports. Surfing with hosts file entries works OK. My VMs get a DHCP address from my local router, I can ping the gateway, but I can't surf because I can't resolve domain names. Similar to other users I'm having trouble with VMs using bridged networking that I don't have using NAT or host-only adapters. ![]() VMs cannot perform DNS queries with bridged networking on a Windows 7 host. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |