Here are some updates to the problem !
81568da1-b61c-43d3-bcd0-3739283624c3
HELP, SOS ... I need help very much !!!!!!!
Remote Desktop problems after update ?
KeldSor
396
Reputation points
To simplify as much as possible:
I have3 machines newly RE-installed
ALL with Windows 10 PRO Machine:
A) version 1903 and 2 shares, the C- and D-Hdrive
B) version 1909 and 1 share, the C-HDrive
C) version 1903 and 1 share, the C-HDrive
I'm logged on to all of them with my MS-account.
ALL machines can acces the SHARES on ALL the other machines - it is all combinations works well !
BUT when it comes to access via Remote Desktop, Oh, my ...
Machines B and C can NOT access A, but A can access BOTH B and C by Remote Desktop !
I've had this problem EVERY TIME I had to upgrade to a new version of Windows - lastly from 1803 to this crap 1903 and 1909.
On one of them I even updated to 2004 and it was even WORSE so I downgraded again.
When I say "newly" installed I mean resetting Windows with clearing the whole disk - I beleave it's including formating too !
I have checked ALL the 'normal on user or super user level' procedures concerning Remote Desktop - nothing seems to work here !
... and remember it worked NICELY FOR YEARS before the update with 1803 !!!!!
This problem is driving me CRAZY !
What is wrong here !
Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
-
KeldSor 396 Reputation points
2020-10-05T08:06:32.513+00:00 When I try to make the connection it responds with a Msgbox with 3 possible causes - translated from danish:
1) Remote access is not activated ----------------------------------> it IS, I've tested severel times !
2) Remote computer is OFF -----------------------------------------> not at all !
3) Remote computer is not accessable on the network ------------> it IS because I can get access to the shares !!!!!!!
-
KeldSor 396 Reputation points
2020-10-09T13:23:15.01+00:00 And B and C in fact CAN access each other via Remote Desktop.
We HAVE TO use a notation like Ip(A) as a function that represents the ip-address of machine A - because the IP-addresses changes from day to day !
PINGing:
From B and C, I can PING A and get an answer
From A I can PING both B and C and get an answerLISTENING:
On A the
telnet Ip(A) 3389
will NOT make contact – error message as in earlier postings.
That eventhough this
REG QUERY "HKLM\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v PortNumber
reports back: PortNumber REG_DWORD 0xd3dB is listening at port 3389 – I get this “black screen” when telnet IP(B) 3389
C is listening at port 3389 – I get this “black screen” when telnet IP(C) 3389Firewall at A allows “Remote Desktop” to pass trough.
SOMEBODY HELP ... it's getting very bad here because of this problem !
Sign in to comment
2 answers
Sort by: Most helpful
-
KeldSor 396 Reputation points
2020-10-10T11:02:37.387+00:00 HELP; HELP ... someone must have an idea to a solution !