[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 440
  • Last Modified:

ssh into Linux Ubuntu remotely

A customer has the following set up:
- a Linux (Ubuntu) server (192.168.1.77)
- a VMWare virtual machine (192.168.1.75) hosted on the Linux server
- Windows Sever 2008 running on the virtual machine
- a BT Business Hub router (192.168.1.254)

At present I can RDP into the Windows Server 2008 VM remotely and from there I can PuTTy into the Linux server over the local network.

I can also remote in to the VMWare Control panel on
https://<server WAN IP address>:8333

The objective is to be able to PuTTy into the Linux server remotely, but without having to go via the VM.

In the router, port 22 and port 8333 are forwarded to the Linux server.

But when I try to PuTTy in to the Linux server remotely, the PuTTy window comes up but there is no login prompt, just a static cursor; and after a short while the connection times out.

Doing an internal (local network) port scan on the server shows that ports 22 and 8333 are open.
Doing the same scan but remotely, to the server WAN IP address shows port 22 closed and port 8333 open.

So what do I need to do to be able to open port 22 for remote  ssh access to the Linux (Ubuntu) server?
0
socross
Asked:
socross
  • 4
2 Solutions
 
Peter HutchisonSenior Network Systems SpecialistCommented:
You might have some firewall rules on the server restricting access or that ssh only responds from certain subnets or ip addresse which may need to be modified to allow remote access. See https://help.ubuntu.com/community/SSH/OpenSSH/Configuring
0
 
socrossAuthor Commented:
Sorry, haven't had a chance to follow this up yet. Will get back to it asap.
0
 
socrossAuthor Commented:
I have tried temporarily disabling the firewall in the router, but it made no difference.

Please find attached the Linux server's current sshd_config file. I made one change from the original by adding the line:
GatewayPorts yes
But this made no difference (with or without the firewall in the router)

Can anyone shed any further light on this problem please?
0
 
socrossAuthor Commented:
This has now been solved. It turned out to be a combination of two things:

1) The static WAN IP of the remote server had actually been changed, unbeknown to me!

2) In the router there were too many instances of SSH applications being port forwarded. Reduced these to just one ( for PuTTY).

So thanks to Peter Hutchison, or his link on openssh, which was useful and informative, but not the route to a fix in this case.
0
 
socrossAuthor Commented:
Sorry for effectively accepting my own solution, but hopefully it may prove useful to others.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now