NT Service and Protocol stacks (Networking Products)
At 09 JAN 1998 01:03:38AM Sam McDonald (Tristalee) wrote:
My question is in regard to protocol stacks and the NT service.
A number of our clients are adding Nt servers into existing network topologies, and are binding Multiple protocols to support other applications, email, internet, mainframe connections etc.
This is fine except that the performance of the NT service is reduced (in some cases the reduction is significant) as each protocol is added.
I know that "Less is best" but unfortunately many of the clients either unwilling or unable to reduce the number of protocol stacks used.
Are there any plans for "future versions" of the NT service to provide the ability to specify which protocol stacks to use.
Also, in the situation where a client workstation (eg: Win95 running OI3.4) has multiple protocols stacks ( Netbeui, TcpIp and IPX/SPX )bound , which stack does the NPP use to communicate with the NT service.
Cheers
Sam (Tristalee -OZ.)
At 09 JAN 1998 09:20AM John Duquette wrote:
Sam,
The NT service uses Named Pipes to communicate, so TCP/IP or NetBeui would be your best choice. Under Win95 it is useful to bind IPX to the Novell client (CLient32 does this automatically) and leave either tcpip or netbeui bound to the ms client.
John Revelation
At 02 FEB 1998 10:40PM Sam Mc Donald wrote:
Thanks for the feedback john.