Win7 host, Ubuntu guest: Port of guest VM not listening

[hsnable]

I have a server application running on my guest VM and want to access it using the corresponding client application on the host. The problem is that the client cannot reach the server and the relevant server port of the guest VM shows up as "not listening" on the host.

Host configuration:
Windows 7 64-bit
IP address: 192.168.1.65 (shown in ipconfig)
Connected to the internet using a wirless card which connects to a home router (probably this is not relevant because neither client nor server need internet access)
The host runs the XLLoop client application (available on Sourceforge)


Guest configuration
Ubuntu 12.04 (Precise Pangolin)
Virtualbox network settings:
- Attached to = "Bridged Adapter"
- Name = "TP-Link 150Mbps Wireless N PCI Express Adapter" is selected (there is also "Realtek PCIe GBE Family Controller" in the dropdown list which is not selected)
- Promiscuous Mode = "Deny"
- Cable Connected = "True"
IP address: 192.168.1.68 (shown in ifconfig)
The guest VM runs the XLLoop server application (available on Sourceforge) on port 5454

I have run the following checks below.

1. The host can successfully ping the guest VM:

Code: Select all

ping 192.168.1.68

Pinging 192.168.1.68 with 32 bytes of data:
Reply from 192.168.1.68: bytes=32 time<1ms TTL=64
Reply from 192.168.1.68: bytes=32 time<1ms TTL=64
Reply from 192.168.1.68: bytes=32 time<1ms TTL=64
Reply from 192.168.1.68: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.68:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

2. The guest can normally not ping the host, but if I add a firewall rule on the host to allow ICMPv4 for all IP addresses then ping will work in both directions.

3. I can successfully ssh from the host into the guest VM using putty on port 22.

4. In the terminal of the guest the port 5454 shows up as listening:

Code: Select all

sudo netstat -tapen | grep ":5454"
tcp        0      0 127.0.0.1:5454          0.0.0.0:*               LISTEN      1000       14568       2273/python     

5. In the command prompt of the host, however, the port 5454 of the guest shows up as not listening. I am using the Microsoft PortQry tool to scan the ports of the guest VM:

Code: Select all

c:\Program Files\PortQryV2>PortQry -n 192.168.1.68 -e 5454
Querying target system called:
 192.168.1.68
Attempting to resolve IP address to a name...
IP address resolved to PCU.lan
querying...
TCP port 5454 (unknown service): NOT LISTENING

6. The firewall of the guest VM is switched off:

Code: Select all

sudo ufw default allow outgoing
sudo ufw default allow incoming

7. The host is using the standard Windows 7 firewall. Oracle VM Virtualbox Manager is in the list of programs which are allowed to communicate through the Windows Firewall (both "Home/Work (Private)" and "Public"). I also tried switching off the host firewall entirely, it did not help.

8. Instead of "Bridged Adapter" I also tried using the "NAT" network mode within Virtualbox and set up port forwarding. It did not help.

It would be great if you could let me know any suggestions what else I could try or how I could narrow down the potential sources of the error. Thank you in advance.

[Perryg]

Bridged or host-only is what you need to use, but from the looks of it the XLLoop server application is not configured properly. Verify that it is configured to use the IP address and not localhost.

[hsnable]

Thank you Perryg for your answer. The reason was indeed that the XLLoop server was using localhost instead of the 192.168.1.68 IP address. I have changed the source code of the server from

Code: Select all

self.server = SocketServer.ThreadingTCPServer(('localhost', self.port), XLLoopHandler)

to

Code: Select all

self.server = SocketServer.ThreadingTCPServer(('192.168.1.68', self.port), XLLoopHandler)

and now it works fine. I am using the bridged mode.