NetworkManager issue - No dhcp...

Hi,
I’m having a problem for some time w/OpenSuse 11.1 and NetWork manager; it just doesen’t work (4 different PCs-Notebooks w/different NICs, Wireless and Cable, native drivers and ndiswrapper, KDE3 and KDE 4)

Below is the output I almost always get; sometimes it seems to work and gives me an IP addres, but I still can’t connect; I can’t figure out what is wrong, and don’t know how to ‘debug’ this. Has anyone had this kind of issue ?

Jun 7 13:13:45 linux-fwy6 dhclient: Internet Systems Consortium DHCP Client V3.1.1
Jun 7 13:13:45 linux-fwy6 dhclient: Copyright 2004-2008 Internet Systems Consortium.
Jun 7 13:13:45 linux-fwy6 dhclient: All rights reserved.
Jun 7 13:13:45 linux-fwy6 dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jun 7 13:13:45 linux-fwy6 dhclient:
Jun 7 13:13:45 linux-fwy6 kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jun 7 13:13:45 linux-fwy6 kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jun 7 13:13:45 linux-fwy6 dhclient: Listening on LPF/wlan0/00:c0:49:59:89:ca
Jun 7 13:13:45 linux-fwy6 dhclient: Sending on LPF/wlan0/00:c0:49:59:89:ca
Jun 7 13:13:45 linux-fwy6 dhclient: Sending on Socket/fallback
Jun 7 13:13:48 linux-fwy6 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jun 7 13:13:48 linux-fwy6 dhclient: send_packet: Message too long
Jun 7 13:13:51 linux-fwy6 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jun 7 13:13:51 linux-fwy6 dhclient: send_packet: Message too long
Jun 7 13:13:58 linux-fwy6 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jun 7 13:13:58 linux-fwy6 dhclient: send_packet: Message too long
Jun 7 13:14:08 linux-fwy6 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jun 7 13:14:08 linux-fwy6 dhclient: send_packet: Message too long
Jun 7 13:14:23 linux-fwy6 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
Jun 7 13:14:23 linux-fwy6 dhclient: send_packet: Message too long

Hi,

First I would try setting a static address on the machine and attempt to communicate with your dhcp server via a simple ping.

If this is succesful then we would have to look deeper into the problem

post back