Guest Chris Posted September 25, 2008 Posted September 25, 2008 Two of our machines cannot access the network resources, nothing was ever said to me and I don't usually check these two computer as they actually control our Atmosphere Environment and hardly get used. The backup of the data on these machiens gets pulled from the SBS2003 server itself - using copy commands. I have removed Symantec AV and PC Anywhere and am in the process of doing all Windows updates. The machines do have SP4 installed. The following messages are recorded in Event Log Event Type: Warning Event Source: MRxSmb Event Category: None Event ID: 3034 Date: 9/25/2008 Time: 10:17:06 AM User: N/A Computer: LV09 Description: The redirector was unable to initialize security context or query context attributes. Data: 0000: 00080000 00560002 00000000 80000bda 0010: 00000000 c000005e 00000000 00000000 0020: 00000000 00000000 0000047d c000005e Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5788 Date: 9/25/2008 Time: 10:07:30 AM User: N/A Computer: LV09 Description: Attempt to update HOST Service Principal Names (SPNs) of the computer object in Active Directory failed. The updated values were '<UNAVAILABLE>' and '<UNAVAILABLE>'. The following error occurred: Could not find the domain controller for this domain. Data: 0000: 00000774 Event Type: Warning Event Source: Kerberos Event Category: None Event ID: 10 Date: 9/25/2008 Time: 12:23:14 AM User: N/A Computer: LV09 Description: The kerberos subsystem is having problems fetching tickets from your domain controller using the UDP network protocol. This is typically due to network problems. Please contact your system administrator. Data: 0000: 80090311
Guest Anteaus Posted September 25, 2008 Posted September 25, 2008 RE: Windows 2000 Client Errors within Windows 2003 SBS Domain "Chris" wrote: > Two of our machines cannot access the network resources, nothing was ever > said to me and I don't usually check these two computer as they actually > control our Atmosphere Environment and hardly get used. > Check the time and date matches that of the server. Kerberos cannot obtain tickets if they do not match. Oh, and in view of the role of these machines, have your suit on and helmet ready. <g>
Guest Chris Posted September 25, 2008 Posted September 25, 2008 RE: Windows 2000 Client Errors within Windows 2003 SBS Domain Time on the workstation was ok, off a minutes or so Tried net time \\server /set no luck Once I remove the TCP/IP stack, reboot and re-install stack - all is fine. In talking with the employee - he said this problem has occured before with a similar fix (funny how thing jog their memories). Installing newer version of A/V and will check for known bugs. Trying to figure out if Winsock can be reset on 2k - use to use netsh ip reset winsock or something similar. "Anteaus" wrote: > > > "Chris" wrote: > > > Two of our machines cannot access the network resources, nothing was ever > > said to me and I don't usually check these two computer as they actually > > control our Atmosphere Environment and hardly get used. > > > > Check the time and date matches that of the server. Kerberos cannot obtain > tickets if they do not match. > > Oh, and in view of the role of these machines, have your suit on and helmet > ready. <g>
Recommended Posts