Article ID: 281382 - View products that this article applies to.
This article was previously published under Q281382
The WinRoute tool connects to the link state port (TCP 691) on a server that is running Exchange 2000 Server or Exchange Server 2003, and extracts the link state information for the Exchange organization. WinRoute presents link state information in its original format.
Installing WinRouteTo install WinRoute with Exchange 2000, run the Microsoft Exchange 2000 Server Resource Kit Setup program. You can also install the tool by following these steps:
How to Use WinRoute
Important To determine the current size of link state data for the organization, copy the information from the lower pane, and then paste it in a Notepad (.txt) file. The size of this new file is equal to the size of the link state data.
You can use WinRoute to view the routing groups and the Major Version attribute that identifies the current sequence number for the routing group. You can also view the status of each connector. If a particular routing group has a version number of zero, link state information from that routing group's master has not yet been received. In this case, the two servers synchronize link state information by comparing the GUIDs that are associated with each routing group.
To save the information that is displayed by WinRoute, click Save As on the File menu. Save this file with an .rte extension so that it can be opened remotely by WinRoute.
TroubleshootingIf the screen is blank after you start WinRoute, the Routing Engine service (RESvc) may not have been initialized or started. If this is the case, make sure that RESvc, the SMTP service, and the MSExchangeMTA services have been started. You may also want to send a message to the SMTP engine to verify that the component is working. For more information about link state routing in Exchange 2000 and Exchange 2003, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/263249/ )Link state routing in Exchange 2000 Server
Article ID: 281382 - Last Review: December 3, 2007 - Revision: 6.3