Advertisement

05.15.2008 at 06:14AM PDT, ID: 23404926
[x]
Attachment Details
[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!

Domain Contoller doesn't appear as connected

I am running Surf Control (SC)web filter to regulate internet access for our users.  I am getting inconsistent behaviour wtih Surf Contol following the rules that I have set up.  Surf Control tech support tells me that it is because the SC server is not connecting to all Domain Contollers properly.  They had me run a command "NETSTAT -AN FIND "61695".  It showed that two of my three domain controllers were connnected.  100.10 is the SC server. The results were:

TCP 0.0.0.0:61695  0.0.0.0.:0   LISTENING
TCP 192.168.100.10:61695 192.168.100.3:1721  ESTABLISHED
TCP 192.168.100.10:61695 192.168.100.8:1721  ESTABLISHED

The two DCs that show up are Win 2000.  The missing DC is Win 2003. I need to somehow get my third DC connected and to show up here for it to work properly. I can browse network neighborhood and see this DC from the SC server I can ping back and forth using IP address or FQDN fine.  Can someone give me a suggestion on how to get this third DC to show up as an established connection on the SC server?  Any more information needed is gladly provided.  Thank you in advance for any help.  
Start your free trial to view this solution
Question Stats
Zone: OS
Question Asked By: Tenrags
Solution Provided By: Jay_Jay70
Participating Experts: 1
Solution Grade: B
Views: 0
Translate:
Loading Advertisement...
05.16.2008 at 01:58AM PDT, ID: 21581023

Rank: Sage

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
06.02.2008 at 03:58PM PDT, ID: 21696422

Rank: Sage

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 
Loading Advertisement...
20080236-EE-VQP-29 / EE_QW_2_20070628