klsphotos
asked on
Wireless connectivity issues
Hello experts,
I am hoping you can help me.
We have a 2003 Active Directory Forest.
We have 3 2008 DC. One physical and 2 Virtual
We use NPS and wireless clients get their ip address from our DHCP server.
We have deployed quite a few new laptops that are having some wireless issues. The behavior is they get a yellow ! and are denied services from our DHCP server.
Sometimes doing a network diagnostics fixes the issue, but at least one is having to do this repeatedly, but upon checking her logs, she does not have this issue when she takes her laptop home.
From what I am seeing when they are off our network, the system is still trying to find our DC for a time source but still allows connectivity through their network.
These errors are repetative on the local system:
This computer was not able to set up a secure session with a domain controller in domain DOMAIN due to the following:
The RPC server is unavailable.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
These have shown up on the DC:
Error
InstanceId : 5722
Message : The session setup from the computermachinename failed
to authenticate.
The name(s) of the account(s) referenced in the security d
atabase is
machinename. The following error occurred:
%Access is denied.
Our DHCP lease is for 2 hours for our wireless client and they get their wireless policy through group policy.
The systems are ghosted and deployed. They are deleted from the domain and ghosted and rejoined with the same names. I have not "yet" seen any proof that anything is duplicated.
This is happening to at least 5 systems that I know about, all laptops.
Any help where to diagnose would be appreciated. If you need more information please let me know.
Thank you,
Karen
I am hoping you can help me.
We have a 2003 Active Directory Forest.
We have 3 2008 DC. One physical and 2 Virtual
We use NPS and wireless clients get their ip address from our DHCP server.
We have deployed quite a few new laptops that are having some wireless issues. The behavior is they get a yellow ! and are denied services from our DHCP server.
Sometimes doing a network diagnostics fixes the issue, but at least one is having to do this repeatedly, but upon checking her logs, she does not have this issue when she takes her laptop home.
From what I am seeing when they are off our network, the system is still trying to find our DC for a time source but still allows connectivity through their network.
These errors are repetative on the local system:
This computer was not able to set up a secure session with a domain controller in domain DOMAIN due to the following:
The RPC server is unavailable.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
These have shown up on the DC:
Error
InstanceId : 5722
Message : The session setup from the computermachinename failed
to authenticate.
The name(s) of the account(s) referenced in the security d
atabase is
machinename. The following error occurred:
%Access is denied.
Our DHCP lease is for 2 hours for our wireless client and they get their wireless policy through group policy.
The systems are ghosted and deployed. They are deleted from the domain and ghosted and rejoined with the same names. I have not "yet" seen any proof that anything is duplicated.
This is happening to at least 5 systems that I know about, all laptops.
Any help where to diagnose would be appreciated. If you need more information please let me know.
Thank you,
Karen
Jakob Digranes
Can you look in Security logs on NPS server to see if there's any denied errors there.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
:-) Well done
ASKER
This was not a easy find. I did confirm time and looked and would do a net time on the servers to confirm time was correct. There was a few issues of time in the logs of these effected systems but they also could not connect to other resources. After looking further into our time, when I saw that our NPS was 14 seconds off I figured that was why and seems to be the reason.