DHCP Vmware fusion issue

Unanswered Question
Dec 4th, 2008

I have some clients connected to our cisco Wireless LAN controller (4402) and they are running vmware fusion 2. When connected to the wireless network their host machines do not aquire a IP when using DHCP. If you type in the IP manually it all works. If they connect by wire it works fine. If i put the host in NAT mode it works but i want it to work in bridge mode.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (4 ratings)
Loading.
dennischolmes Wed, 12/10/2008 - 14:55

The WLC does dhcp as a relay agent. Some hardware devices don't like this. Try cli command: config dhcp proxy disable

jb6846 Thu, 12/11/2008 - 21:52

We did that as well. Here is what I found out from an internal Cisco resource.

The WLC software does not support multiple DHCP client instances running on a wireless client. There is no workaround for this, as only wireless clients registered with WLC (not bringing WGB into the picture) will have a MSCB entry and be able to get an IP address.

When a wireless client has a virtual machine running on it (e.g. in VMware, VirtualPC or Parallels), and when that virtual machine is running in bridged mode rather than in NAT ("shared networking") mode, then the WLC DHCP relay will drop the DHCP packets from the VM client, with a "dhcpProxy: Dropping packet (no mscb)" message.

It does not appear that the WLC's DHCP proxy functionality supports multiple DHCP clients behind the wireless client.

Workarounds:

1. Configure the virtual machine software for NAT ("shared networking") mode, not bridged mode.

2. If using 4.1 WLC software, configure the virtual machine to use static IP addressing, not DHCP.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode