Re: Switching between Airport and wired Ethernet

jack ak <akjack@xxxxxxxxxx> wrote:

Bob Harris wrote:
In article <hpZuj.58203$Pv2.45279@xxxxxxxxxxxxxxxxxxxxxxxxxx>,
jack ak <akjack@xxxxxxxxxx> wrote:

Clark Martin wrote:
In article <ynsuj.1164$pl4.498@xxxxxxxxxxxxxxxxxxxxxxxxxx>,
jack ak <akjack@xxxxxxxxxx> wrote:


I eventually determined the message box was a complaint about the
non-working Ethernet en0 port. I removed the Ethernet connection
from Automatic and the other "location". There are about a dozen
com.apple.xxx files in the "...user - Library - Preferences - ByHost
folder.

These files have the 6 hex digit Ethernet port address embedded in
the filename. I've deleted the folder several times but it returns
and the applications act as though they have never been initialized.

I don't understand why my computer "thinks" there *should be*
a functioning Ethernet port when it is not configured.
Maybe in "Mac OS X Update" (10.5.12) this will be fixed.

ByHost uses your built in Ethernet Port MAC Address (the 6 hex digit
number) to uniquely identify your computer. The Airport MAC address
will never be used (with the likely exception of the MacBook Air). It
really has nothing to do with Ethernet, it's just using the Ethernet
port Mac Address as a machine serial number.

ByHost is used in the event you move your HD to another computer. It
would then create distinct preference files for that computer based on
it's Ethernet MAC Address.

Ok, how do I stop the "Connection failed - Server may not exist.."
message box from appearing? It keeps some functions disabled until
it is dismissed. Zoom won't work while this message box is displayed.

That sounds like something trying to connect to a server that is
not accessable, not an attempt to use ethernet.

The "Server may not exist" message refers to an Ethernet server.
When I connect an Ethernet cable to my 2Wire 2701HG-B Gateway router
2 rooms away, the message doesn't appear.

In that case you have some software on your Mac which is trying to
connect to a particular server, which is only accessible via Ethernet,
and the software is complaining in a silly manner if it can't connect to
the server.

The fact that the server happens to be accessible via Ethernet is
irrelevant. You won't be able to fix the problem by fiddling with your
Ethernet settings or network preferences, or disabling the Ethernet
port. (That is MORE likely to make the error message appear, since it
may prevent your Mac from being able to access the server even if the
Ethernet cable was connected.)

You need to identify what it is on your Mac that is trying to connect to
that server and tell it to stop doing that, otherwise it will keep
complaining if it can't talk to the server.

Exactly what functions is that server providing to your Mac? For
example, is it a file server (in which case, what protocols), a web
server, DNS server, DHCP server, or something else? For what purposes
have you told your Mac to connect to that server?

In an earlier message, you said:
At each machine boot, there is an message box which says

"Connection failed - Server may not exist..."

At which point during "machine boot" does this message appear? What
applications are running at the point this message appears?

Without more detailed information I'm only guessing, but the most likely
explanation is that you have managed to set up an automatic connection
to a file server when you log in to your account on the Mac. If so, you
would get the same error appearing each time you log in (e.g. if you log
out, then log in again) without the Ethernet cable connected.

Have a look in your Login Items, in your account under System
Preferences, Accounts. What items are listed there?

A related possibility is that one application you are running as a login
item has been configured to connect to a server in some way, and it is
that application which is complaining.

Similarly, it could be an application you are launching by hand each
time you start up the computer.

--
David Empson
dempson@xxxxxxxxxxxxx
.

Relevant Pages