Hello @Farber Frederick, FG-AM-5
tcping64.exe isn't a built-in Windows/Microsoft utility, so we'd need the exact error message to determine why the command is failing.
If the objective is simply to verify whether the RDP endpoint is reachable on TCP 3389, Windows already provides a supported PowerShell test:
Test-NetConnection login.workspace.bmw -Port 3389
Check the result for:
TcpTestSucceeded : True
If it returns False, first verify that the hostname resolves correctly:
Resolve-DnsName login.workspace.bmw
A failed TCP test can be caused by DNS resolution, firewall/proxy restrictions, routing, VPN/corporate network policy, or the destination not listening on TCP 3389. Microsoft documents Test-NetConnection specifically for connection diagnostics, including TCP port testing.
Reference: Microsoft - Test-NetConnection documentation
Please post the exact error/output from tcping64.exe or Test-NetConnection. That will help determine whether this is DNS, connectivity, port blocking, or an issue with the third-party tcping64.exe utility itself.
Help make this community better for everyone: if this answer resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution.