Windows NT Terminal Server 4.0 problem

wnyarumb · 06-12-2007, 01:38 AM

We have a problem with our local domain controller which is running on
windows NT 4.0 terminal server.

Yesterday it started disconnecting from the network and refusing us
access to all services. From time to time the domain
controllers, lose all network connectivity, and if you try to open
up eventvwr, or services, you get either "The RPC server is unavailable"
or "The RPC server is too busy to complete this operation"

Any idea what causes this? We are desperate now as none of the machines
can authenticate thus no network resource shares.

newhouse1390 · 06-13-2007, 02:19 PM

How many DC's on the domain? Are they all running NT 4?

wnyarumb · 06-14-2007, 12:16 AM

Just the 2 and they both are running NT terminal server.

Black Unicorn · 06-15-2007, 05:45 AM

Sounds very much like you have alot of stale TS sessions where people have instead of clicking start>logoff they have instead choosen disconnect.

After a while lots of stale TS sessions can reap havoc on the RPC service.

A solution if this is the case is to setup terminal services to disconnect any in active sessions after X amount of time.

06-12-2007, 01:38 AM	#1 (permalink)
wnyarumb Registered User Join Date: Jun 2007 Posts: 2 OS: XP	Windows NT Terminal Server 4.0 problem We have a problem with our local domain controller which is running on windows NT 4.0 terminal server. Yesterday it started disconnecting from the network and refusing us access to all services. From time to time the domain controllers, lose all network connectivity, and if you try to open up eventvwr, or services, you get either "The RPC server is unavailable" or "The RPC server is too busy to complete this operation" Any idea what causes this? We are desperate now as none of the machines can authenticate thus no network resource shares.

06-13-2007, 02:19 PM	#2 (permalink)
newhouse1390 Member, Networking Team Join Date: Jan 2005 Location: Ohio Posts: 1,040 OS: Windows Server 2003	Re: Windows NT Terminal Server 4.0 problem How many DC's on the domain? Are they all running NT 4? __________________ Because you can read this thank a teacher, because it's English thank a soldier.

06-14-2007, 12:16 AM	#3 (permalink)
wnyarumb Registered User Join Date: Jun 2007 Posts: 2 OS: XP	Re: Windows NT Terminal Server 4.0 problem Just the 2 and they both are running NT terminal server.

06-15-2007, 05:45 AM	#4 (permalink)
Black Unicorn Registered User Join Date: Jun 2007 Location: Fareham UK Posts: 22 OS: Vista Ultimate x86	Re: Windows NT Terminal Server 4.0 problem Sounds very much like you have alot of stale TS sessions where people have instead of clicking start>logoff they have instead choosen disconnect. After a while lots of stale TS sessions can reap havoc on the RPC service. A solution if this is the case is to setup terminal services to disconnect any in active sessions after X amount of time. __________________ Black Unicorn Solutions Computer Support \| InHouse Software \| Disaster Recovery \| Voice Systems \|