Use these steps when a Remote Desktop client can't connect to a remote desktop but doesn't provide messages or other symptoms that would help identify the cause.
Check the status of the RDP protocol
Clone Repository to Access GitLab via SourceTree. Go into your projects in your GitLab. Copy the SSH URL. In SourceTree, click on Clone. Paste the repository URL into Source Path. Click on Clone, you have successfully connected GitLab with SourceTree. Now you are able to pull and push your code to GitLab with SourceTree. SourceTree is useless. Works only one time, after that won't show the repositories on own server bitbucket (who would ever share own code with 3rd party, no idea, but seems like most of people using it with BitBucker cloud). Don't bother, never use it. I had the same issue few months ago, and now after few months, they have failed to repair. 2018-12-31 SRCTREE-5905 VSTS does not support personal repositories, so prevent Sourcetree offering to create one; SRCTREE-5909 Add syntax highlighting to diffs; SRCTREE-5910 Fix refreshing accesstokens for Bitbucket accounts; SRCTREE-5912 Automatically switch to the remote repositories listing view if repository creation failed to clone locally.
Check the status of the RDP protocol on a local computer
To check and change the status of the RDP protocol on a local computer, see How to enable Remote Desktop.
Note
If the remote desktop options are not available, see Check whether a Group Policy Object is blocking RDP.
Check the status of the RDP protocol on a remote computer
Important
Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.
To check and change the status of the RDP protocol on a remote computer, use a network registry connection:
Check whether a Group Policy Object (GPO) is blocking RDP on a local computer
If you can't turn on RDP in the user interface or the value of fDenyTSConnections reverts to 1 after you've changed it, a GPO may be overriding the computer-level settings.
To check the group policy configuration on a local computer, open a Command Prompt window as an administrator, and enter the following command:
Refreshing Remote Repositories Failed Sourcetree For Mac Free
After this command finishes, open gpresult.html. In Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostConnections, find the Allow users to connect remotely by using Remote Desktop Services policy.
Check whether a GPO is blocking RDP on a remote computer
To check the Group Policy configuration on a remote computer, the command is almost the same as for a local computer:
The file that this command produces (gpresult-<computer name>.html) uses the same information format as the local computer version (gpresult.html) uses.
Modifying a blocking GPO
You can modify these settings in the Group Policy Object Editor (GPE) and Group Policy Management Console (GPM). For more information about how to use Group Policy, see Advanced Group Policy Management.
To modify the blocking policy, use one of the following methods:
Check the status of the RDP services
On both the local (client) computer and the remote (target) computer, the following services should be running:
You can use the Services MMC snap-in to manage the services locally or remotely. You can also use PowerShell to manage the services locally or remotely (if the remote computer is configured to accept remote PowerShell cmdlets).
On either computer, if one or both services are not running, start them.
Note
If you start the Remote Desktop Services service, click Yes to automatically restart the Remote Desktop Services UserMode Port Redirector service.
Check that the RDP listener is functioning
Important
Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.
Check the status of the RDP listenerRefreshed
For this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work both locally and remotely.
Check the status of the RDP self-signed certificateRefreshing Remote Repositories Failed Sourcetree For Mac Download
Check the permissions of the MachineKeys folder
Check the RDP listener port
On both the local (client) computer and the remote (target) computer, the RDP listener should be listening on port 3389. No other applications should be using this port.
Important
Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.
To check or change the RDP port, use the Registry Editor:
Check that another application isn't trying to use the same port
For this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work locally and remotely.
Check whether a firewall is blocking the RDP port
Use the psping tool to test whether you can reach the affected computer by using port 3389.
Had this issue for a little while, probably since 2.5.x of the app. If I go to 'Show Remote Hosted Repositories', I am presented with the error as shown in the screenshot. I get the error even if I don't have an account added in SourceTree!
Thing is, I can see my remote repositories okay as when I have an account present, I can double tap on it in this window to get the 'clone a repository' popover, entering the correct Source URL. So SourceTree can go via the URL and grab the repository. It just refuses to show me the valid ones I can clone in the window, instead presenting this very odd error.
Host is a Bitbucket Server, Auth Type Basic, via HTTPS protocol.
Attachments
Comments are closed.
|