Author: Bob Lin

There are several reasons why you may be receiving pop-up messages on your Windows 10 computer:

1. System notifications: These are notifications from the operating system, such as low battery warnings or notifications about updates.
2. Anti-virus software alerts: Your anti-virus software may send pop-up messages to alert you about potential threats on your computer.

1. Application notifications: Applications on your computer may also send pop-up messages to provide information or alert you to a new message, update, or other event.
2. Adware or malware: Pop-up messages may also be a result of adware or malware on your computer. These malicious programs can cause pop-ups and other unwanted behavior.

If you want to stop the pop-up messages, you can try the following solutions:

1. Disable system notifications: You can go to the “Settings” app and then to “System,” “Notifications & Actions,” and turn off the notifications you don’t want to see.
2. Disable anti-virus alerts: You can go to the settings or preferences of your anti-virus software and turn off the pop-up alerts.
3. Disable application notifications: You can go to the settings or preferences of the application that is sending the pop-up messages and turn off the notifications.
4. Scan for malware: If you suspect that your pop-up messages are a result of malware, you can run a full scan of your computer using your anti-virus software to detect and remove any threats.

Situation: The client has a Windows Server running as VPN server. Some users can’t establish the VPN with this Error Description: 809: The network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (e.g, firewalls, NAT, routers, etc) between your computer and the remote server is not configured to allow VPN connections. Please contact your Administrator or your service provider to determine which device may be causing the problem.

Troubleshooting: As the popup error message mentions that “The network connection between your computer and the VPN server could not be established because the remote server is not responding”.

1. On the client site, check the VPN traffics and make sure there is not blocked UDP port 500, UDP port 4500 on the firewall. For example, port 500, UDP port 4500 are allowed.

2. On the server site, also make sure the VPN traffics are coming or not denied.

3. Also on the client site, trace route to check any timeout at end point.

4. Check the logs on server and client

Resolutions:

1. Check your network settings: Ensure that the network settings on your device are properly configured and that you have a stable internet connection.
2. Restart your device and the VPN server: Try restarting your device and the VPN server to see if this resolves the issue.
3. Disable third-party security software: Some third-party security software, such as antivirus or firewall programs, can interfere with VPN connections. Temporarily disabling these programs may help resolve the error.
4. Verify the VPN server address: Make sure that you are using the correct VPN server address and that it is reachable from your device.
5. Update your VPN client: Check to see if there is an updated version of your VPN client available, and if so, install it.
6. Contact your VPN provider: If none of the above steps help, contact your VPN provider for further assistance. They will be able to provide you with more specific information about the cause of the error and how to resolve it.

This error message occurs when trying to edit an attribute in the Active Directory Users and Computers snap-in on a Microsoft Windows Server. It means that the editor does not have a registered handler for the type of attribute you are trying to edit.

To resolve this issue, you can try the following steps:

1. Make sure that you have the necessary permissions to edit the attribute.
2. Check if the required schema extension has been made to support the attribute.
3. If the schema extension is not present, you may need to extend the schema and register the attribute with the proper handler.
4. If the schema extension is present, try restarting the Active Directory service or the entire server.

Resolution 2: You may need to add the attributes in order to be able to update them. This PowerShell Command will allow you to add the attributes and may prevent the error you’re seeing and therefore prevent you having to recreate the whole directory:

Set-ADGroup -Identity “test_authOrig” -Server dc.hepek.lab -Add @{authOrig=@(‘CN=TestUser,OU=User,OU=OfficeM,OU=HQ,DC=hepek,DC=lab’)}

Situation: The client has a new Comcast Business router. Wired connection works fine. However, WiFi users can’t use some apps such as Teams, Outlook. However, browsing website is no issues.

Situation: The client uses RSG VPN (in Azure) to establish the connection to the customer. It works for all office and home users except one of office users.

Troubleshooting: 1. We monitor the Palo Alto Firewall in the office, and it shows all traffics are allowed.

2. Trace router confirms it is not our system issues.

C:\Users\blin>tracert 70.37.x.x

Tracing route to 70.37.x.x over a maximum of 30 hops

1 51 ms <1 ms <1 ms www.webgui.nokiawifi.com [192.168.12.1]
2 1 ms <1 ms <1 ms 192.0.0.1
3 * 18 ms * 192.0.0.1
4 * 20 ms 18 ms 192.0.0.1
5 * * 24 ms 192.0.0.1
6 72 ms * * 192.0.0.1
7 51 ms 37 ms 38 ms 192.0.0.1
8 59 ms 37 ms 37 ms 10.165.200.189
9 60 ms 33 ms * 10.164.160.121
10 * 35 ms * 10.164.178.151
11 61 ms 37 ms 37 ms chi-8075.msn.net [208.115.136.27]
12 56 ms 28 ms 23 ms ae36-0.icr02.ch4.ntwk.msn.net [104.44.237.23]
13 70 ms 60 ms 96 ms be-102-0.ibr01.ch4.ntwk.msn.net [104.44.11.3]
14 93 ms * 105 ms be-8-0.ibr03.dsm05.ntwk.msn.net [104.44.28.220]
15 95 ms 83 ms 68 ms be-10-0.ibr01.sn6.ntwk.msn.net [104.44.29.30]
16 64 ms 75 ms 77 ms ae104-0.icr03.sn6.ntwk.msn.net [104.44.11.85]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.

22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 70 ms 76 ms 75 ms 70.37.x.x

It seems to us that the traffics reach to the end point. We call Azure support, and they fix the problem.

1. Open the Server Manager on the remaining server.
2. Click on “Remote Desktop Services” in the left-hand menu.
3. In the center pane, click on “Collections.”
4. Right-click on the collection that is having issues and select “Edit Properties.”
5. In the “Edit Collection Properties” window, go to the “RD Session Host” tab.
6. Make sure that the correct server is listed in the “Server name” field. If not, select the correct server and click “OK.”
7. Restart the Remote Desktop Services on the server by running the following command in an elevated Command Prompt: “net stop termservice & net start termservice.”
8. Test the Remote Desktop Services tools to ensure that they are functioning properly.

The issue with WeChat sound not going through Phone Link could be due to a few factors:

1. Poor network connection: Make sure your phone and the linked device have a stable internet connection.
2. Volume settings: Check the volume settings on both your phone and the linked device to make sure the sound is not muted or set too low.
3. Incorrect settings: Verify that the audio output is set to Phone Link on both devices.
4. Compatibility issues: Ensure that both devices support WeChat audio transmission through Phone Link.

If you are experiencing sound issues while recording WeChat using OBS Studio, here are a few things you can try:

1. Check the audio sources: In OBS Studio, go to the “Sources” panel and make sure that the audio source(s) you want to record are selected and properly configured.
2. Update your sound drivers: Make sure you have the latest sound drivers installed on your computer.
3. Check audio settings in Windows: Go to the sound settings in Windows and make sure the audio output is set to your computer speakers or headphones.
4. Disable exclusive control: Some sound drivers might have an “Exclusive Mode” option that can prevent other applications from accessing the audio device. If this is the case, try disabling this option.
5. Try a different recording software: If the issue persists, you may want to try a different recording software, such as Bandicam or Camtasia, to see if the problem is specific to OBS Studio.

If you are experiencing sound issues while recording WeChat using Bandicam, here are a few things you can try:

1. Check the audio settings in Bandicam: Ensure that the audio recording source is set to “System Sound.”
2. Check the sound settings in Windows: Go to the sound settings in Windows and make sure the audio output is set to your computer speakers or headphones.
3. Update Bandicam and your sound drivers: Make sure you have the latest version of Bandicam and the latest sound drivers installed on your computer.
4. Try a different recording software: If the issue persists, you may want to try a different recording software, such as OBS Studio or Camtasia, to see if the problem is specific to Bandicam.

Situation: The user can’t login his Teams with this message: You cannot access this right now with error code 53003.

Troubleshooting:

1. Sign in to the Azure portal as a member of Administrators
2. Browse to Azure Active Directory.

3. Sign-ins logs under Monitoring.

4. Find the event for the sign-in to review. Add or remove filters and columns to filter out unnecessary information. Foor example user Sean.

5. You can have these information: Status, IP address, Location and Conditional Access. If you double click on it, you can have more info.