🚀 go-pugleaf

Try setting the Frame detect switches at the client side (somewhere in
the IPX protocol settings) from "auto-detect" to "ethernet802_3". This
has helped me through a lot of similar problems on a company that used
a lot of notebooks on the network.

VanderBilt

On Mon, 30 Mar 1998 10:13:06 -0600, smeeuwsen@hotmail.com wrote:

>Situation:
>
>We are getting no Netware login under Windows 95 for our clients using Intel
>EtherEpress ISA 100B Cards. This occured when we changed Netware 4.10 to a
>new server running Intranetware 4.11 and now the login will come up sometimes
>but very rare.  Before this everyone was logging on fine, now only those
>using this specific card are having trouble logging on. Also, if we select
>'Quit all programs and logon as a different user' it works most of the time.
>The login never comes up when our main Novell Server goes past 50%
>utilization.  So it seems it is some glitch in the drivers maybe?  Seems
>kinda like a timeout error of some sort. We have already troubleshot by
>changing frame type, hardcoding speed and duplex.  Any help or suggestion is
>appreciated, especially from intel.  Our data is below.
>
>Scott Meeuwsen, MCP
>Entela, Inc.
>
>NOS: Intranetware 4.11 using 802.2 and 802.3 frame types
>Client: Windows 95, 486DX2-66, 16MB, Intel ISA 100B NIC, driver ver. 2.0.
>Hub: Intel EtherExpress 24 Port set at 100Mb
>
>-----== Posted via Deja News, The Leader in Internet Discussion ==-----
>http://www.dejanews.com/   Now offering spam-free web-based newsreading