Domain login issues with Dell G7 15 7588 laptops when connected to the WLAN

realtimer
realtimer used Ask the Experts™
on
We have 4 new Dell G7 15 7588 laptops that were upgrade from Windows 10 Home to Pro that are connected to the companies domain and connected to the wlan. The users are experiencing issues logging into the domain, where approximately 9 out of 10 times state that the password is incorrect. We have verified that the password is correct when being entered and have removed the laptops from the domain and rejoined them but the issue persists.

The laptops do not have issues logging in when hard wired into the network and other laptops connected to the wireless network are not experiencing issues. Also, Active Directory is not referencing any failed login attempts for the users trying to login to the laptops on the wireless network.

Any help would be greatly appreciated
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2018

Commented:
Just make sure that the Wifi card picks up the correct DNS server (the domain controller's IP address), that is important and, if not set that way, will explain your problems.

Author

Commented:
Thank you McKnife for your response. We did verify that the wifi card was picking up the correct DNS server.
Distinguished Expert 2018

Commented:
Could it be that the wifi connection is simply unstable?
Please logon with a local account and do some tests:

1 ping the DC:
ping your.com -t

Open in new window

-n 100
Please share the response times and packet loss (if any) for these 100  packets
2 open cmd.exe and launch
runas /user:your.dom\someADuser notepad

Open in new window

You'll be asked for the password - does that succeed? If not, is that logged at the DC as failed logon in the security log?
OWASP: Forgery and Phishing

Learn the techniques to avoid forgery and phishing attacks and the types of attacks an application or network may face.

Author

Commented:
Below are the ping results. Also, attempting to launch notepad as the user does not work and the DC does not show failed logon in the security log.

Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=17ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=15ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=12ms TTL=128
Reply from 192.168.1.223: bytes=32 time=3ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=3ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=3ms TTL=128
Reply from 192.168.1.223: bytes=32 time=3ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=5ms TTL=128
Reply from 192.168.1.223: bytes=32 time=3ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=8ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=3ms TTL=128
Reply from 192.168.1.223: bytes=32 time=3ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=9ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=6ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=24ms TTL=128
Reply from 192.168.1.223: bytes=32 time=3ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=16ms TTL=128
Reply from 192.168.1.223: bytes=32 time=3ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=9ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=2ms TTL=128
Reply from 192.168.1.223: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.1.223:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 24ms, Average = 2ms
Distinguished Expert 2018

Commented:
Ok, looks vey stable for WLAN.
Could I get an
ipconfig /all
output of the client, please?
Thank you for your help. We are unsure if the inplace upgrade from Windows 10 Home to Pro was causing the issue but reloading Windows 10 Pro on the laptops fixed the problem.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial