Connecting to Web Service in VM from client in host - web-services

I'm running Ubuntu 10.10 in VirtualBox with Windows 7 as host. I have a java Web Service which I deploy onto a Glassfish3 server in Ubuntu and I want to be able to reach it from the host, according to the VBox documentation I should port forward port 8080 which is the port that my client application connects to on my host. To do this I do the following command in Windows VBoxManage modifyvm Ubuntu --natpf1 glassfish,tcp,,8080,,8080 which should forward my hosts 8080 port to my VM's 8080 port, but it doesn't seem to work when I try to reach it. Any ideas?

Ensure 8080 is not already used by some other process in Windows. Install Guest Additions from the ISO inside Ubuntu. Ensure you are using NAT as the option for networking. Ensure the firewall in Ubuntu does not block incoming requests.

Related

why am I not able to telnet to a Google cloud machine even when all access is allowed

To experiment with VPN, I have created a VPN firewall rule that allows access to all the ports from all the IPs.
But when I telnet to the machine from my windows machine, I get error telnet 35.197.238.136
Connecting To 35.197.238.136...Could not open connection to the host, on port 23: Connect failed
Why am I not able to telnet?
The most likely story is that that, by default, a default Compute Engine doesn't have the telnet server software installed. If it is not installed, it is obviously not listening. If it is not listening, then a client connection to port 23 (the default telnet port) will fail.
You can install the Telnet server on your Compute Engine using:
sudo apt-get install telnetd
You will also have to "think ahead". Once telnet is running and you connect a client, you will be asked to login. Logging in requires a userid/password pair. By default, your Compute Engine has none. Consider creating a user using the Linux command adduser.
You might also want to consider your usage of telnet as compared to SSH. It appears that SSH has all but supplanted telnet connections these days.

How to set Virtualbox centos 7 client to share host vpn

I need to access vpn of host from my virtualbox vm centos.
But search and tried several method failed.
Environment:
Host: Win10
VPN: shadowsocks-windows
Virtual box 5.2
Client: Centos 7
Search from google, many set virtualbox to use Bridge mode.
Here I use NAT mode and passed.
Enable shadowsocks to allow local network connection
Set Virtualbox to use NAT network Adapter
Get virtualbox network adapter ip by run cmd in centos consle: $ ip route show
Set Centos network proxy to use virtualbox network adapter ip and shadowsocks server port, by default is 1080
Then enjoy!
The following looks a good answer to the question:
virtualbox guest os through vpn
https://superuser.com/questions/987150/virtualbox-guest-os-through-vpn

Access host cmd from guest

I'm running Slackware as a guest on Win 7 Virtualbox as host. On the Slack i'm running ssh server which i can access from outside (by port forwarding). Is there a way to issue a commands on host (for e.g. start host's ssh server) via ssh server on guest?
No.
If there is no SSH Server running on your windows machine (the host), there is no way to use ssh from the guest OS...

Zeppelin on AWS EC2 (Ubuntu instance)

I installed Apache Spark and Zeppelin on an Ubuntu instance running on AWS. Zeppelin is starting fine and when I check the status it is OK:
sudo ./bin/zeppelin-daemon.sh status
Zeppelin is running [ OK ]
But I can not use the "ip address":8090 to see the zeppelin webpage and create notebooks. The IP address I am using is the public one AWS give me (and I changed the port to 8090 in zeppelin-site.xml).
Should I change the server address in the zeppelin-site.xml?
Zeppelin is indeed running on port 8090 on that server, but the port is not accessible externally -- that is, it can only be accessed from the server itself.
No fear! You can use port forwarding to connect to it.
Linux
ssh -i keypair.pem -L 8090:localhost:8090 user#<IP-ADDRESS>
This tells SSH to forward any requests sent to port 8090 on the local computer to the remote machine's localhost:8090. Therefore, you can access Zeppelin via localhost:8090 on your computer.
Here's an example of it in use: Big Data: Amazon EMR, Apache Spark and Apache Zeppelin – Part 2 of 2
PuTTy
If you are using PuTTY to connect to the host, there is a similar command in the Tunnels configuration screen. Redirect 8090 to localhost:8090 on the remote machine.

pfsense: Can't access web console when using virtualbox

I've installed pfsense 2.3 x64 in virtualbox with 2 adapters; One is bridged to my wifi adapter (adsl modem) (WAN) and the other one set as'Internal network' ('intnet') (Lan);
The problem is that although pfsense can automatically detect dhcp over first adapter and get an IP but my system (the host) can not ping the pfsense server (pfsense can ping both adsl modem gateway and the host).
Note1: Disabling the antivirus and firewall (kaspersky internet security 2016) has no effect.
Note2: I know that this setup works because I use the exact same network configurations for a Kerio Control server (v9.0.2, installed in virtualbox)
Note3: If I constantly ping pfsense server in my host (ping 192.168.1.102 -t) and at the same time restart pfsense server, during the booting phase of pfsense I can get two pings!
After contacting the pfsense official forum, it turned out that the WAN interface blocks everything by default. Therefore, either a rule should be defined to allow WAN to accept traffic or access server from LAN side.
I figured this out without having to go through the WAN interface, answer is on the pfsense forum
Configure host-only network "vboxnet1" (or any of the other host-only networks if you're already using vboxnet1 for other VMs) with the following:
192.168.1.77 (or whatever IP you want your host to appear as on the network)
255.255.255.0
DHCP Disabled
The make sure that the LAN adapter on your pfSense VM is a "Host-only Adapter" and that it's using "vboxnet1" (or whatever network you configured above)
Reboot/re-install and http://192.168.1.1 should work now