Advertisement

07.02.2008 at 07:08AM PDT, ID: 23533587
[x]
Attachment Details

Windows 2003 terminal  server  session issue

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.0
Tags:

Event ID ( 54 ) in Source ( NEOFLTR_600_12359 ) cannot be found

Running windows 2003 sp2.  Periodically (about every 3 days) users will start reporting that RDC applications take a long time to switch between screens 2 to 3 minutes. Normally this takes 2 to 3 seconds.   This is my first clue that the below event will occur.  About 2 hours later all RDC sessions are ended. The server has no other symptoms that this.  The event logs are filled with this message and after a reboot the system works fine for several days.  

I believe this is due to Juniper's SSL/VPN's Secure Application Manager application running.  
Questions.
1.      is there any fix for this or patch?
2.      removal of this application will that correct this issue and what impact will that have on RDC connections?

Event Type: Warning
Event Source: NEOFLTR_600_12359
Event Category: None
Event ID: 54
Date: 7/1/2008
Time: 6:38:36 AM
User: N/A
Computer: MYCOMPUTER
Description:
The description for Event ID ( 54 ) in Source ( NEOFLTR_600_12359 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\TcpFilter_NEOFLTR_600_12.
Answered By: JaysonJackson
Expert Since: 02/11/2003
Accepted Solutions: 1
Computer Expertise: Beginner
JaysonJackson has been an Expert for 5 years 11 months, during which he has posted 46 comments and answered 1 question. JaysonJackson is just one of 881 experts in the Windows NT Networking Zone. 1 expert collaborated on this answer, which was graded an "A" by the asker.
 
 
20081119-EE-VQP-47 / EE_QW_2_20070628