Airport DHCP fails to get address (Mac on Windows Network)

Open up your Network section of System Preferences and match the settings for the ethernet port to the settings on the Internet pane of AirPort Admin Utility. Is there any discrepancy?

 

Ah, my bad. Okay, match the AirPort card settings with the ethernet settings. Notice any differences?

 

How is your network wired to the NetGear? Is your DHCP server plugged into the LAN ports or the WAN Port?

I suspect that if your network is plugged into the WAN port, that the Netgear, with DHCP turned off, may be blocking, at some level, communications to the WiFi.

Max.

 

I had this same problem, but it was because I was entering the wrong key on the wireless network. OS X won't tell you if it's wrong, it will just connect and not do anything. Contact your sys admin and see if the router is seeing your macbook, if it isn't, that's prolly your problem. tripple check with your sysadmin that you have the right key as well.

 

As mad jew mentioned, please be sure that when you go to System Preferences...->Network and choose Show->Airport in the second drop-down, that, in the TCP/IP tab, you have DCHP selected. In fact, for each of the relevant tabs "TCP/IP","PPPoE", etc., toggle between the Airport and Built-in Ethernet selections in the "Show" drop-down to, as mad jew suggested, make sure they're the same.

Edit: other suggestion: I'd click on the "Location:" drop-down and choose "New Location..." (after clicking the lock on the bottom left to unlock things), then create a location called "Work" or whatever, then set it up there. That way, you can also create a "Home" or whatever location to change the way things network when your laptop is there (and so on, for other places you want to connect wirelessly). Then you can toggle network selection with the "Location" menu item under the Apple menu (the one on the top left of the screen). I use a manual address at home (with no proxies) and DHCP at work (with proxies), and this shortcut comes in handy daily.

 

Are you using the ASCII WEP key or the whole hex number? I had a similar problem with my TiBook and a Linksys router. Even though my computer gave me the option of 128-bit ASCII, the router would not recognize the key, I had to type in the whole 128-bit hex key.

 

I haven't even ventured doing this on the Mac yet (never had problems with DHCP assignations) so I'm not sure if it's possible, but have you tried setting a valid IP address manually on the wireless network?

 

can log on but no ip address

is access control happening on the wireless router?
you might need to add the mac address of the airport card to the router.

rick

 

Not sure it's a windows problem or a hardware one...

I think you guys are assuming some kind of hardware problem when I disagree. I've had exactly this issue with my iMac G5 connecting to our Belkin router, only occasionally and usually when signal strength is poor. I've just gt a MacBook and am having massive problems with this on my University wireless network. I am pretty sure that the problem is OS X's DHCP timeout. Basically it requests an IP address and if the server/router is too slow to respond it gives up and assigns itself one. The issue is that it's giving up too fast. Windows DHCP isn't exactly snappy which would explain Mark's problem, and I know damn sure my Uni's servers are sluggish at times (to be fair they're handling hundreds of wireless roaming connections at any one time plus thousands of wired ones). My big problem is, I have no idea how to change this timeout value! It seems to be about 5s and I think it needs at least doubling. The value must be in a config file somewhere but not sure where, and I can't track down a GUI control for it. Ideas anyone?
Cheers
Rowan

 

Insist on speaking to someone more senior at Apple if you call them, the problem could well be an OS X/Windows incompatibility, you don't normally use a windows server to give out DHCP.

For the WEP key have you tried getting the Hex version? That might help. (someone else should be able to tell you how to find what this is)

The other thing you could try is switching the wireless network security to WPA instead of WEP as that is a lot more secure (and trouble free) it should work fine with OS X or XP SP2.

 

ok so i am going to try to figure out your settings.

1. you have cable internet
2. plugged into a windows server. (which is set to dhcp) out into...
3. a wireless router.
4. the wireless is just bridging the dhcp numbers to the wireless?

now this is what i suggest. change your wireless router settings to give out dhcp numbers. so the wireless becomes another dhcp server. (not just a bridge)

i have my cable going to a wired router. that give out dhcp. and my wireless is conected to that. and gives out a different range of dhcp numbers for wireless.

 

Is the Windows server dishing out the ip addresses? Do you need to put in its' address in the proxy server settings, maybe????
System prefs> Network> Airport> Proxies> then choose Web Proxy HTTP and type in the IP address and port number (eg 10.22.8.53 and 8080).

 

Just saying this because I haven't seen it mentioned by many of the responders. He's not using the router as a router. What he's attempting to do is use the wireless portion of his router like one of these, eleminating the physical wire. The router may simply not be capable of functioning like this. It's a software issue and it may not be designed to provide that function.

Getting mad at Apple is pointless. The OP is attempting to set up a non-standard network, using a router in a role it wasn't designed to perform. Please stop wasting Apple's time. Not only did they not sell him this setup or promise him that it would work, nobody would sell him a router and guarantee it could be used like this. It's not Apple's fault he's having trouble with this and it's not their responsibility to fix the problem.

Now, for the issue at hand...

The easiest solution would be to obtain the right tool for the job. Remove the "router" from the setup. If you're going to use a router like a switch, don't. Just get a switch. They're $10. Get a wireless "gaming" adapter, configure it, plug it into a switch attached to the network. Yes, they're generally used to attach a wired device to a wireless network and this is going the other way around but it really doesn't matter which end of the link it's on.

If you don't want to buy new equipment (those adapters are kinda spendy for what you get), you'll have to hope your router can be configured to do what you want. Some can, some can't. If your router's wireless side can be set to "client" instead of "AP", give that a shot. That might let it bridge the wired and wireless connections inside the router. BTW, WPA won't work with this kind of setup. You'll be limited to WEP.

This is, of course, assuming you absolutely must use the windows server as the DHCP server and router.

 

Here's your problem (as said above the router turns what you think of as your network (singular) into two networks (plural) and your DHCP client and server are on different networks).

 

That is exactly what I think too. You need to be connecting using a wireless Access Point, not a Router, connected to your main network. Then you will probably have success. I am running this at work without a hitch.

 

Almost all wireless routers have settings designed to do exactly what he is doing, and it works for the PC. So what I think he should try is enter those manual IP addresses and then try to ping the wireless routers address. This way you having nothing to do with that extra DHCP server. Also make sure the routers IP your pinging is in the same block as your manuel IP. (ie 192.168.1.X) If this ping does to go through then you know your not connected to the wireless part of the network. If that is the case make sure there is no MAC filtering turned on, on the router. If it is add your macs MAC address to the list and things should be good.

Post a response of what happens with what I mentioned here, and then we can continue troubleshooting. And the router should work just fine. By the way what is the model number of this router?

 

This should not be the problem if the router has been configured correctly from what I can tell with his network NAT, and DHCP has been disabled on the wireless router. Which turns it into a switch. And besides that is beside the point as its all plugged into the LAN ports not the WAN. If it was plugged into the WAN port then it routes traffic and blocks traffic.

 

Is there any chance there is any other type of security you don't know of? RADUIS? anything like that? Captive portal?

 

Hmmm things that come to mind.

Are you running the latest firmware form netgear, never hurts.
Is the netgear in some special rangemax or enhanced network speed mode. This could screw with things as most of those enhanced speed modes are not common protocols.
I am not too familiar with server 2k3, but I am sure it has a DHCP log, you should be able to view it and see the request from the mac to the server for an address and then you should also be able to see the server offering an IP to the machine. Any kind of errors in that log might give you some clue as to what is happening.
Also I would think the DHCP server has an option for creating an IP reservation table based on MAC address. Try putting an entry in for your mac, maybe you will get lucky.
When you enter an IP in manually, including DNS, Gateway etc, what happens? Can you ping other computers on the network, can you ping external IPs? Are you sure you are not running a proxy?