Urgent Help Required - Remote Desktop connection to companies network does not work!

I get a response from : nslookup rdgateway-r1.wvd.microsoft.com
But I get "not reachable" from :  ping rdgateway-r1.wvd.microsoft.com

Are you wishing to rdp direct from your VM connection to rdgateway-r1.wvd.microsoft.com ?
or do you first connect a office VPN & then rdp ?

Remove router connect laptop  to hub in modem mode power off for 2 mins

also change DNS to 1.1.1.1 , 8.8.8.8 or 9.9.9.9

A using a Public DNS does not make rdgateway-r1.wvd.microsoft.com reachable.

I forced the dns change in my router before and it didnt fix the issue

Ping  rdgateway-r1.wvd.microsoft.com  from the link below ... it sure looks to be offline to me.

https://www.host-tracker.com/en/ic/ping-test 

I am out of ideas.

Below is via Planet VPN with Netherlands selected as the exit point :

Yes VM and EE have a routing problem as O2 is fine to port 3389

O2

C:\temp>tracetcp rdgateway-r1.wvd.microsoft.com:3389

Tracing route to 51.140.57.159 on port 3389

Over a maximum of 30 hops.

1 2 ms 2 ms 3 ms 192.168.255.247

2 24 ms 25 ms 61 ms 192.168.8.1

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 Destination Reached in 61 ms. Connection established to 51.140.57.159

Trace Complete.

VM

C:\tracetcp_v1.0.3>tracetcp 51.140.57.159:3389

Tracing route to 51.140.57.159 on port 3389

Over a maximum of 30 hops.

1 6 ms 10 ms 11 ms 10.112.32.133

2 12 ms 11 ms 11 ms 80.1.81.185 [basl-core-2b-ae63-650.network.virginmedia.net]

3 * * * Request timed out.

4 20 ms 18 ms 17 ms 213.105.11.198 [tcl5-ic-7-ae0-0.network.virginmedia.net]

5 18 ms 16 ms 15 ms 207.46.219.212 [ae65-0.lts-96cbe-1a.ntwk.msn.net]

6 19 ms 18 ms 20 ms 104.44.239.101 [ae25-0.icr01.lon22.ntwk.msn.net]

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

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 * * * Request timed out.

30 * * * Request timed out.

Trace Complete.

EE

C:\temp>tracetcp 51.140.57.159:3389

Tracing route to 51.140.57.159 on port 3389

Over a maximum of 30 hops.

1 3 ms 4 ms 4 ms 192.168.255.247

2 3 ms 2 ms 12 ms 10.112.227.1

3 44 ms 69 ms 41 ms 10.247.176.102

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 126 ms 63 ms 45 ms 109.249.132.12

8 66 ms 47 ms 28 ms 62.172.103.199 [peer3-et4-1-6.slough.ukcore.bt.net]

9 63 ms 80 ms 49 ms 104.44.37.125 [ae66-0.ier04.lon04.ntwk.msn.net]

10 26 ms 48 ms 73 ms 104.44.55.180 [ae29-0.icr04.lon22.ntwk.msn.net]

11 * * * Request timed out.

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

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 * * * Request timed out.

30 * * * Request timed out.

Trace Complete.

It is up to the employer to solve why there are so many routes that fail to gain access.

Some jockey in the IT team will have set the profile for what can and what can not route to this host.