-
Notifications
You must be signed in to change notification settings - Fork 760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
impossible to connect windows 10 client machine through public ipv4 #2285
Comments
Can you run |
It's a public ipv4 !! not private!! |
Can you check the firewall rules and make sure |
I will try as soon as , it's vert strangely because even i disable firewall, i Can't connect through public ipv4 ,on 22 port pr 2222 , but inwill verify again |
got same issue ltsc 24h2 turn off firewall completely, connect |
@Chao216 did you verify the firewall rules to ensure |
Hi @tgauth, A weird thing is that i found on some Old os, install open ssh server will automatically add a firewall inbound rule allow port 22 , but new windows seems don't behave like that, I have to manually add firewall inbound rule. regarding permissions for log folder, I used a local admin account, could not open and got uac prompt, this cause the later on ssh server break (restart 1607 error), a question I would like to know is as i set System and administrators to have full control, why my account (member of administrators) can't access log folder by default? |
Yes - newer Windows versions still create a firewall rule, but only for private networks.
Technically, the check is for the SYSTEM and Administrators group SIDs so that is why the account, although administrator, is rejected. We're working on updating this, but in the meantime, if you navigate to the log folder via terminal, the user can still view the logs without the ACLs being modified by file explorer. |
i can only with private netwok , i've tested it |
i cant only private ip like 192.168.1.x or localhost , and i listen on |
reverted permissions full control back to Nt system and administrators, if i use elevated CMD or PowerShell prompt,can cd into log folder and cat the log content. Maybe an elevated Explorer process will be able to access just like the CLI environment |
Do you want video proof ,as i solve others problem , about firewall and ssh port ? |
@aragon5956 - can you provide |
i've jsut this :
and i can't start the service too ! |
I will see as soon as, if the service configuration points to
And no to
|
so i checked it , and it's ok : " C:\Program Files\OpenSSH\sshd" |
after solve this issue partially : #2290, i've still problem to connect through ipv4 |
if I scan my ip with zenmap software on windows , and even connecting my computer to a shared wifi without restriction and high level security policies, I do not see port 22 open. the connection on the service sshd.exe only works locally with the local address 127.0.0.1 and the private ip address of my computer at my home network |
@aragon5956, can you run the following in PowerShell to confirm the network firewall rule(s) for sshd: The profile field for the sshd rule must include See https://learn.microsoft.com/en-us/windows/security/operating-system-security/network-security/windows-firewall/configure-with-command-line?tabs=powershell for more information on configuring firewall rules. |
Prerequisites
Steps to reproduce
hello ,
i can't to connect my windows 10 machine client , i have this version of openssh : ```
OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2
usage: sshd [-46DdeGiqTtV] [-C connection_spec] [-c host_cert_file]
[-E log_file] [-f config_file] [-g login_grace_time]
[-h host_key_file] [-o option] [-p port] [-u len]
PS C:\Program Files\OpenSSH>
could you help me ?
Regards
Expected behavior
connected with success
Actual behavior
timeout
Error details
No response
Environment data
Version
OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2
Visuals
20241013144552.mp4
The text was updated successfully, but these errors were encountered: