Rdp ошибка 0x3000008

Last Updated on February 14, 2023 by rudyooms

I wasn’t going to write a blog today, but after troubleshooting a weird issue, I still needed to.

This blog will be about the Remote Desktop Client and Windows 11 Insider Previews. Normally I am not blogging about Remote desktops… but this time I needed to.

I will divide this blog into multiple parts

1. The Issue
2. Troubleshooting
3. Solving it
4. The Second Issue

1. The Issue

When migrating to full cloud, sometimes you are still stuck with some old legacy apps. Like I told you in this blog, sometimes publishing an old legacy app as a Remote App for the time being could be a great option.

But today we noticed something weird.

A customer called us about a problem he experienced, so we wanted to be sure our test user was also experiencing the same issue. So we wanted to log in with our test user to check it out ourselves.

But after logging in with our credentials, we ended up with this nice remote desktop screen. It hung on the famous “Configuring Remote Session”

That’s weird because that wasn’t what the customer called us for. That’s weird. So the first place we looked was the Remote Desktop Gateway services, and they were running without any issues, people were still logged on and could still do their job.

2. Troubleshooting

The first thing I wanted to know was if it was an issue on the customer server-side or our own devices. So we did the same tests on some other environments. Almost all of them just worked!…

Luckily we also had a second Remote Desktop Gateway for the customer to test with. When googling “configuring remote session” you will end up with some advice on creating the EnforceChannelbinding

HKLM\Software\Microsoft\Windows NT\CurrentVersion\TerminalServerGateway\Config\Core

Type: REG_DWORD
Name: EnforceChannelBinding
Value: 0 (Decimal)

Or creating the registry value RDGClientTransport on the client (Use RDG-RPC instead of RDG-HTTP)

But none of them worked of course. So let’s move further. We also tested the connection from a separate Windows 11 device, that wasn’t enrolled in Azure Ad/Intune.

You can guess what happened. It worked instantly! No problems whatsoever! So it had to be a setting from Intune, maybe a security baseline went rogue? Luckily there were still 20 new Autopilot enrolled notebooks that needed to be shipped to the client.

So we also tested logging in from one of those devices. As we are almost using the exact same security baselines as our customers, we could rule out the Security Baseline. Again, you can guess what happened! It worked wonderfully!

Okay? So we needed to troubleshoot our own devices, this time … isn’t that a nice Christmas present?

So the first thing we checked was the mstsc.exe version itself because I can still remember some issues with a KB update a long time ago that really messed up the Remote desktop client.

Mmm.. this version was recently updated? I guess that could be the problem here. But still, the question remains why?

So, when you need to troubleshoot the Remote Desktop client, the Terminalservices-ClientActivexCore event log would be the first place to start.

So we opened the event log on our devices and on all devices we noticed these nice 1033 errors

Onderdeelnaam:CClientProxyTransport, :: ‘Gateway Error’ in CClientProxyTransport::SetErrorStatus at 2853 err=[0x800759ec], Foutcode:0x800759EC

Onderdeelnaam:CAAUDPClientChannel, :: ‘SecureTunnel’ in CAAUDPClientChannel::HandleChannelConnect at 958 err=[0x8007274c], Foutcode:0x8007274C

Having errors in that event log doesn’t mean anything good!

3. Solving it

I guess you deserve some background information first. Some time ago we decided to put our devices into the Insider Preview ring of Windows Update for Business, so we would know what would come. Why? So we can be prepared!

So I guess with this Windows 11 Build (22523.1000) we also got the new Remote Desktop Client 10.0.22523.1000 But why was it breaking? After ruling out everything else possible, it suddenly hit me. CAAUDPClientChannel, mmm sounds like UDP…. 🙂

It looks like a UDP issue to me indeed, luckily I can still remember some stuff from the “good old days”. You can define UDP transport settings in the Remote Desktop Gateway configuration shown below

This setting was already enabled for a long time. We decided to turn it off to check out if there was any difference.

Yes, there was… When we turned it off the Remote desktop client could log in immediately. We decided to look further into why UDP suddenly wasn’t working.

After checking out the Firewall and NAT table, we noticed something weird. The NAT rule to forward the UDP traffic was disabled?

When turning it on and enabling the UDP on the rd gateway again it also worked!

So to give a summary: It looks like the latest Remote Desktop Client version 10.0.22523.1000 has some issues determining if the UDP port is enabled and AVAILABLE, maybe it doesn’t check it, and just assumes it works? It also looks like the old version checks if UDP is available, if not it doesn’t use it

4. The Second Issue

I guess Remote Desktop issues and Windows Insider Previews are still occurring. This time we will get a nice 0x3000008 error thrown at us with the latest Windows 11 Insider Preview build: 25295.1000

When looking at the Remote Desktop Gateway, the only thing that we will notice is an event 4625 in the security log mentioning the status: 0xc000035b error

Again, we are looking at the EnforceChannelBinding / LmCompatibility error

0xC000035B when you use LmCompatibility – Windows Server | Microsoft Learn

It’s kinda funny as this error started to occur with the same customer so that enforcechannelbinding was still configured. After some more tests, I decided to just create the RDGClientTransport key with the value 1

Yes!! after closing the mstsc.exe and reopening mstsc.exe again, I could login without any issue!

Conclusion

Troubleshooting our own devices and an old remote desktop gateway, was a nice Christmas present indeed!

«Can’t connect to the Remote Desktop Gateway. Contact your network administrator for assistance. ( Error code: 0x03000008) Trouble is, we’re not using an RD Gateway — there isn’t one configured in my Deployment Properties in Server Manager.

What is error code 0x03000008 in remote desktop?

Error code 0x03000008 occurs when using Remote Desktop

The fourth fix addresses an issue where some Remote Desktop Protocol (RDP) clients that used an absolute URI (instead of a relative URI) were blocked by the Web Application Proxy (WAP) server from connecting to the Remote Desktop Gateway.

How do I fix Remote Desktop Connection error?

To resolve this problem, use the following methods, as appropriate.

Why is my remote desktop not accepting incoming connections?

The most common cause of a failing RDP connection concerns network connectivity issues, for instance, if a firewall is blocking access. You can use ping, a Telnet client, and PsPing from your local machine to check the connectivity to the remote computer. Keep in mind ping won’t work if ICMP is blocked on your network.

How do I reinstall Remote Desktop Connection?

How Do I Reinstall RDP?

Fix Microsoft Remote Desktop Error Code 0X3000064

What is error code 0x3000015 on remote desktop?

Generally, Error code 0x3000015 will appear when we attempt to use RD Client to access or control a remote PC if the WVD settings didn’t turn on or the wrong workspace of the RD Client.

How to fix the remote computer requires network level authentication?

Let’s take a look at how you can do this:

How do I fix Remote Desktop Services in Windows 10?

Step 1: Open Settings and then click Network & Internet. Step 2: Go to the Status tab and then click Change connection properties in the right panel. Step 3: Choose Private under Network profile. Step 4: Retry to connect the remote computer and then see if the error still persists.

How do I reset my computer Remote Desktop?

Restart a computer

How do I manually connect to a remote computer?

On your local Windows PC: In the search box on the taskbar, type Remote Desktop Connection, and then select Remote Desktop Connection. In Remote Desktop Connection, type the name of the PC you want to connect to (from Step 1), and then select Connect.

How do I make a remote device accept my connection?

The “Remote device or resource won’t accept the connection” can be resolved using several methods. These methods include resetting internet explorer settings, disabling proxy settings, disabling firewalls, and updating group policies.

How do I handle unable to connect to the remote server?

Solution 1: Restart Driver Easy The problem can be caused by temporary disconnection from the server. When you run into this error, you can try to restart Driver Easy and see if the problem resolves. Solution 2: Ping Checking 1. Press Win+R (Windows key and R key) combination to open the Run dialog box.

What might mean that Remote Desktop can t connect to the remote computer?

Remote Desktop can’t connect to the remote computer for one of these reasons: Remote access to the server is not enabled. The remote computer is turned off. The remote computer is not available on the network.

What is error code 0x0 on remote desktop?

Error code 0x0 0x0 is a generic error that appears on Windows 11 when the system fails to access a certain file or encounters a problem in accessing or running one of its installed programs. It can also occur if the computer runs out of memory, has an issue with its hard drive, or has another hardware problem.

How do I test my remote desktop connection?

Open a command prompt Type in «telnet » and press enter. For example, we would type “telnet 192.168. 8.1 3389” If a blank screen appears then the port is open, and the test is successful.

Does Windows 10 Home no longer support remote desktop?

How to Fix: Your Home Edition of Windows 11 (10) Does Not Support Remote Desktop. Since your Home Edition of Windows 11/10 doesn’t support Remote Desktop, you can upgrade Home to Pro to enable Remote Desktop or just switch to third-party free remote desktop software.

What services need to be running for remote desktop Windows 10?

To work with Remote Desktop Services, the PCs must be running a Windows operating system, have the RDP display protocol installed, and have a live network connection using TCP/IP and a valid IP address.

How to restart remote desktop Service remotely Windows 10?

Search for Remote Desktop Services. 4. Right-click on the Remote Desktop Services, and you will find an option to Restart it. Click on Restart, and it will restart your service.

How to enable Remote Desktop without Network Level Authentication?

Navigate to Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Security. Enable Require use of specific security layer for remote (RDP) connections and select RDP as Security Layer.

How do I connect to Remote Desktop with Network Level Authentication?

Remote Desktop Settings

The first option is to go to Settings in your Start menu, and choose Remote Desktop. Now click Enable Remote Desktop ON, and Confirm with the pop up window. Click into the Advanced Settings, and select the option that says Require computers to use Network Level Authentication to connect.

What is the meaning of unable to connect to the remote server?

This usually means that there is a network or server issue occurring at this moment. Network troubleshooting can help us identify if there is an issue with the connection. Run the following commands to test the network: On your computer’s task bar, click on the Start button.

How would you troubleshoot a server you can t connect to?

What To Do When You Cannot Connect To The Company Server

What is the command to connect remote server?

On the client computer, search for Command Prompt to open it, then type in “mstsc” and press Enter to invoke the Remote Desktop Connection window. Step 2. Type in the IP address and username of the host computer, and then click Connect. Now you may grasp how to remotely access another computer using CMD.