>Will I lose the ability to connect to other Win95 computer, if I will to
>remove the binding to Client for MS Network? Does this binding helps in the
>communication between computers? I am quite confuse about what is "Binding"
>and NetBIOS over IPX/SPX". Another question is, can these 2 settings be on
>"NetBIOS over IPX/SPX" and "NetBIOS over TCP/IP"? What are their differences?
>Please give some light to me, thank you very much.
>

If the Win95 peers are using NetBIOS over IPX/SPX to communicate peer-to-peer, and that's the only available NetBIOS/MS Networking protocol available to them, then yes. If they're using something else, like NetBEUI, or NetBIOS over TCP/IP, then they'd be able to connect using the alternative protocol, although you'd probably have to reboot all the stations to get things set back up.

NetBIOS uses another protocol to carry its message packets; rather than having it's own added packet type, it uses the transport services of another protocol like TCP/IP or IPX/SPX to carry the NetBIOS packets. Yes, both can be enabled at the same time; it should only be necessary if you have stations that can only support NetBIOS on one or the other protocol (ie some stations have only NBT, some have only NetBIOS over IPX; these stations can't talk to each other
since they don't have a common transport mechanism for NetBIOS. Stations having both options enabled could talk to both sets of stations.

I'd recommend that you pick up the MS courseware for Networking Essentials; it covers the topics of protocols and binding in detail.
>>>Thank you for your advise.
>>>I just wonder what is the protocol "IPX/SPX-compatible Protocol" at Win95 is
>>>doing? It seems that the "binding" to the "Client for MS Network" at this
>>>particular protocol is giving the slowness problem.
>>>Any idea what is this doing and will it cause problem to the network
>>>communication if I were to disable the binding to Client for MS Network?
>>>
>>
>>By default, Win95 will try to use NetBIOS over IPX/SPX to do peer-to-peer networking if it doesn't see a better alternative. You could try removing the binding; without knowing exactly what the protocol stacks are doing on your system to communicate with the server, it's hard to say that's the cause, and if it's only using that to connect to peer stations rather than the NT Server, you might lose the ability to connect to other WIn95 boxes.
>>
>>>Note: My customer need Novell to access their email system.
>>>
>>>
>>>>The only thing I can think of is that Win95 may be binding the Microsoft Client to your NT Server using NetBIOS over IPX/SPX rather than using NBT (NetBIOS over TCP/IP.) I'd try several things:
>>>
>>>>(1) Unless the server has a need to access the NetWare resources directly, don't install NWLink/GSNW on the NT Server. If there's no NWLink support on the NT box, the Win95 stations will continue to bind with NBT.
>>>
>>>>(2) Upgrade to Win98. The immediate benefit for you is the improved networking implementation for both NetWare and Microsoft servers, and explicit support for NBT through the Network Control Panel applet.
>>>>
>>>>(3) If you can't remove the NWLink stack on the NT Server, then at least set the TCP/IP stack and the WINS client at the top of the bindings for both Workstation and Server services.