Access localhost on VirtualBox IIS - iis

I am hosting a virtual machine (Windows 7) on my machine via VirtualBox. I am using a bridged connection to my host laptop. I am attempting to access localhost on the VM from another machine on the network. When I use ipconfig from my host machine I get:
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::9538:86c4:59e3:a43f%23
IPv4 Address. . . . . . . . . . . : 192.168.56.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
When I try to access 192.168.56.1, I am unable to load the page. I can ping 192.168.56.1 and get a reply, but I am not sure if this is the correct IP address to use.
I have also attempted to use the IP address from my guest machine (VM)
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::9538:86c4:59e3:a43f%23
IPv4 Address. . . . . . . . . . . : 192.168.2.24
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
but I am unable to get a reply when ping the 192.168.2.24 from my host. Any suggestions here?

Shutdown firewall, that's why it is not accessible from host. Use the IP address you get inside the guest, 192.168.2.24

I will add my cents here. If you don't want to shutdown the firewall, you can all HTTP traffic to flow through it as mentioned in this answer.
Open start menu and type firewall with advance security and open Windows Firewall with Advanced Security. In the window, select Inbound Rules and then double click on the World Wide Web Service (HTTP Traffice In) and check the Enable box. And you are done. You can access the server by putting its IP in the browser.

Related

How to host a node server [duplicate]

I have a pretty straight-forward question. I made a web game with NodeJS, and I can successfully play it by myself with multiple browser windows open side-by-side; however, I'd like to know if it's possible for other local machines to be able to access and play the game with me too.
I naively tried using this url: my-ip-address:8000 and it won't work.
Your node.js server is running on a port determined at the end of the script usually. Sometimes 3000. but can be anything. The correct way for others to access is as you say...
http://your.network.ip.address:port/
e.g.
http://192.168.0.3:3000
Check you have the correct port - and the IP address on the network - not the internet IP.
Otherwise, maybe the ports are being blocked by your router. Try using 8080 or 80 to get around this - otherwise re-configure your router.
If you are using a router then:
Replace server.listen(yourport, 'localhost'); with server.listen(yourport, 'your ipv4 address');
in my machine it is
server.listen(3000, '192.168.0.3');
Make sure yourport is forwarded to your ipv4 address.
On Windows Firewall, tick all on Node.js:Server-side JavaScript.
I had the same question and solved the problem. In my case, the Windows Firewall (not the router) was blocking the V8 machine I/O on the hosting machine.
Go to windows button
Search "Firewall"
Choose "Allow programs to communicate through Firewall"
Click Change Setup
Tick all of "Evented I/O for V8 Javascript" OR "Node.js: Server-side Javascript"
My guess is that "Evented I/O for V8 Javascript" is the I/O process that node.js communicates to outside world and we need to free it before it can send packets outside of the local computer. After enabling this program to communicate over Windows firewall, I could use any port numbers to listen.
One tip that nobody has mentioned yet is to remember to host the app on the LAN-accessible address 0.0.0.0 instead of the default localhost. Firewalls on Mac and Linux are less strict about this address compared to the default localhost address (127.0.0.1).
For example,
gatsby develop --host 0.0.0.0
yarn start --host 0.0.0.0
npm start --host 0.0.0.0
You can then access the address to connect to by entering ifconfig or ipconfig in the terminal. Then try one of the IP addresses on the left that does not end in .255 or .0
Faced similar issue with my Angular Node Server(v6.10.3) which set up in WIndows 10.
http://localhost:4201 worked fine in localhost. But http://{ipaddress}:4201 not working in other machines in local network.
For this I updated the ng serve like this
//Older ng serve in windows command Prompt
ng serve --host localhost --port 4201
//Updated ng serve
//ng serve --host {ipaddress} --port {portno}
ng serve --host 192.168.1.104 --port 4201
After doing this modification able to access my application in other machines in network bt calling this url
http://192.168.1.104:4201
//http://{ipaddress}:4201
The port is probably blocked by your local firewall or router. Hard to tell without details.
But there is a simple solution for which you don't have to mess with firewall rules, run node as a privileded process to serve on port 80, etc...
Check out Localtunnel. Its a great Ruby script/service, which allows you to make any local port available on the internet within seconds. It's certainly not useful for a production setup, but to try out a game with colleagues, it should work just fine!
const express = require('express');
var app = express();
app.listen(Port Number, "Your IP Address");
// e.g.
app.listen(3000, "192.183.190.3");
You can get your IP Address by typing ipconfig in cmd if your Windows user else you can use ifconfig.
After trying many solution and lot of research I did to the following to make sure my localhost is accessible from other machine in same network. I didn't start my server with IPAddress as parameter to listen method as suggested by others in this question. I did the following to make sure my local node js server is accessible from other machine on same local network. My node server is running in Windows 10 machine.
Open "Windows Defender Firewall with Advanced Security"
Select "Inbound Rules" in the left pane.
In the list of available rules, "Node.js Server-side Javascript" has "Block the connection" radio checked. Change this to "Allow the connection".
Please see the attached screenshot:
After these changes, I am able to access my localhost using http://IPAddress:Port/
Thanks.
And Don't Forget To Change in Index.html Following Code :
<script src="http://192.168.1.4:8000/socket.io/socket.io.js"></script>
<script src="http://code.jquery.com/jquery-1.6.2.min.js"></script>
var socket = io.connect('http://192.168.1.4:8000');
Good luck!
This worked for me and I think this is the most basic solution which involves the least setup possible:
With your PC and other device connected to the same network , open cmd from your PC which you plan to set up as a server, and hit ipconfig to get your ip address.
Note this ip address. It should be something like "192.168.1.2" which is the value to the right of IPv4 Address field as shown in below format:
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : ffff::ffff:ffff:ffff:ffad%14
IPv4 Address. . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Start your node server like this : npm start <IP obtained in step 1:3000> e.g. npm start 192.168.1.2:3000
Open browser of your other device and hit the url: <your_ip:3000> i.e. 192.168.1.2:3000 and you will see your website.
put this codes in your server.js :
app.set('port', (80))
app.listen(app.get('port'), () => {
console.log('Node app is running on port', app.get('port'))
})
after that if you can't access app on network disable firewall like this :
ngrok allows you to expose a port on the internet with custom forwarding refs:
$ npx ngrok http 8000
First, check your ipv4 address. In my case my ipv4 address is 192.168.44.112. If you don't know your ipv4 address, run this command on cmd.
ipconfig
Follow this code...
const express = require('express');
const app = express();
const port = process.env.port || 8000
app.get('/', (req, res) => {
res.send("Hello Network!")
});
app.listen(port, '192.168.77.112', ()=>{
console.log(`Listening port on ${port}`)
});
In Ubuntu you can fix this by allowing a specific port or port range:
sudo ufw allow PORT-NUMBER/tcp
example:
sudo ufw allow 3000/tcp
or a range:
sudo ufw allow 3000:3001/tcp
var http = require('http');
http.createServer(function (req, res) {
}).listen(80, '127.0.0.1');
console.log('Server running at http://127.0.0.1:80/');
By default node will run on every IP address exposed by the host on which it runs. You don't need to do anything special. You already knew the server runs on a particular port. You can prove this, by using that IP address on a browser on that machine:
http://my-ip-address:port
If that didn't work, you might have your IP address wrong.
I had this problem. The solution was to allow node.js through the server's firewall.

Unknown host connecting to internet in ubuntu

I tried to connect to my wifi network but i am not able to connect through my laptop .My other device at home are able to connect to internet. I am using ubuntu 16.04 LTS . I set my browser proxy to no proxy . I have no antivirus installed .
I tried to ping -c 5 (google .com and facebook.com) in terminal its showing unknown host google.com and unknown host facebook.com and tried to install eclipse while downloading it shows error java error unknown host .
Please help me to solve this issue.
Sounds like DNS may not have been configured when you connected to the network. This should normally happen automatically, but you can check by looking at the file /etc/resolv.conf. There should be at least one line in the file containing nameserver and an IP address.
If there are no nameserver lines, or if there's only one and it says nameserver 127.0.0.1, then you can try to use Google's public DNS by adding the line nameserver 8.8.8.8 (replacing the 127.0.0.1 if that's present).
Like everyone, I had to face this issue. So what did I do to address this issue?
1) I configured my Ubuntu server to have two network interfaces (NAT and Intnet).
2) In /etc/network/interfaces , I added the following lines:
auto enp0s8
iface enp0s8 inet static
address 192.168.10.23
dns-nameservers 8.8.8.8 8.8.4.4
3) Restarted the network - /etc/init.d/networking restart
Result: ping google.com worked.
I hope this helps you in resolving this issue :)

How to config Dual DHCP DNS Server on windows with Virtualbox?

I have a host system with Windows 10 OS.
I installed a Virtualbox and made a Ubuntu server 15.10 as a guest system.
I have a Apache on my Virtualbox.
My host is connected to the Internet through a router.
Usually my LAN on my host has the ip addresses like this:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::687b:c091:96f:731c%7
IPv4 Address. . . . . . . . . . . : 172.16.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
And my virtualbox has this ip: 172.16.1.101 through the bridge
When I want to access the webpage in my virtualbox it is sufficient to type
172.16.1.101:8080
in browser and then I see my index.html page in host.
I want to access this address trough a fake domain like example.lcl
I don't want to do that through the c:\Windows\System32\Drivers\etc\hosts file.
I want to use some local dns server like Bind or Dual DHCP DNS Server but I don't know how to do that.
As my host OS gets its ip dynamically from router I couldn't set Dual DHCP DNS Server to listen my local request to map some fake domains to that destination ip address.
Any help would be appreciated.
Thanks in advance.
Use Acrylic DNS Proxy. You can use wildcards and also dynamic answer with it. More details here:
http://stackoverflow.com/questions/138162/wildcards-in-a-windows-hosts-file

Send post request from android using 'ionic run android' to nodejs localhost server

I am using 'ionic run android' to run the ionic app on my device, connected with usb to my laptop for inspecting. I also run a node js server on my laptop's localhost:3000 port.
1) How to send requests from the ionic app that runs on my device to my server that runs on my laptop locally.
2) What is the url i need to send the request to? is it 'localhost:3000'? Is it my actual ip (x.x.x.x:3000)?
thanks!
los ,i have tried the same thing with actual android device and laptop with wifi connection.
To generate your server url:
Step1: bring your device and laptop or computer in the same network through wifi or wired connection.(Assume we are connected both mobile device and laptop through wifi router.If wifi router is not available we can connect our devices with wifi-hotspot of any of the devices and go on. )
step2: after connecting both in same network , go to terminal(mac) or command prompt(Windows) and fire ifconfig or ipconfig command respectively.
step3: Then find Wireless IPv4 Address which works as your server ip :
LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::781e:3ac2:6dcc:fa75%13
IPv4 Address. . . . . . . . . . . : 192.168.43.88
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.43.1
so in this case 192.168.43.88 is our server ip.
Step4:then append your server application's port number to our generated ip, as in your case 3000
192.168.43.88:3000
Step5: finally as we are using our laptop as our server we can say it is our local server. So for local server we need to use http protocol in our url, if you are using any remote server (e.g. Amezon server) or if you deploy server on any cloud(e.g. Heroku cloud) then use https as protocol.
So, now our address becomes: http://192.168.43.88:3000
Step 6: Then you can attach your server endpoint name or server url where your request is handled.
e.g. http://192.168.43.88:3000/home
Step 7: Finally , in your app send request to server using something. I used JQuery Ajax request as follows:
var basepath="http://192.168.43.88:3000";// Put your servers ip address here. if connecting to local server use 'http' and if to remote server use 'https'
$(document).ready(function(){
$("#mybtn").click(function(e){
$.ajax({
type:"GET",
url:basepath+"/bots",
success:function(data,status,request){
//success action
},
error: function(error){
//failuer action
},
timeout:5000
});
});
Hope this will help you.
I would suggest you try out https://localtunnel.me/. I wrote a short post about how to use it.
TL;DR is, you install it with npm:
npm install -g localtunnel
Then, start your project on some local port (for example 1337), and make sure all works well locally. Now, request a tunnel to your local server:
lt --port 1337
And you should get an output like:
your url is: https://awesome.localtunnel.me
You can use this link now and any requests to that url will be routed to your service on port 1337.

multicast traffic fails with virtualbox host only network

I have an application where it sends some multicast request to the multicast group ,
If I test my Client and Server application on two separate PC which are in same subnet it works fine .
Since I can not run always on two PCs during testing of my application, I thought of using the virtualbox to run the another OS to run my server application .
My Host is ubuntu , I installed the vitrtualbox to run the another guest os linux , and since my traffic only has to be with in the HOST and Guest , I have selected a "host only network type" .
My guest OS get the IP address but when I run my server application, It fails to join to the multicast group says
"No Such Device" .
Can someone help me to set up a network between the Guest and HOST OS ..
My main goal is to send a multicast request and it should reach the guest OS.
In VM:
ls /sys/class/net - get net devices. (lo, eth0, eth1...). You should have one lo and two eth devices.
sudo nano /etc/network/interfaces. At eth0 there is a NAT connection. Lo is a localhost. We should set the Host-Only connection. Add the following:
# The host-only network interface
auto eth1
iface eth1 inet static
address 192.168.56.101
netmask 255.255.255.0
network 192.168.56.0
broadcast 192.168.56.255
(Address is taken from ipconfig/ifconfig output in host system. Instead eth1 you can have another connection name, taken from the step 4.b.i)
For checking the edited file, run:
sudo service network-manager restart
Check if you have all three connections running. Check Host-Only addresses.
ifconfig
Reboot
sudo reboot

Resources