• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 590
  • Last Modified:

Event errors on PCs in SBS 2003 domain

Hi all

We are seeing numerous error event ID's on PCs attached to a SBS 2003 domain (Events 1097, 1030, 1110 in the Application log and Event 7 in the System log - please see full copy and paste below).

Everything "seems" to be working ok but I am still concerned about these errors. I have a suspicion that they are linked to the fact that at one point, the server was dual homed, but now just has one working NIC, the additional card having been disabled.

Any suggestions gratefully received.

Event 1097

Windows cannot find the machine account, No authority could be contacted for authentication. .

Event 1030

Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine.

Event 1110

Attempt to determine whether user and machine accounts are in the same forest failed (The interface is unknown. ).


Event 7

The kerberos subsystem encountered a PAC verification failure.  This indicates that the PAC from the client xxx0101$ in realm xxxxxx.LOCAL had a PAC which failed to verify or was modified.  Contact your system administrator.
0
actionco
Asked:
actionco
  • 2
  • 2
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Can you please post a COMPLETE IPCONFIG /ALL from both a workstation as well as from your SBS?

Thanks

Jeff
TechSoEasy
0
 
actioncoAuthor Commented:
IPCONFIGS attached.
pc.txt
server.txt
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
So those look good.  Can you verify that the binding order is correct now that you've disabled the other NIC?  To do this, on the SBS open up Network Connections > Advanced > Advanced Settings

Make sure that the currently enabled NIC is on the top of the Connections list.  If it isn't, use the arrows on the right to move it to the top.

Once this is done, rerun the Configure Email and Internet Connection Wizard and reboot the server.

Finally, if that doesn't resolve the error messages you can try resetting the TCP/IP stack on a workstation.  http://support.microsoft.com/kb/299357

Jeff
TechSoEasy
0
 
actioncoAuthor Commented:
All seems to work now, thank you.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now