Article ID: 889000 - View products that this article applies to.
On a Microsoft Windows XP Service Pack 2 (SP2)-based computer, when you map a network drive or connect to a network share by using a UNC path name such as \\server_name\share_name, the following event log warning entry may be written in the System Event log:
Note The FinalStatus c0000184 in the Data Words section of the event log entry translates to the following:
Event ID: 3019 Source: MRxSmb Type: Warning Description: The redirector failed to determine the connection type. For more information, see Help and Support Center at http://support.microsoft.com. Data Words 0000: 00000000 004e0004 00000000 80000bcb 0010: 00000000 c0000184 00000000 00000000 0020: 00000000 00000000
STATUS_INVALID_DEVICE_STATE, 'The device is not in a valid state to perform this request.'
This problem can occur when NetBIOS over TCP/IP (NetBT) tries to query a loopback adaptor as a destination device to determine network speed. The loopback adaptor does not handle speed negotiation. Therefore, the loopback adaptor cannot negotiate network speed.
Note This problem is associated only with the TCP/IP protocol because TCP/IP is the only protocol that uses the loopback adaptor.
To avoid the event log warning entry in the System Event log, you can install Update for Windows XP SP2. This update is described in the following article in the Microsoft Knowledge Base:
884020Note This problem is resolved in the file Tcpip.sys version 5.1.2600.2505 and later versions.
(https://support.microsoft.com/kb/884020/ )Programs that connect to IP addresses that are in the loopback address range may not work as you expect in Windows XP Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
If you find the same event log warning entry in the System Event Log in an earlier version of Windows XP, see the following article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/315244/ )Error message: The redirector failed to determine the connection type
Article ID: 889000 - Last Review: September 20, 2006 - Revision: 2.2