SwiftOnSecurity on Nostr: [@jpsays]( ) Any insights on same subnet RDP inbound 3389 to a desktop listening for ...
[@jpsays](
https://mastodon.social/@jpsays ) Any insights on same subnet RDP inbound 3389 to a desktop listening for TermServ would not respond to SYN, and also not show up in the pfirewall.log? Wireshark sees inbound SYN and remote retransmits. No connection security rules configured anymore either side anymore. What layer could be borking it? Reverse RDP direction does work
Published at
2026-09-03 21:02:49 UTCEvent JSON
{
"id": "eb70dde1351e1b54c80c1c1bd8753cc35ae069137bed6cec1314749d8d56b871",
"pubkey": "598e0e964aab08bcf4584071bb0eabc588ed39ba89390665c5cedea83a69b262",
"created_at": 1788469369,
"kind": 1,
"tags": [
[
"proxy",
"https://infosec.exchange/@SwiftOnSecurity/117209128613669945",
"web"
],
[
"proxy",
"https://infosec.exchange/users/SwiftOnSecurity/statuses/117209128613669945",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://infosec.exchange/users/SwiftOnSecurity/statuses/117209128613669945",
"pink.momostr"
],
[
"-"
]
],
"content": "[@jpsays](https://mastodon.social/@jpsays ) Any insights on same subnet RDP inbound 3389 to a desktop listening for TermServ would not respond to SYN, and also not show up in the pfirewall.log? Wireshark sees inbound SYN and remote retransmits. No connection security rules configured anymore either side anymore. What layer could be borking it? Reverse RDP direction does work",
"sig": "15ef03faaccee600aba8c6c964759ae91ed7009faa7fd136d80753a7ab77e46ecb775ce5e0cdcf4dc40732ab578d0803bd05f6d8865a50ca176194048e10820c"
}
