Can't get my mac to successfully use a internal static IP
 

Hi, I have my mac setup as a webserver, it connects to the internet through a Aiport Extreme Basestation, would it work if I set it to statically keepm the internal IP of 10.0.1.2 and the family PC on the network to 10.0.1.3? I'm asking mainly because from time to time other people (guests we have over) will connect to the network, will the basestation attempt to assign the two IPs to their computers and thus cause network conflicts or do you think it'll all work out and it'll be smart enough to not assign the two IPs again?

thanks for any advice in advance!

Yes, that will work. Though you might have to tell the AEBS that they will be static. That, I don't know, I don't use ABSs.

I'm asking mainly because from time to time other people (guests we have over) will connect to the network, will the basestation attempt to assign the two IPs to their computers and thus cause network conflicts or do you think it'll all work out and it'll be smart enough to not assign the two IPs again?

You need to set your fixed IP machines to 10.0.1.201 and above. The Base Station DHCP server assigns 10.0.1.2 -10.0.1.200 and the range cannot be changed without losing NAT functionality.

ahh so if I assign the computers that need a static internal IP one of 10.0.1.201 and up no conflicts will occur when guests connect to the network?

Exactly.

.

ok tight thanks for your help

I tried assigning the IP both via DHCP with manual address and manual and both times it seems the base station would reject the static IP of 10.0.1.201...why? (I could not connect to the internet after applying the settings with the manual IP) :confused:

When you select "Using DHCP with manual address", enter and IP of 10.0.1.201 and click apply, what happens?

It applies but the subnet mask turns to nothing as well as the router address, then in network status it says something along the lines of "Your mac cable is connected to the network but your mac doesn't have a IP and couldn't connect to the internet" and I can't connect to the internet at that time - what do I need to do to get it to accept the static IP(s)?

please help......:(

First, confirm that you can still get a proper connection using DHCP. You don't need to make changes to the base station for this to work. Once you get a working connection with DHCP, then all you need to do is change to DHCP with manual IP and put in an IP ending 201+.

I'm using dhcp right now successfuly, I'll try again...

ok still no luck :(, here's what happens when I try as suggested: http://img1.uploadimages.net/397722screen1.jpg...what should I do?

thanks in advance!

I've noticed that in the airport admin that the option to share the IP 10.0.1.1 has been selected, am I supposed to select the Share A Range Of IP Adresses (Using DHCP) option instead in order for this to work? If so, should the range be 10.0.1.2-10.0.1.200?

thanks!

EDIT: I just figured out that I can't use the range option since I don't have a static IP from my ISP :(...how do I get my basestation to let me use a internal static IP?? please help me...:(

No. You want the DHCP with NAT option.

If you have DNS servers configured in your BS then you can use Manual IP and set 10.0.1.1 for both router and DNS server.

I don't have any static IPs from my ISP so I don't think I can assign my airport base station a static one...is there any clear way I can get my mac to use a static internal IP (one only visible inside the network)?

In your network preferences, select manual. Set your IP to 10.0.1.201. Set your router to 10.0.1.1. Set your DNS to 10.0.1.1 (assuming your DNS server has been entered into your base station).

yay I got it to work, thanks kfaulhaber!

Just looks like the AEBS does not automatically send to the computer outside of the range of automatic addressing the subnet and gateway info... Does any one know why that is ? Cause it looks a bit strange... Askingas I don't have an AEBS but do work with wireless alot :D

The whole thing sounds a little strange. One of the points of using a DHCP server is that the server doles out IP addresses such that there are no conflicts. I'm not totally sure about the Airport base station, but I believe that most DHCP servers are designed to try to give every computer the same IP every time. It should only drop the association when it runs out of IP addresses. Either way, as long as the servers are running, their IPs should never change.

Further experimentation found that, regardless of what IP I put in, it would not retrieve anything from the AEBS. Apparently DHCP w/manual IP just does not work with the AEBS.