We are dealing with an issue with a number of PC's where the workstation gives up trying to authenticate to NAC. So, how the setup looks is, the computer is connected to the VOIP phone network port and the VOIP phone is connected to the network port under a desk. What happens is this:
Say the phone loses power and goes off
Then the computer that is plugged into phone for its network connection loses connectivity as well
Then say the phone starts to power up
The computer's network connection comes up
Symantec client tries to authenticate NAC (the NIC's status says it's up, but says "identifying")
Symantec client seems to give up and NIC status says unknown or something to that affect
If we disable and reneable the nic (or unseat and reseat the network cable to the computer) then NAC authenticates properly and NIC comes up and gets IP address
The question is how do we deal with this. Telling our end users to unplug their network cable or disable and reenable their NIC obviously does no good if people aren't in the office at the time. Also, we don't have two network jacks at each desk, which is why we need the computer tethered to the phone.
I'm hoping there is a timeout or something somewhere that can be adjusted...whether it's on the switch or in the Symantec Client.
Thoughts?