Author: Bob Lin

Bob Lin, Chicagotech-MVP, MCSE & CNE Data recovery, Windows OS Recovery, Networking, and Computer Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com

Your credentials did not work. Your system administrator doesn’t allow the use of saved the credentials to log on to the remote Computer.

Situation: one of outside client cant login remote Desktop server with this error: Your credentials did not work. Your system administrator doesn’t allow the use of saved the credentials to log on to the remote Computer.

Troubleshooting: 1. Use other computer with the same username doesn’t have this problem.

2. We fixes it by do this:

“The reason why it wasn’t working was because Windows automatically stored the certificate in a “non-trusted” root store. Once it was moved RDP connected without prompting for credentials”

Other suggestions: 1. Change the group policy setting.

2. Security settings.

3. If the client is located the same LAN, change the network profile from public to private.

4. Make sure the company firewall allow remote session.

5. Edit Windows Security Policy.

6. Delete the credentials:

Go to Control Panel -> Credential Manager. You will see three sections:

  1. Windows Credentials
  2. Certificate-Based Credentials
  3. Generic Credentials

Remove the credentials from Windows Credentials and add it to Generic Credentials.

Server locks with Event ID 51: An error was detected on device \Device\Harddisk1\DR23 during a paging operation.

Situation: The client has Hyper-V server running Windows 2016. They can’t login server remotely or from the console. But all VMs run fine and they can access those VMs without any problems.

Troubleshooting: We use another server’s Computer Management and Service to connect to the Host server, every thing is fine except the Event ID: 51
Description:
An error was detected on device \Device\Harddisk1\DR23 during a paging operation.

We find they has external USB connect to the server. Unplugging the external USB and restart the host, everything works.

Can’t login FTP site because of missing port 20 on Windows firewall

Situation: The client setup a FTP site in their Windows 2012 R2. When they try to access the FTP site, and enter their credentials, they can’t access the FTP with timeout message.

Troubleshooting: 1. If we turn Windows Firewall off, it works.

2. The Windows Firewall already has FTP inbound and outbound configured.

3. We fix the problem by adding port 20 in windows firewall.

FTP: 227 Entering Passive Mode (10,0,1,17,149,179)

Situation: The client setup a FTP site on their Windows 2012 R2 server. They can’t access FTP with this message: Make sure you have permission to access that folder. The hadle is invalid.

Details
200 Type set to A
227 Entering Passive Mode (10,0,1,17,149,179)

Troubleshooting: This could be the FTP Firewall Support issue. Go to IIS Manger>Server name, double click on FTP Firewall Support.

Change the Data channel Port Range to 0-0 and remove the External IP addresses of Firewall in it is used for internal only.

An error occurred opening that folder on the FTP Server.

Situation: The client setup a FTP site on their Windows 2012 R2 server. They can’t access FTP using Internet Explorer, Microsoft Edge, and FileZilla and WinSCP. However, they can access FTP using Chrome browser. This is the error message: An error occurred opening that folder on the FTP Server. Make sure you have permission to access that folder. The hadle is invalid.

Troubleshooting: This could be the FTP Firewall Support issue. Go to IIS Manger>Server name, double click on FTP Firewall Support.

Change the Data channel Port Range to 0-0 and remove the External IP addresses of Firewall in it is used for internal only.

Can’t access FTP, SFTP and FTPS server

Here are some cases we have been working on FTP connection problem.

  1. The certificate expired.

2. Make sure you connect to correct FTP site. In this case, the client open the port 21 on Default website. Disable the default website or remove the port 21 from the default website fixes the problem.

3. In other case, The client assign port 21 to ftps site. Refer to above screenshot.

4. Make sure you configure correct authentication and authorization. Also make sure you enter correct username and password. In one of case, the client needs to enter domainname/user to access the FTP site.

System.ComponentModel.Win32Exception: The account name is invalid or does not exist, or the password is invalid

Situation: When running Installutil to install a program as windows service, the client receives this message:

An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: The account name is invalid or does not exist, or the password is invalid for the account name specified

Troubleshooting: You need to use correct login format, for example domain name\admin and correct password.

Add-in doesn’t work in Outlook

Situation: After the user installed Business for Skype on her new computer, the CRM Add-in doesn’t work.

Troubleshooting: we can see the CRM add-in, but whenever we enable it, it doesn’t work and it doesn’t give any error.

After checking the programs and features, we find there are two version of Microsoft Office, Microsoft Office 2016 and Microsoft Office 2016 ProPlus.

Removing all Office and re-installing Office Proplust fixes the problem.