Hi
My PC can connect to another server via ssh so the issue probably isn't on my side.
I cannot access the dedicated server (Windows 2008) through ssh, port scans show that the server's port 22 is filtered/stealth. I assumed that the port just wasn't set on the windows firewall.
So I tried to use the ISP's Linux rescue system which boots from the network and connect to it via ssh under the assumption that the port 22 would not be blocked on the linux environment. However port 22 remained filtered and any connections to the linux system just times out.
If anyone could shed some light on the issue or where the issue might be, I would be grateful.
Edit:
It looks like the issue was a hardware one, the remote hard reboot wasn't working so while I thought the server had booted in linux rescue, it was still in windows. I was able to access the linux rescue system with the remote access hardware the hosting company provided me with.
Thank you for all of your suggestions.I appreciate it.
My PC can connect to another server via ssh so the issue probably isn't on my side.
I cannot access the dedicated server (Windows 2008) through ssh, port scans show that the server's port 22 is filtered/stealth. I assumed that the port just wasn't set on the windows firewall.
So I tried to use the ISP's Linux rescue system which boots from the network and connect to it via ssh under the assumption that the port 22 would not be blocked on the linux environment. However port 22 remained filtered and any connections to the linux system just times out.
If anyone could shed some light on the issue or where the issue might be, I would be grateful.
Edit:
It looks like the issue was a hardware one, the remote hard reboot wasn't working so while I thought the server had booted in linux rescue, it was still in windows. I was able to access the linux rescue system with the remote access hardware the hosting company provided me with.
Thank you for all of your suggestions.I appreciate it.
Last edited: