From: J.J. O'Shea on
On Thu, 18 Feb 2010 06:34:10 -0500, Salmon Egg wrote
(in article <SalmonEgg-44AE94.03341018022010(a)news60.forteinc.com>):

> I performed an experiment.
>
> 1. I shut down my Mac Pro while I had a working DSL internet connection
> using one of the Ethernet ports on the computer.
>
> 2. I switched the Ethernet port on the computer into which the cable to
> the modem was plugged.

You need to check and see what IP address and DNS servers were assigned on
that port. You might also want to verify that DHCP is turned on on that port.
The way to check is to go to System Preferences/Network and look for the
Ethernet port that has the little green dot next to it. If _no_ Ethernet
ports have a little green dot, then there's a problem, the exact nature of
which will depend on the colour of the dot. Red dots mean that the connection
is disabled. Orange dots mean that the connection is enabled but that there's
nothing detectable on the other side. The act of plugging in a working
Ethernet cable should automatically turn on the port and it should be able to
detect the carrier signal. if you have red dots despite plugging in a live
cable, then you may have a hardware problem or a fairly serious software
problem. Did the second Ethernet port ship with the Mac?

If you have an orange dot, then you almost certainly have a software problem,
but it should be fixable.

If you have a green dot, and your IP is in the 169.254.x.y range, where x is
a number from 0 to 255 and y is a number from 1 to 254, then you have an
APIPA address and your system is not picking up DHCP. That's fixable.

If you have a green dot, and your IP is a 192.168.x.y, a 172.16.x.y through
172.31.x.y, or a 10.x.x.y address, then you have a valid Class C, B, or A
private network address and the odds are you have a DNS problem. I'd put in a
DNS server in the provided space; use your ISP's DNS, or if you can't find it
easily, use 8.8.8.8 and 8.8.4.4 (Google's free DNS) or 208.67.222.222 and
208.67.220.220 (OpenDNS's free DNS).

If you have a green dot and your IP is something other than above, then
there's a different problem. Get back to us on it, but odds are that you'll
have to do something about your modem or router, 'cause you're not on a
private net.

>
> 3. This morning I booted with the resulting connection. It did mot work.
>
> 4. I fiddled with the Network pane settings. I was not able to get a
> connection. I really do not have a good mental model of what these
> machinations do.
>
> 4. I switched the Ethernet cable back to the original port, the way it
> was before step 1 above. I did shut down the computer. I also used the
> same location to what it was before step 1.
>
> 5. Everything worked well.
>
> My key problem is that documentation is sketchy at best. Although a
> computer should be completely predictable, I find that I must
> reluctantly resort to experiment.
>
> Bill
>
>



--
email to oshea dot j dot j at gmail dot com.

From: Tom Stiller on
In article <SalmonEgg-44AE94.03341018022010(a)news60.forteinc.com>,
Salmon Egg <SalmonEgg(a)sbcglobal.net> wrote:

> My key problem is that documentation is sketchy at best. Although a
> computer should be completely predictable, I find that I must
> reluctantly resort to experiment.

The predictability of a computer's behavior and your understanding of
that behavior are independent variables. Experimentation is one way of
reconciling the observed differences.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF
From: Salmon Egg on
In article <tom_stiller-82608B.08174718022010(a)news.individual.net>,
Tom Stiller <tom_stiller(a)yahoo.com> wrote:

> In article <SalmonEgg-44AE94.03341018022010(a)news60.forteinc.com>,
> Salmon Egg <SalmonEgg(a)sbcglobal.net> wrote:
>
> > My key problem is that documentation is sketchy at best. Although a
> > computer should be completely predictable, I find that I must
> > reluctantly resort to experiment.
>
> The predictability of a computer's behavior and your understanding of
> that behavior are independent variables. Experimentation is one way of
> reconciling the observed differences.

I fully understand your point. With increasing complexity of computers
and the software that runs them, it is difficult to figure out just what
experiments to do. My point is, that with sufficient documentation, the
necessity to experiment can be greatly reduced. I see the problem as a
lack of availability and clarity of documentation. In addition, there is
a lack of my own capability.

Bill

--
An old man would be better off never having been born.
From: You on
In article
<66d04a7f-7190-4379-95bd-f9a645d1ddfc(a)v20g2000yqv.googlegroups.com>,
queries0 <queries0(a)gmail.com> wrote:

> Related question: I would like a Mac with two ethernet ports, one
> connected to my local network and one public. A Mac Mini would be more
> than sufficient but I understand it cannot be configured with two
> ethernet interfaces. Any solution other than buying a Mac Pro?
>
> Any advice appreciated

Not True.... You can ALWAYS add an Ethernet Port via a USB Dongle....
From: Salmon Egg on
In article <you-6499E0.20225919022010(a)news.starband.net>,
You <you(a)shadow.orgs> wrote:

> gured with two
> > ethernet interfaces. Any solution other than buying

I am guessing that Ethernet PCI cards are available to provide
additional ports just as PCI cards can be used to provide additional USB
ports. You just would need to get software that will handle the
additional ports.

Bill

--
An old man would be better off never having been born.