Author: Bob Lin

Situation: The client setup FTP on their Windows 2012 R2 server. Internet Browser access the FTP server without any issues. However, FillZilla can’t establish the connection with this error: Could not connect to server.

Troubleshooting: 1. Make sure the user has correct password.

2. Make sure the user has permissions to access the FTP folder.

3. Try change encryption to “only use plain FTP” and logon type “Normal” under File>Site Manager.

4. try this settings:

• Open Filezilla, go to Edit -> Settings
• Click on Connection -> FTP: Choose Active
• Click on Connection -> FTP -> Active Mode: Select “Ask your operating system for the external IP address”
• Click on Connection -> FTP -> Passive Mode: Choose Fall Back to Active Mode
• Press OK.

5. Try to use the IP address instead of the DDNS.

6. Go to File > Site Manager > Select your site > Transfer Settings, change the Transfer mode from Default to Active or Passive.

7. Make sure you can telnet port 21.

8. Go to File > Site Manager, change the Encryption to Only use plaint FTP (insecure).

Situation: The client setup FTP on their Windows 2012 R2 server. Internet Browser access the FTP server without any issues. However, FillZilla can’t establish the connection with this error: Failed to retrieve directory listing.

Troubleshooting: 1. Make sure the user has correct password.

2. Make sure the user has permissions to access the FTP folder.

3. Try change encryption to “only use plain FTP” and logon type “Normal” under File>Site Manager.

4. try this settings:

• Open Filezilla, go to Edit -> Settings
• Click on Connection -> FTP: Choose Active
• Click on Connection -> FTP -> Active Mode: Select “Ask your operating system for the external IP address”
• Click on Connection -> FTP -> Passive Mode: Choose Fall Back to Active Mode
• Press OK.

5. Try to use the IP address instead of the DDNS.

6. o to File > Site Manager > Select your site > Transfer Settings, change the Trasfer mode from Default to Active or Passive.

Situation: The client has VM running Windows 2012 R2 on windows 2012 R2 Hyper-V. They can’t login the VM with “Apply Computer settings” screen forever.

Troubleshooting: 1. Turn off and turn on VM doesn’t fix the problem.

2. Running Safe mode has the same problem.

3. We find the host has a Windows update. Installing and restarting the host fixes the problem.

4. The problem we had is the server Windows update is default settings Install updates automatically. Whenever major windows updates installed, the RD server has a problem and the restating takes along time with “Apply Computer settings”. The resolution is change the Windows update default settings to Check for updates but let me choose whether to download and install them.

Situation: The client has VM running Windows 2012 R2 on windows 2012 R2 Hyper-V. They can’t login the VM with “Please wait ” screen.

Troubleshooting: 1. Turn off and turn on VM doesn’t fix the problem.

2. Running Safe mode has the same problem.

3. We find the host has a Windows update. Installing and restarting the host fixes the problem.

4. The problem we had is the server Windows update is default settings Install updates automatically. Whenever major windows updates installed, the RD server has a problem and the restating takes along time with “Apply Computer settings”. The resolution is change the Windows update default settings to Check for updates but let me choose whether to download and install them.

Situation: The client try to use robocopy to copy files and folders with security from one server and anew server. It process for a few minutes. some folders and files miss, and then no one can access the server. This is the commond:

robocopy \\comm\TS_Share C:\ TS_Share /MIR /COPYALL /DCOPY:T /R:1 /W:1 /NP /TEE

Troubleshooting: There is the space between C:\ and TS_Share. That curses the problem and override some system files.

Situation: The client has Palo Alto Firewall as VPN. One of users can’t establish the VPN. it shows “Still working”.

Troubleshooting: 1. It could be the DNS issue. Make sure the VPN hostname is correct. For a test, use IP address instead of DDNS.

2. Repair GlobalProtect in Control Panel. To do that, type Control in the search bar. Click on Control Panel to open it.

In the Control Panel, click on Program and Features.

In Program and Features, right click on GloablProtect and select Repair.

3. Make sure PanGPS service is running

4. Uninstall and re-install GloablProtect.

Situation: when the client setup Synology SNA notification using Office 365 account, they receive 535 5.7.3 authentication unsuccessful.

Troubleshooting: 1. Make sure you use correct SMTP server info:

Server: outlook.office365.com

Port: 993

Encryption: SSL/TLS

or

Server: smtp.office365.com

Port: 587

Encryption: STARTTLS

2. Make sure account credential are correct.

3. When filling out the Username, put in the full email address.

4. In out case, we fix the problem by switching Service Provider from SMTP Server to Outlook. Please refer to thispost:

How to configure Notification on Synology SAN

Situation: The client installs Veeam Backup and Replication Community Edition. Backing up VM works fine. However, it gets this error message when backing up SQL.

10/1/2019 11:39:33 AM :: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Job failed (‘Checkpoint operation for ‘SQLServer07’ failed. (Virtual machine ID 76714D70-9FF7-4F19-902B-0CFF030D7FAC)

‘SQLServer07′ could not initiate a checkpoint operation: %%2147754996 (0x800423F4). (Virtual machine ID 76714D70-9FF7-4F19-902B-0CFF030D7FAC)’). Error code: ‘32768’.
Failed to create VM recovery snapshot, VM ID ‘76714d70-9ff7-4f19-902b-0cff030d7fac’.

Troubleshooting: Go to VM Settings. Navigate to Checkpoints, change the Production checkpoints to Standard checkpoint.

Situation: The client just created a distribution group email in Office 365. The members of the group send and receive email without any problems. However, other company users can’t send the email to the group with this message: “The group sales@chicagotech.net isn’t set up to receive messages from info@chicagotech.net”.

Troubleshooting: most users were migrated from their Exchange server. This group was created in Office 365. If you check the the Group Type and Status in Office 365, you can see the different.

Even their email addresses are in the same domain name, but the group types are different. We fixed it by enabling “Let people outside the organization send email to the group” as shown below.

Situation: The client a couple hundred users access their system remotely using RDP. Some remote users complaint that they keep losing the connections.

Troubleshooting: We suspect it is RD license issue. When Login RD license Manager, we do see the yellow !. If we click on Review Configuration, it shows this error: “This system cannot determine if the license server is registered as service connection point(SCP) in Active Dirctory Domain Services(AD DS) because the AD cannot be contacted”.

1. Go to configuration or Change Scope to fix any issues.
2. Restart the RD license service.
3. Re-install the RD license.