🚀 go-pugleaf

In article <5g93m8$ddo@eve.enteract.com> pschuman@interserv.com (Phil Schuman) writes:
>From: pschuman@interserv.com (Phil Schuman)
>Subject: Win95 + Novell Client 32 vs MS Client for Netware
>Date: 13 Mar 1997 14:41:12 GMT

>we are running a Novell 4.1 IPX network - 
>using Novell Client 32 for the Win95 workstations...

>If I setup my laptop with the same config for the Dialup Adapter - 
>        Win95 + Novell Client 32 + 32-bit IPX Protocol 
>I can get connected to the Shiva - but NOT see the Novell network...

>If I remove the Novell Client 32  - 
>ADD the MS Client for Netware - 
>ADD the MS IPX/SPX compatible protocol

>then it works !!! - 
>but I can't see the Novell NDS tree - 
>and therefore CAN'T login to any userID that is NOT in the root 
>nor perform any system NDS maint...

>We have this same problem with some other program products also....
>with workstations on the LAN..

>They will NOT work when using the Novell Client 32 - 
>but WILL work when using the MS Client for Netware 
>and the MS protocol stack.

>So - 
>is it a programming problem with the API that applications are using?
>OR - is the 32-bit client and protocol requesting some function that 
>is not being interpreted correctly - ???

>why would an application, or a device (Shiva) not work with Client 32,
>yet work fine with the MS Client for Netware - ?????

>Phil - 

I don't know why it didn't work for you.  I have a similar setup however my 
remote access server is a Cisco 2509 instead of Shiva.  When I call in (with 
client32 installed), I can see the NDS tree and login normally.  No difficulty 
at all.  After the login (PPP with CHAP), I can go into network neighborhood 
to browse and see my netware directory services and netware servers folders.
Network setup config is as:  Novell Client32, DialUP adapter, ipx 32-bit 
protocol, ipx/spx compat protocol and tcpip all bounded to dialup adapter

Daniel Tran - dtran@ucla.edu