You may receive error messages and you may receive frequent Stop error messages

Microsoft states in their article: 899268

You may receive error messages and you may receive frequent Stop error messages that indicate that the Srv.sys or the Netbt.sys driver has failed when you use Terminal Services to connect to a computer that is running Windows 2000 Server
View products that this article applies to.
Article ID : 899268
Last Review : February 28, 2006
Revision : 1.0
On This Page
SYMPTOMS SYMPTOMS
CAUSE CAUSE
RESOLUTION RESOLUTION
Hotfix information Hotfix information
Prerequisites Prerequisites
Restart requirement Restart requirement
Hotfix replacement information Hotfix replacement information
File information File information
STATUS STATUS
MORE INFORMATION MORE INFORMATION
APPLIES TO APPLIES TO
SYMPTOMS
Consider the following scenario. You use Terminal Services to connect to a computer that is running Windows 2000 Server. This computer also hosts third-party software. In this scenario, you may experience the following symptoms:
• You receive frequent Stop error messages. These messages indicate that the Srv.sys driver has failed or that the Netbt.sys driver has failed.
• You receive any one of the following error messages from the computer that is running Windows 2000 Server. You receive the error message when you try to establish a connection to another server by using the NetBIOS name:
Error 6
ERROR_INVALID_HANDLE
The handle is invalid.
Error 22
ERROR_BAD_COMMAND
The device does not recognize the command
Error 995
ERROR_OPERATION_ABORTED
The I/O operation has been aborted because of either a thread exit or an application request.
Error 1229
ERROR_CONNECTION_INVALID
An operation was attempted on a nonexistent network connection.
Note If you connect to the computer that is running Windows 2000 Server by using its IP address or by using its fully qualified domain name, you do not receive these error messages.
Back to the top Back to the top
CAUSE
This problem occurs if of the TCP transport driver (Tdtcp.sys) does not function correctly.
Back to the top Back to the top
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
No prerequisites are required.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
File name File version File size Date Time Platform
Tdasync.sys 5.0.2195.7052 12,696 06-Jun-2005 18:59 x86
Tdipx.sys 5.0.2195.7052 20,792 06-Jun-2005 18:59 x86
Tdnetb.sys 5.0.2195.7052 18,392 06-Jun-2005 18:59 x86
Tdpipe.sys 5.0.2195.7052 10,584 06-Jun-2005 18:59 x86
Tdspx.sys 5.0.2195.7052 18,264 06-Jun-2005 18:59 x86
Tdtcp.sys 5.0.2195.7052 19,032 06-Jun-2005 18:59 x86
Termdd.sys 5.0.2195.6692 35,832 19-Jun-2003 07:35 x86
Back to the top Back to the top
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top Back to the top
MORE INFORMATION
For more information about standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 (http://support.microsoft.com/kb/824684/) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top Back to the top
APPLIES TO
• Microsoft Windows 2000 Advanced Server
• Microsoft Windows 2000 Server
Back to the top Back to the top
Keywords:
kbbug kbfix kbqfe kbwin2000presp5fix kbmsccsearch kbpubtypekc KB899268



Primary links

Custom Search

Who's new

  • japhabept
  • Rullydery
  • eagenorce
  • rittaarier
  • swasseZex

Who's online

There are currently 0 users and 3 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.