Situation: The client has some servers on AWS which connecting to the LAN over site to site VPN. Today, two of servers on AWS can’t access one of LAN servers.
Troubleshooting: 1. Ping LAN server IP doesn’t work.
2. Paloalto firewall Monitor shows sending is fine. However, Packet received is 0.
3. AWS support confirm they don’t block access the LAN.
4. Finally, we find the server has a security software that blocks the AWS servers. Unblocking fixes the problem.
Situation: The client uses Malwarebytes cloud. Malwarebytes shows some computers need scan. They would like to know how to fix it. Resolution 1:
Make sure Malwarebytes services are running.
2) Make sure both Malwarebytes services are running. If not, please start them.
Resolution 2: If there is a Windows Update holding, please install and restart the computer.
Resolution 3: Re-install the Malwarebytes agent.
Situation: The client setup Windows update to be checked only.
However, sometimes, the Update installs automatically and requires to restart.
Passible cause: After some Windows updates, the Settings change to the default: Install update automatically (recommended).
Situation: The client use DHCP Reservation to assignee IP address to each printer. Today, one of their printers (HP M608) doesn’t work. Can’t ping it by IP also.
Troubleshooting: 1. The DHCP Reservation shows correct configuration and the printer should be assigned 10.0.220.12.
However, printing configuration page shows the IP address is 10.0.200.44.
2. Double-check the hostname and Mac address are correct.
3. We fix the problem by changing to Statics IP address still using 10.0.220.12.
Situation: The client has PA-850 firewall running GloableProtect for VPN connection. After they changed the DNS by going to Network>Gloableprotect>Gateway>Agent and then Network services,
Some VPN client take the change but not all. Some users still use the old DNS server.
Troubleshooting: You also need to change the DNS server under Client Settings>Network Services.
Please refer to this post for more details: How to change DNS settings for PA Firewall GloablProetc
Situation: The user has a good Internet connection and enter the correct credentails. However, she has a problem to run Microsoft teams.
Resolution 1: Logoff and re-login Teams.
Resolution 2: Make sure not Windows Update pennding. If so, please install the update wand restart the computer.
Resolution 3: Make sure your date and time are set up correctly.
Resolution 4: Clear Teams cache in %appdata%\Microsoft\Teams
Resolution 5: If it is offline, switch to Available.
Situation: The client has Microsoft System center. They receive this notification: System Center Management Health Service Unable to Process New Configuration: The System Center Management Health Service 2614488B-0285-1500-4635-BBE41B968D24 running on host Process04.chicagotech.net and serving management group with id {DF8F1BA9-B466-BD6C-DD3F-1C36113D82E7} is not healthy. System Center Management Health Service is unable to process or load configuration.
Resolution 1: Enable repair the agent.
| Navigate to the Administration space |
| Click the Agent Managed view under Device Management |
| In the result pane, select one or more agents |
| Click Repair… in the Actions pane |
| You can use the default action account or supply alternate credentials |
| Click the Repair button |
This should repair the agent and force it to request its new configuration.
Resolution 2: Restart the Agent service.
Resolution 3: Re-install the Agent.
Situation: the client WFH and access company private websites through VPN. Now, he can’t access some of websites inside.
Troubleshooting: 1. He can’t use Microsoft Edge and google Chrome to access those websites. However Firefox works fine.
2. He has clear the cache on both Edge and Chrome.
3, finally, we find IT enabled DNS over HTTPs recently on their firewall. Disable DoH fixes the problem.
Situation: The client has a Dell PowerEdge 2950 server running Windows 2012 R2. The server has a problem to start with this error: E1000 Failsafe, Call Support E1215 1.8V.
Troubleshooting: Online suggestion:
The issue you are seeing is due to a problem with either the motherboard, riser, or a PCI card in that riser. To start troubleshooting which one, take the server down to the minimum hardware required to POST. That is removing everything in the server but the folowing;
We fixed the problem by reset the memory.