?
Solved

Event id 5783 on Win 2000 Terminal Servers

Posted on 2009-05-08
7
Medium Priority
?
412 Views
Last Modified: 2013-12-05
Every now and then we get the following message in the event logs on our Terminal servers:-

NETLOGON,Error,None,5783,N/A,SERVERX,The session setup to the Windows NT or
Windows 2000 Domain Controller \\serverY.domainname for the domain domainname is not responsive.  The current RPC call from Netlogon on \\SERVERX to \\serverY.domainname has been cancelled. (Actual server names/domain name not shown in text).

It happens on a random basis and users then start to notice that the server is non-responsive, until it seems to grind to a halt. We then have to hard reboot using the power button, the server won't even shut down.

We have two domain controllers that also act as wins servers and the error may point to either of the controllers.

I read MS article - http://technet.microsoft.com/en-us/library/bb727055.aspx and checked the dns. Both controllers are listed as wins lookup, name servers and both have host records.

I'm not sure where to look next with this one. The MS article suggests potential rpc call problems.
0
Comment
Question by:jon_kershaw
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 15

Expert Comment

by:zelron22
ID: 24335732
A lot of unusual Windows 2000 Terminal SErver problems can be traced back to printer drivers.  W2K terminal servers are notoriously temperamental about printer drivers.

http://www.msterminalservices.org/articles/hunt-bad-printer-driver.html
http://www.msterminalservices.org/articles/Managing-Printer-Drivers.html
   

0
 

Author Comment

by:jon_kershaw
ID: 24435152
Hi,

I read the articles and having just completed a rbuild of one of the Terminal servers, I have set all printers (all HP 4000 series) to use 4250 drivers - so far things seem ok. Will monitor for a few days more - thanks.
0
 

Author Comment

by:jon_kershaw
ID: 24439511
Spoke too soon - the one of the Terminal Servers has had the same error again and locked up - only forcing reboot by poer off/on would work.
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
LVL 15

Expert Comment

by:zelron22
ID: 24440922
Did you just install the base drivers, or did you also install the printer management software?  That often is the cause.

However, you may be having hardware issues, such as memory issues, or some app that's causing the problem.  Any errors in the event logs on the terminal servers?
0
 

Author Comment

by:jon_kershaw
ID: 24676790
Sorry for the delay, but I've been out of the office and there has only been one incident in the last couple of week. I updated only the HP driver. There's error msgs keep appearing in the logs on the DC that's reported as being non-responsive in the eventid 5783 errors on the Termnal Server. The errors in the DC log occur roughly every hour and one appeared just before the last lockup. The error is:

Source: MrxSmb
Type: Error
Event: Code 8003
Computer: ServerY
 Description:
 The master browser has received a server announcement from the computer XXXSERVER that believes that it is the master browser for the for the domain on transport NetBT_Tcpip_(36D5D40E-B09A-4DF7). The master browser is stopping or an election is being forced.

ServerY is the DC and XXXSERVER is a Unix machine on our network that provides Internet firewall services. I checked on the Unix machine, as it has a feature that allows it to be the Master Browser. The feature is turned off. I've contacted the firewall manufacturer about this proble, but so far no response.

Since the last crash, I've swapped the network card on the DC and so, no Terminal Server crashes, but still hourly Event ID 8003 msgs.

I'm keeping this incident open for a while longer and keeping an eye on the Terminal Servers.
0
 
LVL 15

Accepted Solution

by:
zelron22 earned 2000 total points
ID: 24904268
Have you resolved this?

Another thing to check with that error (5783) is the DNS settings on the terminal server.  Assuming that the terminal server is a member of your domain it needs to be pointed to an AD aware DNS server and ONLY that.  Then the DNS server should be set up as a forwarder for other requests.

0
 

Author Comment

by:jon_kershaw
ID: 25276217
The Terminal Server is a member of a domain. There are two domain controllers, both provide AD aware DNS services. One of the DNS servers (ServerY) has a forwarder, the other (ServerX) does not.

At present the TCP/IP DNS and WINS settings on the Terminal Server network card point to ServerX first, then ServerY - things seem to be more stable this way, with only two crashes in almost as many months.

On the two Domain controllers, the WINS setting on each server's network card points to itself and the DNS settings on the cards lists ServerY (the one with the forwarder) first, followed by ServerX.

When checking the DNS server properties for the domain on both DC servers, both the DNS and WINS servers are listed ServerY (the one with the forwarder) then ServerX. ServerY is not easy to check for network card settings, as the connection disappears from the Network and Dial Up Connections list (and the icon from the Windows Taskbar) when the server has been running for a couple of days after a reboot.

With the recession starting to ease, I've now got management approval to purchase new DCs and Terminal Servers over the next few monts. I'm hopeful that the guys who install the servers will be able put an end to these problems.
0

Featured Post

Enroll in August's Course of the Month

August's CompTIA IT Fundamentals course includes 19 hours of basic computer principle modules and prepares you for the certification exam. It's free for Premium Members, Team Accounts, and Qualified Experts!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
New style of hardware planning for Microsoft Exchange server.
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…

800 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question