Start a Conversation



2 Posts


October 5th, 2023 13:59

Dell Latitude 3420 / VMware Client keeps disconnecting / reconnecting to WiFi

Good Day Everyone.  We have had an ongoing issue where a number of users are reporting their Dell Latitude 3420s are going through some kind of cycle where they disconnect and then reconnect every 5 minutes or so.  This results in their vmware session freezing up for 1 - 5 seconds and in some cases completely disconnecting.  All of the users have reported that their other devices at home are not having this issue at all.  If they come into the office and work on WiFi with these same Latitudes, they do not have any problems.  We have been working with Dell support on the issue for quite awhile and still no answers.  I have been checking through the wlan.logs for these users and tend to see this when the cycle happens:

20231005-090446.345: WLAN: CTRL-EVENT-CONNECTED - Connection to a8:70:5d:e8:f9:ec completed [id=0 id_str=]
20231005-090446.346: bgscan: Initialized module 'simple' with parameters '30:-70:300'
20231005-090446.349: WLAN: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=245000
20231005-090946.353: Scan requested (ret=0) - scan timeout 30 seconds
20231005-090950.332: WLAN: Scan completed in 3.979394 seconds
20231005-090950.334: WLAN: AP candidate [a8:70:5d:e8:f9:ec] (dBm=-51, ch=5220)
20231005-090950.334: WLAN: AP candidate [a8:70:5d:e8:f9:eb] (dBm=-37, ch=2462)
20231005-090950.334: WLAN: No need to roam
20231005-091444.351: WLAN: CTRL-EVENT-DISCONNECTED bssid=a8:70:5d:e8:f9:ec reason=3 locally_generated=1
20231005-091444.352: bgscan: Deinitializing module 'simple'
20231005-091444.352: WLAN: CTRL-EVENT-DSCP-POLICY clear_all
20231005-091444.358: Scan requested (ret=0) - scan timeout 30 seconds
20231005-091446.220: WLAN: Scan completed in 1.861693 seconds
20231005-091446.371: WLAN: CTRL-EVENT-DSCP-POLICY clear_all
20231005-091446.377: WLAN: SME: Trying to authenticate with a8:70:5d:e8:f9:ec (SSID='dawhill' freq=5220 MHz)
20231005-091446.411: WLAN: Trying to associate with a8:70:5d:e8:f9:ec (SSID='dawhill' freq=5220 MHz)
20231005-091446.425: WLAN: Associated with a8:70:5d:e8:f9:ec
20231005-091446.425: WLAN: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
20231005-091446.430: WLAN: WPA: Key negotiation completed with a8:70:5d:e8:f9:ec [PTK=CCMP GTK=CCMP]
20231005-091446.430: WLAN: CTRL-EVENT-CONNECTED - Connection to a8:70:5d:e8:f9:ec completed [id=0 id_str=]

Is anyone else seeing similar behavior?  Are there other log files I should be checking for clues as to what is happening?  I've done a large amount of Googling and information on what these codes mean is pretty scarce.  Any hints on how work towards a resolution would be appreciated!

October 16th, 2023 20:38

Think we figured this one out.  I was looking through the nm.log file and noticed that the device seemed to be having issues with connecting to a time server.  Long story short, there was a typo in our configuration that prevented the Latitudes from connecting to a time server when not on our local network.  I fixed that and no more issues...

No Events found!