Can't connect to a DHCP-LAN network

Question

Level 1

6 points

Can't connect to a DHCP-LAN network

Got my MacBook Pro (10.6.4) w/ me to work the other day, plugged work's ethernet in, but got a "Self-Assigned IP"-error, asked the IT dep. and they assured me its a DHCP network, no manual IP settings is required. So I have launched VMware - Windows XP Pro (latest SP) the LAN was instantly connected and working like a charm, whats wrong and how to fix it in OS X?

MBP15" Penryn 2.5GHz, 4GB RAM, 320GB 7200rpm; iMac17" C2D 2.0GHz, 2GB RAM, 10.4., Mac OS X (10.6.4), 1Gbps ethernet/n-draft ABES w/ APX; iPod Video 30GB White; iPhone 3GS 32GB Black

Posted on Jul 8, 2010 3:01 AM

Reply

Answer 1

Jul 8, 2010 5:26 AM in response to CEnTR4L

Just to confirm things: go to System Preferences>Network. Select the current network if you have more than one, Click on the TCP/IP tab, and check that the 'Configure IPv4' drop-down menu is set to 'DHCP'. It should be the default, but it's the first thing to check.

If it is, click 'Renew DHCP Lease'. See what is shown as 'IPv4 Address' - it should probably begin 192.168...

This thread suggests a solution if you are using a proxy server, as may be the case:

Click on the 'Proxies' tab and uncheck 'Use Passive FTP Mode' (though I can't quite see what this has to do with the case).

Reply

Answer 2

MartinR

Level 7

24,456 points

Jul 8, 2010 5:31 AM in response to CEnTR4L

Check +System Preferences > Network > Ethernet > Advanced > TCP/IP+ and make sure the setting for +Configure IPv4+ = "Using DHCP". Likewise make sure all other settings are also correct. Then click "Renew DHCP Lease". If you change any settings, be sure to click OK, then click Apply.

One other thing, you might check +System Preferences > Network+ and make sure "Ethernet" is at the top of the list on the left side of the window. If not, click the little +gear icon+ at the lower left, then select +Set Service Order+ and drag Ethernet to the top of the list.

Reply

Answer 3

CEnTR4L Author

Level 1

6 points

Jul 8, 2010 5:52 AM in response to CEnTR4L

Roger Wilmut1, I have already done that when I was in work's network environment, doesn't do anything, its all DHCP by default.

Also, in 'Proxies' tab, there's only FTP Proxy but no 'Use Passive FTP Mode'.

MarinR, its all DHCP by default.

Thanks for stepping by, much appreciated.

What I have stated in my main post was about my work network, home network (LAN mainly and rarely WiFi, both DHCP) works without a hitch.

Reply

Answer 4

direwolf8

Level 4

1,286 points

Jul 8, 2010 1:09 PM in response to CEnTR4L

It sounds like the router you use at work doesn't handle DHCP strictly to specification. One of the symptoms is that operating systems whose network stacks are poorly implemented may work, while operating systems that expect to see packets that obey the specification won't.

Is there a firmware upgrade for the router that may fix the problem?

Reply

Answer 5

Jul 9, 2010 2:18 AM in response to direwolf8

Hi,

this is very curious because what should be wrong with your Mac OS network settings, when you have connection in your VM? How is your VM configured to use the network? NAT, pass-through or any other possibility? Can you access the network with your Mac OS when the VM is offline?

Bye Tom

Reply

Answer 6

peppitos

Level 1

5 points

Jul 10, 2010 1:26 AM in response to CEnTR4L

Same problem here. My older MB (running snow leopard) works just fine through ethernet but my latest MB (running 10.5.8) can't connect to the same lan and I get the "self assigned ip" message. If however I try to connect it to my modem router directly (instead of connecting to my switch first) then it connects just fine as well!

Reply

Answer 7

Jul 8, 2010 5:01 AM in response to CEnTR4L

Did I understood it correctly -> Your Windows VM is hosted on your MacBook and there are no problems connecting the LAN but your Mac OS can't connect?

Bye Tom

Reply

Answer 8

CEnTR4L Author

Level 1

6 points

Jul 8, 2010 5:05 AM in response to prontosystems

Thats true, VMware is in my Mac, Mac can't connect to the LAN, but VMware Windows XP Pro does, perfectly.

Reply