Quote:
Originally Posted by fraserspeirs
Simply put, nothing can route out of the Airport's internal network to the internet.
|
Could it be a default gateway issue on the AE? What is it set to on the Macs and is it the same on the AE? I'm just wondering if the Macs are somehow working it out for themselves but the AE maybe isn't? It sounds like the AE doesn't know where to send packets that aren't on its own subnet which points to DG. The other static Mac IPs will be on the same subnet which means DG is not required when communicating with them since a broadcast will be sent out to obtain their MAC addresses directly, which explains how you can get from the LAN side of then AE to the static Macs but not out on to the internet.
One other possibility, you haven't got the DG in the DHCP settings on the AE set to something other than the AE have you (previous config maybe)? Check your AE clients have their DG set to the AE IP address. [EDIT] Forget that last possibility, you wouldn't be able to communicate with the static Macs from AE LAN clients if the AE DHCP DG setting wasn't the LAN IP of the AE. [/EDIT]
Either way, this smacks of a default gateway problem specifically with the AE especially if you've already eliminated a problem with the specific IP address by following Carmock's suggestion.
[EDIT2] Also check your WAN DNS settings are manually configured in the AE. Obvious I know, but don't overlook anything!