• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 875
  • Last Modified:

VMWare Server on Vista SP1 - WLAN Bridged, duplicate ARPs

I'm trying to run VMWare guest OS with VMWare Server 2.0.2 on Vista SP1. The only valid network connection is AVM WLAN via USB, which works good. This connection is not using the Vista WLAN service, but an own one.
IPv6 is not bound to the WLAN NIC.

When I want to bridge in VMWare, IP address requests and checks (DHCP, ARP) are done twice, once with the VMWare MAC, once with the WLAN MAC. The OS is thinking there are duplicate IP addresses hence. NAT and DHCP NICs work, but do not allow for LAN traffic of course.
0
Qlemo
Asked:
Qlemo
  • 9
  • 6
1 Solution
 
WolfhereCommented:
Try assigning an IP to the DHCP NIC rather than letting DHCP do its thing.
0
 
QlemoC++ DeveloperAuthor Commented:
DHCP isn't the issue. Windows OS' check for the IP address they have when restarted. Any ARP to check for the own IP address will have the same (duplicate) result.
0
 
ryder0707Commented:
What kind of LAN traffic you want to forward to the VM?
Fyi, LAN traffic is still possible to reach the VM via port forwarding, check the "Virtual Network Editor" from the start menu
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
QlemoC++ DeveloperAuthor Commented:
ryder,

The guest OS' should be full-integrated part of my LAN network, as I need to test VPN connections (over own tunnels or those of the host), routing aso.. I don't want to add another level of routing for the "VM network", as this might introduce several issues more.

Could you elaborate on the port forwarding? "Virtual Network Editor" isn't "Manage Virtual Networks", I suppose? Up to know, I always used bridged VMs (on other PCs).
0
 
ryder0707Commented:
Yeah its the same thing(its called "Virtual Network Editor" in workstation), under NAT configuration, you can setup port forwarding on the host for specific port for specific VM ip address
0
 
QlemoC++ DeveloperAuthor Commented:
Ok, I tricked the VM into getting connection, by using a /25 subnet of my /24 LAN on NAT. That would be a appropriate workaround, as the connections are usually outbound. But I'm not certain about what the NAT device does, to be blunt. I did not define any port forwarding yet, but can reach the VM guest by its associated IP address (no NAT, then?).
0
 
QlemoC++ DeveloperAuthor Commented:
I tried Virtualbox 3.1, which does not have that issue. Seems to be VMware-related.
0
 
ryder0707Commented:
Sorry i missed your previous update. Btw, I'm not clear what is your exact issue?
How do you setup NAT in vmware? You should not be able to reach VMs from outside host if you configure NAT for each VM
The NAT device is for VMs to reach Internet by sharing the host IP address, similar to how normal internal office network go out to Internet via a router, NAT is configured at the router to hide the Internal IP address
0
 
QlemoC++ DeveloperAuthor Commented:
My exact issue is that I do not want to use NAT mode, but Bridge mode. Since I have two workarounds now (VMware NAT or Virtualbox), I might just wait for the next VMware Server release, and try again then.
0
 
ryder0707Commented:
If you bridge the connection directly at the host level, you should not have this problem with vmware server
In this case, you cant assign the USB device directly to the VM
0
 
QlemoC++ DeveloperAuthor Commented:
> "If you bridge the connection directly at the host level"
 Isn't that exactly what I do if I use the "Bridged" network type?
0
 
ryder0707Commented:
You said "This connection is not using the Vista WLAN service, but an own one."
Perhaps i misunderstood, it sounds like you present the USB device directly to the VM
Or did you map using "virftual network editor" to bridge directly your usb wlan device?
0
 
QlemoC++ DeveloperAuthor Commented:
Strange, after the Virtualbox installation my XP VM works in Bridge mode. Previously I had the same issue there. Now only my W7 VM shows the "duplicate IP" symptom.
0
 
QlemoC++ DeveloperAuthor Commented:
I had both tried to use "Automatic" and static assignment for the WLAN device. I never passed the USB WLAN stick thru as USB device. My VMs are working with the Intel NIC emulation driver.
0
 
ryder0707Commented:
Oh ok perhaps its a device issue becoz i dont have this problem with aztech wl230
0
 
QlemoC++ DeveloperAuthor Commented:
I assume this is a VMWare-only issue. I will try again with the next VMWare Server release. For the time being, I'll use Virtualbox instead.

Thanks ryder0707 for trying to help, to no avail.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 9
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now