NOTE: This post was incorrectly posted under "Access Security" previously.\nI misinterpreted the topic as resource access, not MS Access database\nproduct...oh well!....\n\n\nI am new to networking. I recently built a small AD-integrated DNS domain\nnetwork for labbing purposes using my TechNet Plus Server 2003 Ent. OS. The\nsingle server is also running DNS and DHCP. All of my clients (yeah, all SIX\nof them - I did say SMALL!) are running XPsp2. Hosts connect to the network\nusing wireless cards through a linksys NAT-enabled router/switch. The server\nis hard wired to one of the switch ports on the linksys. I am using 128-bit\nWEP encryption\nand further control access using a MAC table of allowed hosts on the\nwireless. Three machines are workstations and three are laptop/portables.\n\nI successfully joined the client machines to the domain. They receive\nDHCP-assigned IP addresses. However, when I run the Netdiag commmand, I\nreceive PASSING results for all tested parameters, EXCEPT the Kerberos test\nwhich gives a: " [FATAL] Kerberos does not have a ticket for\nhost/mymachinename.mydomainname" result.\n\nThe strange thing is that immediately after I joined the machines to the\ndomain and ran Netdiag, a PASSING Kerberos result is obtained. HOWEVER, once\nthe machines are restarted, the Kerberos test yields a consistent FAILED\nstatus. With Server2003/XP, I thought Kerberos v.5 was the default\nauthentication protocol. If my machine is not being authenticated, how come\nI can still access domain resources? Should my audit logs show a "logon"\nevent instead of an "account logon" event if my machine is not authenticated?\n\nDoes anyone have an explanation? I would prefer guidance on how to\nefficiently troubleshoot this problem and not just a "here, do this"\nsolution. The REAL problem is I don't yet have the troubleshooting skills\nto effectively address the apparent Kerberos authentication failures.\n\nAny help would be appreciated.