Windows 10: Windows 10 Pro - can't connect establish a remote TCP/IP session using SSH or RDP, syn ack...

Cannot connect to a remote server using ssh or RDP using Windows 10 Pro, even with the FW off. I verified server receives the SYN and responds a SYN ACK but that apparently is not received by my WIn 10 PC. and the connection times out. An SSH connection using another device ssh client from the same location connects properly. I have been working on this for over 48 hours now and am very experienced telecomms. I saw similar problems reported in this forum but haven't seen an acknowledgement of the problem or a resolution. I would greatly appreciate any help you can give.


zapo-25

:)

 

Windows 10 drops incoming TCP SYN packet for no reason

I am running some services on my Windows 10 laptop behind a NAT server (I have set port forwarding rules). I am encountering the issue that Windows drops incoming TCP SYN packet from some IP addresses for
no reason. To be specific, currently, only the laptop itself and connected (via SSH) remote servers are whitelisted by some unknown firewall-like thing. According to my examination, the reason seems to be NOT one of the following:

1. Built-in firewall, which is the only firewall on my system, is blocking incoming connection (because I have whitelisted all the services/applications, and even if I turn off the firewall, nothing is changed)
2. The upstream is blocking incoming connection (because the RaspberryPi under the same network does not have the same issue)

What's more, I can confirm that the link is not broken because I did see the initial SYN packet and some retransmitted SYN packet of the incoming connection in Wireshark. However, I
did not see any SYN-ACK packet in response to those SYN packets in all network interfaces. It seems like the connection event did not reach the application layer.



Things got even more weirder after last time I booted into safe mode to see if the issue remains unresolved. The issue did remain unresolved in safe mode, so I rebooted the system without any changes to firewall
rules or anything. Magically, after this reboot, the problem disappeared for no reason. Everything was working great since then, until I rebooted, again. Now Windows (I assume that it is Windows) is again blocking incoming TCP connections.



Can anyone help? Really sad

 

RDP not allowing remote connection

I had it working perfectly fine the other day but I logged into my server, removed a open port and both computer quit.

I run the computers with the firewall off, I see no point in them being on, it's a windows firewall a hacker will know how to get around so fire wall is OFF.

Ports are 9000 for server and 3390 for htpc

ip:9000
ip:3390

This does not work from a linux workstation using 'Remote Desktop Client'

It does not work from mac RDP
It does not work from windows RDP
And it does not work from my iphone.

I know it's enabled as I can RDP into the computers at my home (except htpc at the moment, I think that one needs restarted)

Ports are open, both tcp / udp ports are open using the internal server IP wich is MAC assigned by the router. Server - 10.0.1.2 - 9000
And same thing for the htpc - 10.0.1.8 - 3390

Besides the obvious of firewall, ports, and 'remote connection enabled' any ideas?

 

[bug] Windows 10 Pro remote desktop session logs off

I have tried closing RDP on Windows 10 virtual machine, and I cannot duplicate your problem.

Perhaps the difference is that I have applied
this registry fix because I was getting the message of "the connection cannot proceed because authentication is not enabled" :

Answer from: Windows 10 remote desktop session logs off