On Client32 V3.21 for Win9X, the IPX/SPX protocol and the 32 bit protocol are bound to the Novell client. What ramifications might we experience if we UNBIND the IPX/SPX compatible protocol from the client 32? We are trying to alleviate some of the issues we are having by chipping away, little by little and this seems to be increasing overhead, but to what extent and to what it is talking to, I don't know. Thanks for the posts!

Unless you are running a pure ip environment (only supported by Netware 5.x), it won't work. Simply remove it from a workstation and try it. However from your reference to "network issues" you are having, your problem solution may lie elsewhere.

IPX is still working because the 32 bit IPX protocol is bound to the client32. We can get to the Novell 4.11 servers from the client with the IPX/SPX compatible protocol unbound (on Win9x: start, settings , control panel, netowrk, IPX/SPX compatible protocol, properties, bindings)to the Novell Client32 and the IPX 32bit protocol for the netware client (...control panel, network, IPX 32bit protocol for the Novell Netware Client, properties, bindings) bound to the client32. I agree, some of the issues we have stem from the NT side also. Mainly with browsing, WINS and the latency caused by name resolution/browsing in a large corporate environment. Every little bit helps and if we keep chipping away at the little issues, pretty soon, this stuff will work as advertised (but my expectations aren't set too terribly high!). What are the implications of unbinding the NWLINK (IPX/SPX-compatible protocol) from the Client32 and keeping the 32bit Novell protocol bound to Client32?