Hrm. I suspect that there's something about our 10/100 switches that causes
the card to either autodetect incorrectly the first time, or try one setting,
and if there's an error then close the connection and try another. This
might confuse the Newton driver if it expects the card to be linked to the
network by a certain point and the card is trying to drop and re-enable the
link. Unfortunately, looking at 3Com's diagnostic and setting software
for this card, there doesn't seem to be a way to "hard-code" the card in
either full or half duplex mode.
Also, sometimes I have to reset the Newton, try to connect with Newt's Cape,
wait for the failure, and then use the Reset HTTP function and connect
again.
-- Victor
Original Message:
-----------------
From: Rolf Brakvatne rbrak29_at_qwest.net
Date: Wed, 31 Jul 2002 10:17:19 -0500
Subject: Re: [NTLK] Farallon problem with switches
Victor,
Yes, it is a Netgear FS 605 10/100 switch.
RB
On Wednesday, July 31, 2002, at 09:56 AM, victor_at_newtontalk.net wrote:
>
> You know what... I just started having this problem with my 3c589D as
> well.
> Tres bizzare. I got rid of my hub and moved to an 8-port 10/100 switch.
> Is your switch 10/100 as well? Maybe this is part of the problem.
> I've seen
> some strange things happen with switches and autosensing Ethernet
> equipment
> before.
-------------------------------------------------------------------
This message has been posted from Mail2Web http://www.mail2web.com/
Web Hosting for $9.95 per month! Visit: http://www.yourhosting.com/
-------------------------------------------------------------------
-- Read the List FAQ/Etiquette: http://www.newtontalk.net/faq.html Read the Newton FAQ: http://www.chuma.org/newton/faq/ This is the NewtonTalk mailing list - http://www.newtontalk.net/
This archive was generated by hypermail 2.1.2 : Thu Aug 01 2002 - 06:03:28 EDT