Redirector Object
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
The Redirector performance object consists of counters that monitor network connections originating at the local computer.
| Counter Name | Description | Counter Type |
|---|---|---|
Bytes Received/sec |
Shows the rate, in incidents per second, of bytes that were received by the redirector from the network. It includes all application data and network protocol information, such as packet headers. |
|
Bytes Total/sec |
Shows the rate, in incidents per second, at which the redirector processed data bytes. This includes all application and file data as well as protocol information, such as packet headers. |
|
Bytes Transmitted/sec |
Shows the rate, in incidents per second, at which bytes left the redirector to the network. It includes all application data and network protocol information, such as packet headers. |
|
Connects Core |
Shows the number of connections to servers running the original MS-Net SMB protocol, including MS-Net itself, Xenix, and VAXs. |
|
Connects LAN Manager 2.0 |
Shows the number of connections to LAN Manager 2.0 servers, including LMX servers. |
|
Connects LAN Manager 2.1 |
Shows the number of connections to LAN Manager 2.1 servers, including LMX servers. |
|
Connects Windows NT |
Shows the total number of connections to computers that are running Windows NT, Windows 2000, Windows XP, and the Windows Server 2003 family. |
|
Current Commands |
Shows the number of requests to the redirector that were queued for service. If this number is much larger than the number of network adapter cards installed in the computer, then the network(s) and/or the server(s) being accessed are seriously bottlenecked. |
|
File Data Operations/sec |
Shows the rate, in incidents per second, at which the redirector processed data operations. To determine the efficiency of this path, calculate the average number of bytes transferred per operation by dividing the value of Bytes/sec by the value of this counter |
|
File Read Operations/sec |
Shows the rate, in incidents per second, at which applications asked the redirector for data. Each call to a file system, or similar application program interface (API) call, is counted as one operation. |
|
File Write Operations/sec |
Shows the rate, in incidents per second, at which applications sent data to the redirector. Each call to a file system, or similar API call, counts as one operation. |
|
Network Errors/sec |
Shows the rate, in incidents per second, at which serious unexpected errors occurred. Such errors generally indicate that the redirector and one or more servers are having serious communication difficulties. For example, a Server Manager Block protocol error generates a network error. An entry is written in the system event log, and can provide details. |
|
Packets Received/sec |
Shows the rate, in incidents per second, at which the redirector received packets (also called server message blocks or SMBs). Network transmissions are divided into packets. To calculate the average number of bytes received in a packet, divide the value of Bytes Received/sec by the value of this counter. Some packets received might not contain incoming data (for example, an acknowledgment of a write operation made by the redirector is counted as an incoming packet). |
|
Packets Transmitted/sec |
Shows the rate, in incidents per second, at which the redirector sent packets (also called server message blocks or SMBs). Network transmissions are divided into packets. To calculate the average number of bytes transmitted in a packet, divide the value of Bytes Transmitted/sec by the value of this counter. |
|
Packets/sec |
Shows the rate, in incidents per second, at which the redirector processed data packets. To determine the efficiency of this path, calculate the average number of bytes transferred per packet by dividing the value of Bytes Transmitted/sec by the value of this counter. For another measure of efficiency, calculate the average number of packets transferred per operation by dividing the value of this counter by the value of Operations/sec. |
|
Read Bytes Cache/sec |
Shows the rate, in incidents per second, at which applications used the redirector to access the file system. Some data requests are satisfied by retrieving the data from the cache. Requests that miss the cache cause a page fault. |
|
Read Bytes Network/sec |
Shows the rate, in incidents per second, at which applications read data across the network. This occurs when data sought in the file system cache is not found there and must be retrieved from the network. Dividing this value by the value of Bytes Received/sec indicates the proportion of application data that is traveling across the network. |
|
Read Bytes Non-Paging/sec |
Shows the number of bytes, in incidents per second, read by the redirector in response to normal file requests by an application when they were redirected to come from another computer. In addition to file requests, this counter includes other methods of reading across the network, such as Named Pipes and Transactions. This counter counts only application data, not network protocol information. |
|
Read Bytes Paging/sec |
Shows the rate, in incidents per second, at which the redirector attempted to read bytes in response to page faults. Page faults are caused by loading modules (such as programs and libraries), by a miss in the file system cache, or by files directly mapped into the address space of applications. |
|
Read Operations Random/sec |
Shows the rate, in incidents per second, at which, on a file-by-file basis, non-sequential read operations are made. If a read operation is made using a particular file handle, and then is followed by another read operation that is not the next contiguous byte, this counter is incremented by one. |
|
Read Packets Small/sec |
Shows the rate, in incidents per second, at which read operations of less than one-fourth of the server's negotiated buffer size were made by applications. A high rate of small packet read operations indicates the possibility that buffers are being used inefficiently. This counter is incremented once for each small read operation. It does not count packets. |
|
Read Packets/sec |
Shows the rate, in incidents per second, at which read packets were placed on the network. Each time a single packet is sent with a request to read data remotely, this counter is incremented by one. |
|
Reads Denied/sec |
Shows the rate, in incidents per second, at which the server was unable to accommodate requests for raw read operations. When a read operation is much larger than the server's negotiated buffer size, the redirector requests a raw read operation. If granted, a raw read operation permits the transfer of the data without much protocol overhead on each packet. However, to accomplish a raw read operation, the server must lock out other requests; if the server is too busy, the request is denied. |
|
Reads Large/sec |
Shows the rate, in incidents per second, at which read operations that were more than double the server's negotiated buffer size were made by applications. Too many large read operations could place a strain on server resources. This counter is incremented once for each large read operation. It does not count packets. |
|
Server Disconnects |
Shows the number of times that a server has disconnected the redirector. |
|
Server Reconnects |
Shows the number of times that the redirector had to reconnect to a server to complete a new active request. Users can be disconnected by the server if they remain inactive for too long. Even if all remote files are closed, the redirector keeps connections intact locally for about ten minutes. Such inactive connections are called dormant connections. Reconnecting is expensive in time. |
|
Server Sessions |
Shows the total number of security objects that are managed by the redirector. For example, logging on to a server followed by a network access to the same server establishes one connection, but two sessions. |
|
Server Sessions Hung |
Shows the number of active sessions that were timed out and were unable to proceed due to a lack of response from the remote server. |
|
Write Bytes Cache/sec |
Shows the rate, in incidents per second, at which applications on a computer used the redirector to write to the file system cache. The data might not leave the computer immediately; it can be retained in the cache for further modification before being written to the network, reducing network traffic. Every byte that is written to the cache is counted here. |
|
Write Bytes Network/sec |
Shows the rate, in incidents per second, at which applications wrote data across the network. This occurs when the file system cache is bypassed, such as for named pipes or transactions, or else when the cache writes the bytes to disk to make room for other data. To calculate what proportion of application data is being written to the network, divide the value of this counter by the value of Bytes Transmitted/sec. |
|
Write Bytes Non-Paging/sec |
Shows the rate, in incidents per second, at which bytes were written by the redirector. This is in response to normal file outputs by an application, when the bytes were redirected to another computer. In addition to file requests, this counter includes other methods of writing across the network such as Named Pipes and Transactions. This counter only counts application data, and does not count network protocol information. |
|
Write Bytes Paging/sec |
Shows the rate, in incidents per second, at which the redirector attempted to write bytes that were changed in the pages being used by applications. The program data changed by modules (such as programs and libraries) that were loaded over the network are paged out when no longer needed. Other output pages come from the cache. |
|
Write Operations Random/sec |
Shows the rate, in incidents per second, at which, on a file-by-file basis, non-sequential write operations were made. If a write operation is made using a particular file handle and then is followed by another write operation that is not the next contiguous byte, this counter is incremented by one. |
|
Write Packets Small/sec |
Shows the rate, in incidents per second, at which write operations were made by applications that are less than one-fourth of the server's negotiated buffer size. Too many write operations can indicate a waste of buffers on the server. This counter shows write operations, not packets, and is incremented once for each write operation. |
|
Write Packets/sec |
Shows the rate, in incidents per second, at which write operations were sent to the network. Each time a single packet is sent with a request to write remote data, this counter is incremented by one. |
|
Writes Denied/sec |
Shows the rate, in incidents per second, at which the server was unable to accommodate requests for raw write operations. When a write operation is much larger than the server's negotiated buffer size, the redirector requests a raw write operation. If granted, a raw write operation permits the transfer of the data without much protocol overhead on each packet. However, to accomplish a raw write operation, the server must lock out other requests; if the server is too busy, the request is denied. |
|
Writes Large/sec |
Shows the rate, in incidents per second, at which write operations that were more than double the server's negotiated buffer size were made by applications. Too many large write operations could place a strain on server resources. This counter is incremented once for each large write operation. It does not count packets. |