GPT Help Desk Study Flashcards
(45 cards)
Steps to troubleshooting
- Identify problem
- Create theory of possible cause
- Test the theory/theories to fix cause
- Verify Functionality
- Document, document, document
Application Crashes Frequently
✅ Check for Software updates
✅ Verify Compatibility
✅ View the Event logs in the event viewer
✅ Reinstall Application
A user cannot access the shared drive
✅ Check network connectivity
✅ Ensure user has permissions in AD
✅ Confirm the correct path is being used
User says no websites load in any browser. How do you troubleshoot it as an internet connection issue?
→ Check if the device is connected to Wi-Fi or Ethernet.
→ If connected, run (ipconfig /all) to check for valid IP, gateway, and DNS.
→ If IP is missing or incorrect, run (ipconfig /release) and (ipconfig /renew).
→ Try to ping the default gateway using (ping <gateway>) to test local network.
→ If successful, ping a public IP like (ping 8.8.8.8) to test external connectivity.
→ If that works, ping a domain like (ping google.com) to check DNS resolution.
→ If DNS fails, flush DNS using (ipconfig /flushdns) or try changing DNS servers.
→ If local pings fail, check physical connection, adapter status, or escalate to networking.</gateway>
What steps would you take if a user reports their internet browser is slow?
→ Try the site in a different browser or incognito mode.
→ If it works there, clear cache and cookies in the original browser.
→ If the issue persists, disable/remove extensions, then restart the browser.
→ Check if all websites are slow or just specific ones.
→ If all are slow, run a speed test.
→ If speed is fine, check Task Manager for high CPU, RAM, or disk usage.
→ If the browser is consuming too many resources and not responding, restart the browser—or the computer if needed.
→ If still unresolved, scan for malware and check for browser updates or corruption.
A user is unable to connect to Wi-Fi. What steps would you take to troubleshoot this?
→ First, check that Wi-Fi is enabled on the user’s device.
→ Verify they are connecting to the correct SSID and using the correct password.
→ Ask if other users or devices can connect to the same network.
- If no one can connect, escalate.
→ If it’s isolated to one user, have them forget the network and reconnect.
→ Toggle the Wi-Fi adapter off and on.
→ Restart the device.
→ If still not working, release and renew the IP using (ipconfig /release) and (ipconfig /renew).
→ If still failes, escalate to networking.
A user cannot access a specific website but can reach others. What might be causing this and how would you troubleshoot?
→ First, try the website in a different browser or incognito mode to rule out cache, cookies, or extensions.
→ If it works in another browser, clear the cache and cookies, disable extensions.
→ If that fails, ping the website to see if it resolves and responds.
→ If ping fails, flush DNS (ipconfig /flushdns) and renew IP (ipconfig /renew).
→ Check firewall or proxy settings to ensure the site isn’t blocked.
→ Test from another device or network to see if it’s a local issue.
A user gets an SSL certificate warning when visiting a secure website. What do you check?
→ Confirm the system date and time are correct.
→ Try accessing the site in a different browser.
→ If works, clear the browser cache, cookies, and possibly disable extensions or try restarting browser.
→ if fails, check for OS updates.
→ If it’s a company site, verify the certificate is not expired or misconfigured.
A user says they are being redirected to strange or unwanted websites. What’s likely happening and how do you fix it?
→ Likely browser hijacking or malware infection.
→ Run a malware scan immediately.
→ Check for unknown or suspicious extensions and remove them.
→ Reset browser settings to default.
→ Clear cache and cookies.
A browser keeps crashing on startup. What steps do you take?
→ Try launching the browser in safe/incognito mode.
→ If works, clear cache/cookies and disable extensions.
→ If fails, check for browser updates or reinstall the browser.
→ If crashing persists, check Event Viewer or run a malware scan.
A user forgot their password and is locked out. How do you help?
→ Verify the user’s identity per company policy.
→ In Active Directory (AD), search for the user account.
→ Unlock the account if it’s locked.
→ Reset the password and select “User must change password at next login” if required.
→ Provide the temp password securely and confirm they can log in.
A user says their password is correct, but they can’t log in. What do you check?
→ Confirm there are no typos or Caps Lock is on.
→ Ask if the user recently changed their password.
→ Check if the account is locked, disabled, or expired in Active Directory.
→ Verify the login domain is correct (especially if on a domain-joined PC).
→ If remote, ensure they are connected to VPN if required for authentication.
A user can’t log in after changing their password. What do you check?
→ Make sure they are using the updated password.
→ Confirm they are not using old saved credentials (auto-fill).
→ If on a laptop, check they are connected to the network or VPN.
→ Verify their account is not locked due to failed attempts.
→ Have them reboot and log in manually if syncing is delayed.
A user is repeatedly locked out after changing their password. What’s likely happening?
→ A saved password on another device (email client, phone, mapped drive, etc.) is causing the lockout.
→ Check Event Viewer or use AD lockout tools to trace the source.
→ Help the user update stored credentials on all devices.
→ Reset the password again if needed and confirm lockouts stop.
A user is connected to Wi-Fi but has no internet. What do you check?
→ Run (ipconfig /all) to check for valid IP and gateway.
→ Ping the default gateway to test internal network access.
→ If gateway ping fails, have the user reconnect to Wi-Fi or reset the adapter.
→ If ping works, test external access with (ping 8.8.8.8) and then (ping google.com).
→ If public IP works but DNS fails, flush DNS with (ipconfig /flushdns) or set a public DNS.
→ If no response at all, escalate to network team—could be DHCP or routing issue.
A user keeps getting disconnected from the network randomly. What steps do you take?
→ Check if the issue happens on Wi-Fi or wired.
→ If Wi-Fi, confirm signal strength and test from a different location.
→ Update or reinstall the network driver.
→ Check power settings and disable network adapter power-saving features.
→ Run (ping -t 8.8.8.8) to monitor for packet drops.
→ If issue continues, escalate for switch/AP port check or interference scan.
A user is reporting they can’t access network resources due to an IP conflict. How do you troubleshoot?
→ Run (ipconfig /all) to confirm the user’s current IP address and subnet mask.
→ Run (ping <IP>) to verify the conflict by pinging the problematic IP address.
→ Release and renew the IP using (ipconfig /release) and (ipconfig /renew).
→ If fails, escalate to networking</IP>
A user is unable to print. What steps do you take to troubleshoot?
→ Check the printer status: Printer showing as “Online.”
→ Confirm connected to the correct printer: Verify the default printer is selected.
→ Ping the printer’s IP address to check for network connectivity.
→ Check for any stuck print jobs in the print queue and clear if necessary.
→ Restart the printer and try printing again.
→ Check printer drivers: Ensure they are up-to-date.
→ If the printer is still not working, try reinstalling the printer driver.
→ If all else fails, escalate.
A user’s print job is stuck in the queue and will not print. How do you fix it?
→ Cancel the print job from the queue.
→ Restart the print spooler service by typing services.msc and restarting the “Print Spooler” service.
→ Clear any stuck jobs by deleting the files in the C:\Windows\System32\spool\PRINTERS folder.
→ Restart the printer and the user’s computer to refresh the connection.
→ If the issue persists, check for outdated or corrupted drivers and reinstall them.
A user is printing, but the document is coming out blank. What do you check?
→ Check the ink or toner levels and replace if needed.
→ Ensure the correct printer is selected.
→ Check for any paper jams or issues in the printer.
→ Try printing from another application to see if the issue is app-specific.
→ Reinstall the printer driver to ensure it is up-to-date and properly configured.
→ Check the print settings to ensure nothing unusual is selected (e.g., print to PDF instead of printer).
A user reports that an application is not launching. What do you check?
→ Check if the app is running in the background: Use Task Manager to verify if the app is already running.
→ Verify the app is installed correctly: If it’s missing files, try repairing or reinstalling the app.
→ Check for any error messages when launching and use those for troubleshooting.
→ Check system resources: Ensure the system has enough CPU and RAM to run the app.
→ Review Event Viewer logs for any application errors or crashes.
→ If the app still doesn’t open, check for conflicts with antivirus or firewall blocking the app.
A user is experiencing a Blue Screen of Death (BSOD). What steps do you take?
→ Take note of the error code or message on the BSOD.
→ Reboot the system and see if the BSOD persists.
→ Check for recent changes to the system, such as new software or updates.
→ Update drivers (especially graphics, network, and storage drivers).
→ Run a system scan to check for hardware issues using tools like chkdsk.
→ Check the Event Viewer for any system or hardware error logs.
→ If the BSOD continues, boot into Safe Mode and uninstall any recent updates or drivers.
→ If hardware-related, escalate the issue for hardware diagnostics or replacement.
A user says they are getting “not responding” errors when using an application. How do you troubleshoot?
→ Check system resource usage (CPU, memory, disk) using Task Manager to identify any overload.
→ Close any unnecessary applications running in the background.
→ Reboot the computer to clear temporary system processes.
→ Repair or reinstall the application if it’s not responding consistently.
→ Check for updates for both the application and the operating system.
→ Look at Event Viewer logs for application or system errors that could be causing the issue.
→ If the issue is network-related (e.g., cloud app), verify network stability and bandwidth.
A user’s computer is running slowly. What steps do you take to troubleshoot?
→ Check Task Manager for processes that are consuming high amounts of CPU, memory, or disk.
→ End unnecessary processes or applications that may be using up resources.
→ Free up disk space by deleting temporary files and running Disk Cleanup.
→ Check if the system has recently installed updates that could be affecting performance.
→ Run a malware scan to rule out viruses or other malicious software.
→ Check for background processes like updates, backups, or cloud sync apps that might be running.