one of the two interfaces doesnt get IP from dhcp

P

pbergamo

Registered
this is one of the weirdest errors I have ever seen

en1: works fine

en0: DHCP doesn't get IP address (autoassigns the 169.254.x.x address)

dhcp server works fine for all the other comptuers of the network

even crazier, if i install a virtual machine the guest OS can actually get the IP address from the dhcp server

there is no mac filtering or anything like that

any idea?
 
The million dollar question is this: Does your computer work?

Seems like a very stupid question but my computer also has en0 inactive, but I don't have any issues. So if your computer works on the internet then theres nothing to worry about.
 
supanatral said:
The million dollar question is this: Does your computer work?

Seems like a very stupid question but my computer also has en0 inactive, but I don't have any issues. So if your computer works on the internet then theres nothing to worry about.
Click to expand...

Go to network pane and check if the network card is enabled. If enabled, force a renew of the ip-information (renew ip).

It looks like a misconfiguration if you get an ip-number in a different os on the same system.

Check network status -> configure networkports -> enable build-in networkcard.


Good luck, Kees
 
If your computer can't recieve an IP, then it defaults to a 169 address.

OSX shows a lot of information in network information that is in general useless to the everyday user. Like why we need to see more then one ethernet configuration for each ethernet adapter is beyond me.

I got it, pebergamo said that he runs a guest OS on his computer. The ethernet adapter that gets a 169 address would get that address because the Operating system has not started up yet. OSX has it enabled but is not requesting an IP since its leaving that upto windows or what ever guest operating system he/she's using.
 
Does the computer has 1 or 2 network cards installed.

You can check with ifconfig if .en0 and .en1 are both display with some information. If 1 is not displayed, it most likely is disabled.

Please provide some more information.


Good luck, kees
 
..also, if internet-sharing is ON on one of the ports, you're actually running a DHCP-server locally, and the port in question will look like it's inactive. (but actually have an IP like 192.168.2.1)

-----8<------ edit ----------

btw, do you hookup both ethernet ports to the same network (and same DHCP server)?
because thinking of it, i can imagine ip-adresses are given-out by the DHCP server on a 'per host' basis.
if that is the case, i can also imagine that a host will generally get just one IP-adress from the same pool, leaving the second interface without one.

but this is speculative...
 
You must log in or register to reply here.
Back
Top