What causes “Reconnections made” statistics on network? – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.
But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows, networking, , , .
A client site is having hard-to-diagnose issues related to their network. While working on the problem, I ran the command “net statistics workstation” on one of the computers. I got the following data covering approximately a week of activity:
Bytes received 23791085485 Server Message Blocks (SMBs) received 22410645 Bytes transmitted 8962989188 Server Message Blocks (SMBs) transmitted 22410618 Read operations 4481436 Write operations 2275694 Raw reads denied 0 Raw writes denied 0 Network errors 0 Connections made 629 Reconnections made 990560 Server disconnects 40 Sessions started 0 Hung sessions 0 Failed sessions 0 Failed operations 22 Use count 1212 Failed use count 198
I’m thinking the very large number of “Reconnections made” (almost a million of them, so almost 2 per second for a week) should be telling me something about what’s going on with this network. What precisely does that number represent and what does it indicate? How about the other numbers?
Thanks for any help!
You can use the Redirector object in perfmon to get statistics about the Workstation service. The descriptions of each counter in perfmon is a good place to start when you have no idea what they mean.
Directly from perfmon, here is the Microsoft description of “Reconnections Made” which is labelled as “Server Reconnects” in perfmon:
Server Reconnects counts the number of times your Redirector has had
to reconnect to a server in order to complete a new active request.
You can be disconnected by the Server if you remain inactive for too
long. Locally even if all your remote files are closed, the
Redirector will keep your connections intact for (nominally) ten
minutes. Such inactive connections are called Dormant Connections.
Reconnecting is expensive in time.