NAT issue

[pkasarski]

I have transmission-daemon running in a CentOS 7 virtual machine in VirtualBox. I am using NAT to forward port 9091 to the virtual machine. I am running Windows 10 which I understand has some issues with networking, but I do the same thing for SSH and it works fine. Settings are the same:

Code: Select all

NIC 1 Rule(0):   name = SSH, protocol = tcp, host ip = , host port = 22, guest ip = , guest port = 22
NIC 1 Rule(1):   name = Transmission web server, protocol = tcp, host ip = , host port = 9091, guest ip = , guest port = 9091

I am able to load the web page in lynx through SSH on the VM, so I know it's running, but I would prefer to open it in Chrome in the host OS. I can see the port is open in nmap:

Code: Select all

Nmap scan report for localhost (127.0.0.1)
Host is up (0.000061s latency).
Other addresses for localhost (not scanned): 127.0.0.1
Not shown: 998 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
9091/tcp open  xmltec-xmlmail

(Nmap has misidentified the service, but that doesn't matter.)

However, I am not able to load it in the host OS, I get connection refused. Any ideas why it would forward SSH port 22 without any issues but not 9091?

[noteirak]

Moved to "Linux Guests".

Nmap says 9091 is open on 127.0.0.1 which is only reachable by the guest itself. you need transmition to listen on all interfaces (IPs) for this to work.