cannot share airport connection to ethernet

Well, for one, your network settings are invalid.

If you manually set an IP address 169.254.208.193 then there's no way, ever, your router address could be 192.168.2.1.

Can't happen. Your router HAS to be on the same subnet as the machine, and in this case they're not. In fact I'm shocked you even get 4 green dots when you check the network settings.

In this case, if you really want to use a 169.254.x.x. address on the second laptop you should set the router address to the 169.254.x.x. address of the gateway machine (i.e. 169.254.208.193).

However, I still do not recommend this. You would be FAR better off setting a manual address on the 'BlackBook' rather than relying on self-assigned addresses.

So if your BlackBook's WiFi network is using 192.168.2.x/255.255.255.0 then turn off Internet Sharing and manually set the ethernet network to a different subnet (e.g. 10.1.1.1/255.255.255.0).

Re-enable Internet Sharing and connect the PowerBook's ethernet port.

The PowerBook could use either DHCP or manual addressing - if you use manual addressing, give it an address in the BlackBook's ethernet subnet (e.g. 10.1.1.2) and set the router address to the BlackBook's ethernet address (e.g. 10.1.1.1).

Now the PowerBook knows to send all its traffic to 10.1.1.1 - the wired port on the BlackBook - which will then relay it to the public internet.

Internet Sharing from WiFi (in) to Ethernet (out) will have your MacBook acting as a 192.168.2.1 router.

If the Powerbook is getting 169.254.x.x addresses, then the Powerbook did not see or play nice with the DHCP server on the MacBook internet sharing. 169.254.x.x addresses are called "Self Assigned" addresses.

The basic question is why did the Powerbook NOT play nice with the MacBook's Internet Sharing DHCP server?

The process 'bootpd' should be handling the DHCP services on your MacBook. Activity Monitor will tell you if it is even running. Another process 'named' should be providing DNS services on the MacBook for the PowerBook (translate domain names to IP addresses). Again Activity Monitor on your MacBook will tell you if they are running while Internet Sharing is running. Google Searches can get you more information on these processes; "Mac OS X bootpd" or "Mac OS X named" if you are interested.

If AND ONLY IF you want to try manual IP setup, Camilot's suggestion to use

192.168.2.x (for example 192.168.2.100

255.255.255.0 mask

192.168.2.1 router

8.8.8.8 and 8.8.4.4 (Google's DNS servers; why worry about the router providing DNS when Google will do it for you)

If that does not work, then I would suspect something is wrong with the MacBook's Internet Sharing setup.

But still no connection?

Everything you posted looks correct. You Powerbook has the correct IP address on its ethernet port.

Can your Powerbook access your MacBook's file system via file sharing? I'm thinking maybe you can based on this statement, but it is also possible I am reading into your statement that you did not mean:

Now I go over to the PowerBook [10.4.11] which I can interact with, I see the Desktop on my MacBook.

On your Powerbook you should look at your System Preferences -> Network -> Ethernet -> Advanced -> DNS tab and see if you have DNS servers provided.

A lot of times systems that have valid IP addresses that cannot access the internet are having problems with the DNS servers. Either they do not have a DNS server, or the DNS server is not translating www.company.com domain names into IP addresses.

You can try several things.

You could use the System Preferences -> Network -> Ethernet -> Advanced -> DNS tab [+] to add your own DNS servers, such as the OpenDNS or Google DNS servers:

OpenDNS.org

208.67.222.222

208.67.220.220

Google DNS

8.8.8.8

8.8.4.4

You could also experiment by trying to access a web page using the server's IP address instead of its name as an experiment to see if it is a DNS issue. For example there are the IP addresses of several well known companies:

https://69.192.29.15 www.apple.com

https://74.125.226.147 www.google.com

https://72.21.214.128 www.amazon.com

https://208.80.152.2 www.wikipedia.com

I cannot think of any other reason why you should be able to talk to your MacBook, but not reach the internet.

You can creater a new location by pulling down the Location menu in the Network pane. and chosing Edit Locations and adding a new one. That will make sure everything is cleared for a fresh config.

You need to add a DNS server to your setting on the Powerbook or else you won't be able to access anything that uses names, and not IP numbers. You can try adding Google's 8.8.8.8 as a DNS server in the TCP/IP pane of the Powerbook.

If this doesn't work, to see where the problem lies, do a traceroute on the powerbook: Open the Terminal (or) Network Utility and type:

traceroute <ipaddress>

where <ipaddress> is replaced by the site you are trying to reach.

if you don't know what ip address to use in place of <ipaddress>

open the Terminal or the Network Utility in the Macbook and type ping google.com

(if you use the terminal press control-c to cancel the ping or it will keep going.)

It should show you the IP address of google.com. In my case, and probably yours:

64 bytes from 74.125.224.51: icmp_seq=0 ttl=53 time=53.308 ms

the 74.125.224.51 is google's IP address.

While you're at it see if you can ping the Powerbook from the Macbook, by typing the IP address you gave to the Powerbook.

Then (on the powerbook) you can type:

traceroute 74.125.224.51

and you should see something like this:

traceroute to 74.125.224.51 (74.125.224.51), 64 hops max, 52 byte packets

1 home (192.168.1.254) 3.823 ms 4.137 ms 4.110 ms

2 bras30-l0.pltnca.sbcglobal.net (151.164.184.110) 45.367 ms 47.513 ms 46.900 ms

3 64.164.107.1 (64.164.107.1) 44.981 ms 45.607 ms 45.587 ms

4 151.164.93.229 (151.164.93.229) 220.613 ms 204.985 ms 197.448 ms

5 ppp-151-164-52-161.rcsntx.swbell.net (151.164.52.161) 47.060 ms 45.944 ms 47.656 ms

6 gar7.sffca.ip.att.net (12.122.79.97) 48.849 ms 46.207 ms 49.329 ms

7 cr83.sffca.ip.att.net (12.122.110.118) 53.108 ms 50.556 ms 51.029 ms

8 cr1.sffca.ip.att.net (12.123.15.109) 51.217 ms 49.968 ms 51.303 ms

9 cr81.sj2ca.ip.att.net (12.122.1.118) 49.355 ms 51.339 ms 63.659 ms

10 gar4.sn1ca.ip.att.net (12.122.110.61) 49.306 ms 48.254 ms 49.170 ms

11 12.248.108.10 (12.248.108.10) 49.192 ms 50.075 ms 49.127 ms

12 216.239.49.168 (216.239.49.168) 49.259 ms 49.982 ms 49.280 ms

13 64.233.174.15 (64.233.174.15) 49.239 ms 51.339 ms 48.548 ms

14 74.125.224.51 (74.125.224.51) 50.613 ms 49.568 ms 50.611 ms

If any thing comes back * * *, then that means that's where you connection problem is.

Stupid Apple. the previous was wrong. I typed up the solution and took too long to edit it and my carefully typed correct response was deleted.

So. Here's the no explanation solution:

on the MacBook's Ethernet:

IP Address: 192.168.1.1

Netmask: 255.255.255.0

Gateway: 192.168.1.1

on the Powerbook's Ethernet:

IP Address: 192.168.1.2

Netmask: 255.255.255.0

Router: 192.168.1.1

ping the Macbook from the Powerbook (ping 192.168.1.1)

if that works enter 8.8.8.8 for the DNS server on the Powerbook's Ethernet DNS Servers.

ping apple.com or google.com

Let me know if it doesn't work. And include full screen shots of your Ethernet Panes of both machince.

Netmasks are used to block out the network address. and the Machnie Address is what left over.

Class A netmask: 255.0.0.0 common non-routed (private) network addresses: 10.x.x.x

Class B netmask: 255.255.0.0 self-assigned (private) IP network (no DHCP server found): 169.254.x.x

Class C netmask: 255.255.255.0 private network address for small netowrks: 192.168.1.x

The 'x' is the machine's address in the network. So, in a Class B network (netmask 255.255.0.0) with an IP address of 133.127.31.77 the Network address is 133.127.0.0 and the machine address is the remaining 31.77

All of the networks listed as private are non-routable. Meaning their packets using those IP netowrks will not be passed on by a gateway without translating them to a public IP address. You Macbook is acting as a gateway, and DHCP only works withing the same network. SO, the ethernet cannot reach your WiFi routers DHCP server, thus why it is assigning itself a 169.254.x.x address.

By the way. You're machines can see each other because they are communicating via Appletalk which is a completely different Protocol, that will not work to connect to the internet.

Well, if you do not mind throwing money at the problem.

Ethernet Bridge

"The versatile Wireless-G Ethernet Bridge can make any wired Ethernet-equipped device a part of your wireless network." from linksys

example:

http://www.amazon.com/Linksys-RE1000-Wireless-N-Range-Extender/dp/B005FDXMJS/ref =sr_1_1?ie=UTF8&qid=1314563758&sr=8-1

Setup:

http://www.linksys.com/servlet/Satellite?c=L_Product_C2&amp;childpagename=US%2FL ayout&amp;pagename=Linksys%2FCommon%2FVisitorWrapper&amp;cid=1134692497433

Short answer - Do not use 'self-assigned IP addresses'

If I'm reading your screenshots correctly, your gateway machine has a 192.168.2.x IP address and your ethernet connection has a self-assigned.

You're also trying to share the wireless network with ethernet clients.

The problem is that since the ethernet port is not (properly) configured it's not passing the correct data out to the ethernet clients. Most specifically, in your seventh screenshot the client has no DNS server configured, therefore it's not going to be able to resolve hostnames, therefore no internet.

You can avoid this by either using static/'Manual' addressing on all machines on your ethernet network, or by configuring the gateway machine to have some private address (e.g. 10.2.2.x/255.255.255.0) with a DNS server assigned. This should then get pushed out to the DHCP clients with a better chance of success.

Well, I hope your Kernal panics are solved by now. But they can see each other through Bonjour, I bet.

If I wanted to share my Airport via Ethernet, I'd do the following:

Don't worry that my Ethrnet is red, that's because I don't have a cable to plug into anything right now.

Now on the Powerbook, do the following:

Keep the sharing as you have it set on the Blackbook.

since you're connecting without a switch between the two there's no DHCP server to assign an address. Also, in your Blackbook's Ethernet settings, you made the mistake of setting an IP address for Ethenet, then setting a router address that's no on the same subnet. So, if you notice on the Blackbook I set above, point the router address to itself. Essentially if you point a deivde at itself you're basically saying (look for another interface to route out ot the internet.) Then on the Powerbook, use any address on the same subnet (10.0.0.2 in this case) and point the router to the other machine's ethernat address.

This should work. Let me know.