I am trying out a conferencing application (BigBlueButton).
For this I created an Ubuntu virtual machine that functions as the application server. On this machine I can test the application by navigating to the app url (for example http://10.0.2.15).
I also created a second virtual machine that should function as a client. On this machine I want to be able to navigate to the server as well, but that doesn't seem to be working. If I try to navigate from the client to the server by using the app-url I get nothing, followed by a timeout.
To establish a network between the two machines I tried the following solutions:
Create a second network adapter on each virtual machine and attach to "Host-only Adapter" with name "vboxnet0"
Create a second adapter on each machine and attach to "Internal network" named "intnet".
I thought that either of above options would be a good solutions, but none of them works.
Can anyone help me out here?
FYI I am using MacOS X as host system.
EDIT:
I created my second machine by cloning the first one (using the clone utility). Maybe this causes both machines to be identical which makes them indistinguishable on a network. Would this cause a problem? (As a desktop developer I'm a bit of a noob when it comes to I.T.)
I just got this to work. What I did was the internal network with the tasteful name on both VMs, but THEN I went to Advanced and set the Promiscuous Mode to "Allow All". I connect just fine now. Try it!
OK, just looked at the dates and it was last updated 2009, but for anyone looking for the answer, here you go!
IF you cloned the machine and didn't change the ip, they will never connect...
Also - make sure there is something listening on the url that you're trying to reach.
each machine should have a different ip
(but on the same network of-course)
Set the interfaces you created to internal networking. Choose a tasteful and interesting name, like "mynet". Use that name as the network name for both of the virtual machines and they will automatically be able to talk to each other over those interfaces.
Sorry, I see you already did that. In this case just give those two machines static IP addresses on the interfaces of "internal networking" type. Like, 192.168.0.2 and 192.168.0.3.
Also, once you've changed the IPs make sure the server is listening on the right interface.
I realize this is long overdue... But I just got mine set up and am able to ping each virtual machine from one another.
Assuming you're running boot2docker like I am, simply right-click the boot2docker VM in VirtualBox and click clone. In the box that pops up, be sure to check the box that says "Reinitialize the MAC address of all network cards" so that the two virtual machines don't have the same MAC address.
That's it, seems to be working for me. I can ping, scan (via nmap) and even SSH into the virtual machines from one another or from my host machine.
Related
I have followed the guides at https://www.azerothcore.org/acore-docker/, and everything installs and works fine. Auth, WorldServer, DB, etc all work. However, when trying to play locally (LAN, main computer with client, the server on a different Windows machine on same LAN), it consistently loops back to realm selection.
So, I searched here and found these two questions/answers:
Azerothcore: Looping on Realm Selection List
How to resolve sticking in "Realm Selection"?
I have followed the guide in the bottom one, and have changed the Address field in the database to my external IP address (assigned by ISP). The LocalAddress is 127.0.0.1 The rest of the information appears to be correct.
When trying to connect via the external IP, it won't connect at all. But when I try setting my realmlist to 127.0.0.1 it will connect and log me in, but continually loops back to the realm selection screen.
To make sure it was updating, I changed the name of the realm and it shows up correctly when I try and log in. So the data appears to be saved to the database, but I cannot get it to connect from the LAN.
Followed the official guides, and changed the IP address in the DB to external IP. Same result, except now it takes a few seconds to connect and try to log into the realm. Then fails, back to realm selection.
Help would be appreciated. Thanks.
It's 99.9% related to your networking. That's what it turns out to be for pretty much everyone asking this question.
Most likely either a port isn't forwarded correctly, or your firewall prevents the connection. Try and use an external service to verify if the port is open. (Do a search for "Port open check"). Also, check your firewall to have the worldserver listed as an exception in the right folder.
Another common mistake is to change the "default" values when using HeidiSQL in the realmlist db instead of changing the actual values in the 'data' tab.
I'm experiencing a strange issue with Microsoft Edge not loading a local Craft CMS website hosted inside a vagrant virtual machine. Any attempt to load the locally configured host name or IP, returns the "Hmm, we can't reach this page." error.
I have a line in my hosts file:
192.168.10.12 test.craft.dev
I've read various resources about Microsoft Edge not properly handling the hosts file properly, however not even the IPv4 address works either. I've tried several of the recommendations related to Internet Options tweaks but nothing works, it does seem however the hosts file is not the issue.
The network configuration uses NAT and sets an IP in the range of 192.168.10.x (defined by Homestead.yaml, if I assign a public_network and get an IP with my LAN network DHCP range, Edge can access this IP, but it doesn't explain why all other browsers work and Edge doesn't without it.
It's worth mentioning that the local Craft hostname will load fine in every other browser (including IE). Does Microsoft Edge have specific issues with loading local websites inside VirtualBox due to some network level issue?
Install and run fiddler. It will do everything automatically.
Edge browser seems to pay attention to the interface you are using to access your sites. My guess is that you are using Vagrant to launch a Virtualbox VM. My answer below assumes that you are accessing via a Virtualbox host-only network, or some other network interface that has an NdisDeviceType of 1.
What didn't work
None of the following worked for me:
Using about:flags and confirming that "allow localhost loopback" was on
Control panel, Network and Internet, Internet Options, Security and adding my site explicitly to Trusted Sites or Local Internet.
CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"
My environment
In my case, I have VirtualBox 5.2.18 running on Windows 10 build 1803 "Spring Creators Update". Using Edge 42.17134.1.0. I have a host-only network for my VM guests. e.g. 192.168.7.0/24. I couldn't access addresses from my Edge on the VM host such as http://192.168.7.0. This site was hosted by a web server running in my VM guest. Note that this address worked just fine in Google Chrome, Internet Explorer 11 etc.
What worked
The solution is as follows:
Find the interface number for the host only network. I ran "route print" from the Windows command line and the first number shown in the "interface list" in my case was 17.
Use regedit to change the interface type from 1 to 0. The key is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4d36e972-e325-11ce-bfc1-08002be10318}\XXXX
In my case XXXX was 0016 because my interface number was 17. I had to change *NdisDeviceType from 0 to 1. The * in that key name is a literal asterisk. I had to reboot for the changes to take effect.
The answer was gleaned from a post by "Jani L" dated Oct 3, 2017, on the first URL referenced below, but it didn't give a clue as to how to determine the interface number. The second reference below was the thread on which I originally posted this solution.
References:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10142843/
https://social.technet.microsoft.com/Forums/en-US/0face535-3c7a-4658-be34-6c376322ca34/microsoft-edge-cant-open-local-domains
https://www.virtualbox.org/ticket/15565
It seems you are using Laravel Homestead box. If so, you can forward one of your host ports to the 80 port of your VM. Thus, you will be able to access your web sites hosted on your VM on MS Edge.
Here is what I've done:
ports:
- send: 8000
to: 80
If you don't want to have to type yourdomain.dev:8000 you may use fiddler. Thus, you will be able to only type yourdain.dev. :D
I have a web application I have developed on a server on my home computer. Is it possible to access that web page from another computer on my home network?
My naive approach was just enter my ip address followed by the port number :8888 which the server is listening on...
Any help would be great thank you.
I don't know if it will help but you can use an ssh connection to your computer. But you need to do it from a shell (from terminal on a mac, use putty on a PC)
In the end it was easier to set up remote access to the server by setting up port-forwarding on my router and using no-ip for DNS management. They have a decent walkthrough to get it all up and running. So i simply have to type in my-address.no-ip.org to access my site from any remote device.
Otherwise the links to questions on superuser that Sampo posted are worth a try.
This may be a general topic, but I came across the issue while working on some code using the Rook package.
The recent R versions include an http server. You may have seen this while checking for help topics using RGui. It opens a new browser with the IP/Port, etc.
For eg., if I enter ?paste, this brings up,
http://127.0.0.1:31234/library/.../paste.html
But if I use my IP, say 192.168.1.2 in place of 127.0.0.1, the page fails to load, I get an error
While trying to retrieve the URL:http://192....
The following error was encountered:
We can not connect to the server you have requested
I have other apps that have httpd interfaces, and I can go to those app's http interfaces using both 127.0.0.1 and 192.168.1.2 ... etc. So, as far as system/network permissions are concerned - I do not think that is the issue here.
Rather, there is something specific to the R httpd process that disallows it to be accessed using the domain name, etc ?
The above was tested in a corporate network. When I tried the same process from my home network it worked fine. However, since I already access http interfaces of many other locally installed apps from the corporate PC, I think there might be something specific to R's http process that needs to be checked ?
Workstation is running - Windows XP
Please let me know if you have any thoughts on the above,
Regards,
Raj.
Fixed it. The trick is to specify,
s <- Rhttpd$new()
s$start(listen="0.0.0.0",port="20000")
when starting the Rook process. Specifying 0.0.0.0 makes it listen to all the interfaces and now I can access it using my external IP. Thanks a lot for your help nonetheless !
When opening a TCP port, the local IP address may be chosen. For incoming connections, typically INADDR_ANY (-1) is supplied to bind(), which means to open the port on every available interface.
However, it is quite possible to open a port on just one interface on your machine (in this case, 127.0.0.1), simply by supplying the IP address of the interface. Seems that R does just this.
My guess is that you may have a proxy in place on your corporate network. Your browser is probably configured to use that proxy to access the Internet. Most browsers will exclude an address which they know to be local (127.0.0.1 or localhost) from using the proxy, but might not exclude any other IP.
Try disabling the proxy in your browser (even "Auto-Detect", completely turn the proxy off) and see if you're able to connect.
I had the same problem.
If you are using RStudio, this might be a bug in the RStudio. Check out this link:
https://support.rstudio.com/hc/communities/public/questions/202656007-Cryptic-error-on-starting-RStudio-daily-with-R-devel
Updating to the latest version of RStudio with the latest version of R fixes the problem.
I am a noob when it comes to network. Recently, I was trying to help a friend edit php code. In his office, there is a computer running which he said is the server that hosts the site. But he is not sure since the guy that build the site is unreachable now. So, he gave me the password and username to this local server but no ip to me. I have no idea how to connect to this "in house" server.
I see that there are several computers in the office and I tried to ssh to their LAN ip, ie. 1.1.1.1... to 1.1.1.10 something like that but none of the connection went through.
When I look up the ip of the website and put the ip into the browser, it actually goes to networksolutions.com. So guys, do you think the source code can be found on networksolutions.com(which is what I think) or is there a way to try to connect to this "in house" server(I am not even sure whether there's anything in it).
Have you tried attaching a monitor and keyboard to this server to determine what it is?
The IP of the site appears to be virtual hosted by Network Solutions. It is likely the server in the room is in fact not the server, instead that is handled by NetSol.
if you know the local ip range of the network which is normally either 10.*.*.* or 192.168.*.* or so you can use nmap to locate any servers quite quickly like: nmap -vvv 192.168.0.* which takes 5 seconds to find 4 end points