Client Service for NetWare Object
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
The Client Service for NetWare performance object consists of counters that measure packet transmission rates, logon attempts, and connections.
Counter Name | Description | Counter Type |
---|---|---|
Bytes Received/sec |
Shows the rate at which bytes are coming in to the redirector from the network. This counter includes all application data in addition to network protocol information (such as packet headers). |
|
Bytes Total/sec |
Shows the rate at which the redirector is processing data bytes. This counter includes all application and file data in addition to network protocol information (such as packet headers). |
|
Bytes Transmitted/sec |
Shows the rate at which bytes are leaving the redirector to the network. This counter includes all application data in addition to network protocol information (such as packet headers). |
|
Connect NetWare 2.x |
Shows the number of connections to NetWare 2.x servers. |
|
Connect NetWare 3.x |
Shows the number of connections to NetWare 3.x servers. |
|
Connect NetWare 4.x |
Shows the number of connections to NetWare 4.x servers. |
|
File Data Operations/sec |
Shows the rate at which the redirector is processing data operations. In general, one operation includes many bytes, although this may not always be the case because of operation overhead. You can determine the efficiency of this path by dividing the value of Bytes/sec by the value of File Data Operations/sec to determine the average number of bytes transferred per operation. |
|
File Read Operations/sec |
Shows the rate at which applications are asking the redirector for data. Each call to a file system (or similar application programming interface (API) call) counts as one operation. |
|
File Write Operations/sec |
Shows the rate at which applications are sending data to the redirector. Each call to a file system (or similar API call) counts as one operation. |
|
Packet Burst IO/sec |
Shows the sum of the values of Packet Burst Read NCP Count/sec and Packet Burst Write NCP Count/sec. |
|
Packet Burst Read NCP Count/sec |
Shows the rate at which NetWare Core Protocol (NCP) requests packet burst reads. The windowing Packet Burst Protocol is built on top of Internetwork Packet Exchange (IPX). It can speed the transfer of multiple-packet NCP file reads and writes. |
|
Packet Burst Read Timeouts/sec |
Shows the rate at which the Client Service for NetWare was required to retransmit a packet burst read request because the NetWare server took too long to respond. |
|
Packet Burst Write NCP Count/sec |
Shows the rate at which NCP requests packet burst writes. |
|
Packet Burst Write Timeouts/sec |
Shows the rate at which the Client Service for NetWare was required to retransmit a burst write request because the NetWare server took too long to respond. |
|
Packets Received/sec |
Shows the rate at which the redirector receives packets, also called server message blocks (SMBs). Network transmissions are divided into packets. The average number of bytes received in a packet can be obtained by dividing the value of Bytes Received/sec by the value of Packets Received/sec. Some packets received might not contain incoming data (for example, an acknowledgment to a write operation made by the redirector would count as an incoming packet). |
|
Packets Transmitted/sec |
Shows the rate at which the redirector sends packets. The average number of bytes transmitted in a packet can be obtained by dividing the value of Bytes Transmitted/sec by the value of Packets Transmitted/sec. |
|
Packets/sec |
Shows the rate at which the redirector processes data packets. In general, one packet includes many bytes, although this may not always be the case because each packet has protocol overhead. The average number of bytes transferred in a packet can be obtained by dividing the value of Bytes/sec by the value of Packets/sec. You can also divide this counter by the value of Operations/sec to determine the average number of packets per operation, another measure of efficiency. |
|
Read Operations Random/sec |
Shows the rate at which, on a file-by-file basis, nonsequential read operations are made. If a read is made using a particular file handle, and then is followed by another read that is not the next contiguous byte, this counter is incremented by one. |
|
Read Packets/sec |
Shows the rate at which read packets are being placed on the network. Each time a single packet is sent with a request to read data remotely, this counter is incremented by one. |
|
Server Disconnects |
Shows the number of times that a server has disconnected the redirector. |
|
Server Reconnects |
Shows the number of times that the redirector reconnected to a server to complete a new active request. The redirector may be disconnected by the server if it remains inactive for too long. Even if all of your remote files are closed, the redirector keeps your connections intact on your local computer for about 10 minutes. Such inactive connections are called dormant connections. Reconnecting may take a substantial period of time. |
|
Server Sessions |
Shows the total number of security objects managed by the redirector. Logging on to a server followed by a network access to the same server establishes one connection, but two sessions. Each session corresponds to one security object. |
|
Write Operations Random/sec |
Shows the rate at which, on a file-by-file basis, nonsequential write operations are made. If a write is made using a particular file handle, and then is followed by another write that is not the next contiguous byte, this counter is incremented by one. |
|
Write Packets/sec |
Shows the rate at which write operations are sent to the network. Each time a single packet is sent with a request to write remote data, this counter is incremented by one. |