Advertisement

10.13.2008 at 09:05AM PDT, ID: 23809894
[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!
6.8

Error connecting to workstation

Asked by StoneG in SBS Small Business Server, Windows Networking, Windows XP Operating System

Tags: , ,

SBS 2003 shows the events below on only one of about 30 workstations on our LAN.
It shows this every morning when the operator logs on.

The workstation [referred to in the error messages as "XXXX"] is running XP Pro SP3.

This workstation is the only workstation that shows the correct [real world] time. Even our servers are about 17 minutes ahead of real time as are all of the other workstations. There is some problem that has existed for years that keeps our system at +17 minutes. It has never been a problem...just a little pain.

I can find nothing on the workstation that would account for this discrepancy in the time.
There is no problem with this workstation connecting to the LAN or Internet. There are no hardware issues.

The time thing is one part of the issue.
The other part is that the error messages keep referring to XXXX as a "server".
That bothers me.
I have never seen any of the other workstations referred to as a server on our LAN.

Is there a reason for concern?
Is it possible that this workstation is trying to work as a server in some capacity, maybe as a bot?
I have run SpywareDoctor, Spybot S&D, Adaware, HijackThis, & RootKit Revealer and found nothing.


Start Free Trial 
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:

Event Type:	Error
Event Source:	Kerberos
Event Category:	None
Event ID:	5
Date:		10/13/2008
Time:		7:41:45 AM
User:		N/A
Computer:	[SERVER]
Description:
The kerberos client received a KRB_AP_ERR_TKT_NYV error from the server XXXX$.  This indicates that the ticket used against that server is not yet valid (in relationship to that server time).  Contact your system administrator  to make sure the client and server times are in sync, and that the KDC in realm DOMAIN.OFFICE is  in sync with the KDC in the client realm.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
Event Type:	Warning
Event Source:	LSASRV
Event Category:	SPNEGO (Negotiator) 
Event ID:	40960
Date:		10/13/2008
Time:		7:41:46 AM
User:		N/A
Computer:	[SERVER]
Description:
The Security System detected an authentication error for the server cifs/ XXXX.DOMAIN.office.  The failure code from authentication protocol Kerberos was "{Operation Failed}
The requested operation was unsuccessful.
 (0xc0000001)".
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 01 00 00 c0               ...À    
 
 
 
Event Type:	Warning
Event Source:	LSASRV
Event Category:	SPNEGO (Negotiator) 
Event ID:	40960
Date:		10/13/2008
Time:		8:01:48 AM
User:		N/A
Computer:	[SERVER]
Description:
The Security System detected an authentication error for the server cifs/ XXXX.  The failure code from authentication protocol Kerberos was "{Operation Failed}
The requested operation was unsuccessful.
 (0xc0000001)".
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 01 00 00 c0               ...À
 
Keywords: Error connecting to workstation
Title
1 rootkit remover
2 Rootkit detected by RootkitBuster...…
3 1527 Rootkits Found
4 rootkit suspect
5 Hijackthis log file
6 Svchost.exe rootkit still there after for…
 
Loading Advertisement...
 
[+][-]10.13.2008 at 09:29AM PDT, ID: 22703775

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]10.13.2008 at 09:30AM PDT, ID: 22703779

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]10.13.2008 at 10:18AM PDT, ID: 22704199

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]10.13.2008 at 02:58PM PDT, ID: 22706900

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: SBS Small Business Server, Windows Networking, Windows XP Operating System
Tags: Microsoft, Exchange, SBS 2003 SP2
Sign Up Now!
Solution Provided By: shekerra
Participating Experts: 3
Solution Grade: A
 
 
[+][-]10.13.2008 at 03:17PM PDT, ID: 22707058

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 7-day free trial to view this Assisted Solution or ask the Experts your question.

 
[+][-]10.13.2008 at 05:46PM PDT, ID: 22707830

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]10.14.2008 at 07:28AM PDT, ID: 22711585

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]10.14.2008 at 08:01AM PDT, ID: 22711942

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]10.20.2008 at 01:38PM PDT, ID: 22761906

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628