I am hosting a Oracle Linux 6.5 OS using VMWare on my windows 7 laptop. The VM is configured to use NAT networking configuration, and I am able to ping the guest OS successfully from my windows machine. Also, I am able to access internet from within my guest OS.
However, I am unable to access a web application running on port 8080 on a web server hosted within the guest OS using a browser in my host OS. The application is however accessible when accessed from a browser within the guest OS.
Some observations that may be of some use:
1. Neither my laptop, nor the VM have a static IP address.
2. I am able to ping my guest OS from host, and vice versa
3. Firewalls are disabled on both my laptop as well as the guest OS
Any help would be highly appreciated
The reason for the above issue could be mostly because of firewall settings/rules enabled in guest OS OEL. To check the rules you can type iptables -L -n at bash prompt which will display FILTER rules (CHAIN INPUT/OUTPUT/FORWARD).
Adding filters to allow the host to access guest http protocol would make things work. On the other hand, if this is for developmental purposes you can completely disable the firewall filter by saying
service iptables stop. Keep in mind that this is not a safe approach as it exposes your guest to the world without a firewall especially if you are using a bridged network connection.
Related
my web server is on wsl, and beeware is on anaconda (windows version not linux), how do I configure beeware app to communicate with wsl server.
is there a feasible way?
current I'm using ngrok host as a gateway.
Is there any alternate way that doesn't require data packet to travel outside my system
Is there any guide to develop a local system?
I'm going to attempt to answer this generically since I don't currently use Beeware/Anaconda. I tried skimming the Beeware docs, but too much of it (including the "publish", which might be a key element in the nginx integration) is "Coming soon".
Assuming there are no virtual machines or containers in the mix, Windows should detect ports on the WSL2 instance and map them correctly to localhost. For instance, if in WSL you python3 -m http.server 3000, then you should be able to open that page in a Windows web browser at http://localhost:3000. So, by default, Anaconda on Windows should be able to access your web server in WSL through localhost. If this isn't happening:
First, make sure that nginx is listening on 0.0.0.0
Sometimes the Windows localhost auto-mapping seems to break. See this answer for some additional ideas. A quick-fix is often to just do a wsl --shutdown to reset the interfaces. A longer-term fix might be to disable Windows Fast Startup.
On the flip side, if there is any connection from nginx that needs to be made to Beeware/Anaconda, WSL2 does not map localhost back to the Windows host. You'll need to access it by the Windows host IP.
The easiest method is using mDNS, meaning from within WSL2 you can access the Windows host at the mDNS name "mycomputername.local", where mycomputername is the Windows "computer name".
See this answer for more details and alternatives if mDNS doesn't work.
I have been facing an issue with VMware which is unable to ping host machine from Guest Machin, but I'm able to ping guest machine from host machine.
Note: Here one more interesting matter is I could able to ping my host machine from guest machine with NAT network, but I couldn't ping my guest machine from host machine.
Your question is not clear at all.
In any case, you might wish yo specify what OS you are using in both nodes.
Firewall issues? You could try to disable Windows firewall for instance and locate where is the issue.
Could you give some basic data of the IP address of both nodes when the set up is in bridge mode?
Instead of disabling the firewall. Enable Rule "File and Printer Sharing (Echo Request - ICMPv4-In)" from Inbound Rules on both Host and the VMWare Workstation. In some host machines or VMWare Workstation you may find multiple Rules with the same name "File and Printer Sharing (Echo Request - ICMPv4-In)", make sure you enable all.
I am trying to use a Virtual Box VM to create a development environment I can share with a few dozen other developers. We are all on an internal network and need to connect to external web sites via proxy server. On the VM (guest) I am putting:
windows 10 64 bit
weblogic server
Several other dev tools
My requirements are:
From the guest OS I need to be able to hit the internet (ie google.com)
From the guest OS I also need to be able to open chrome and hit the server webpages running on the guest OS using mysite.com:8007/index.html.
I have modified the guest OS host file such that 127.0.0.1 maps to mysite.com. Ideally that should mean anything going to mysite.com will get resolved to 127.0.0.1.
Our proxy to reach the internet is http-proxy.mysite.com:80. I am able to connect to the internet (pages like www.google.com) as long as I enable the proxy (http-proxy.mysite.com:80) in chrome proxy settings. However I need to be able to enter mysite.com:8007/index.html in the browser and be able to load the homepage. I am able to hit the server using localhost:8007 but I need mysite.com:8007 to work since authentication cookies wont get passed correctly to localhost:8007 urls.
When I enter mysite.com:8007/index.html in chrome it keeps trying to redirect to the IP address of the host OS 10 . * . * . * and the server is not running on the Host OS.
When I enter 'curl mysite.com:8007/index.html' in a command prompt on the guest OS it actually does prints the correct response from my server (no idea why chrome is different / not respecting the host file config).
Any idea how to configure Virtual Box or chrome such that the external pages as well as the guest server pages work?
For internet access on VM, you need to configure network card as BRIDGE, NAT or NAT NETWORK. In your case NAT NETWORK will be better solution, because this will allow you bo be you VM visible in network, just like your Host.
If you have and Internal network you mus have also another card configured for VM for internal network.
To be your VM accessible from Internal Network via http... the coomputers in network have to setup DNS entry pointing to your VM.
I am running a web server in my Windows 7 guest OS, while I want to access it from my Mac host OS.
The web server is running and I can access it from my guest OS, but not from its host.
I'm using Parallels Desktop and I've tried to change the networking mode from shared, bridged, to host-only with no result.
This is for development sake, so I just need it to be at least accessible to my host OS.
Is this actually possible with Parallels, or should I keep an eye on other VM engine?
You want to put your guest into "bridged" networking mode. This will allow it to obtain an IP address on the same network as your host OS (from your router via DHCP or statically configured).
See this:
Shared Networking – the recommended type of networking for the VM. Your virtual machine will share whatever network connection is used by
your Mac. You will be able to access the network from the VM as long
your Mac OS X is connected to the network. The only limitation of this
mode is that the VM is not visible from the external network
Bridged Networking – uses your network adapter. You should choose this mode if you want to access the VM from the external network.
Please keep in mind that your network configuration should allow using
DHCP to assign IP address for the VM, or you should obtain a static IP
for the VM and set it in the guest OS.
I'm running the app engine devserver on localhost:8080, and want to access it from ie7 running on parallels.
I've tried all of the tips here:
How Do I Access The Host Machine From The Guest Machine?
And they seem like they should work, particularly accessing via the gateway ip address. I've also
sudo ipfw add allow tcp from 8080 to 8089
for good measure. Still no dice. I can access the external internet from ie7. The connection settings on parallels are set to 'Shared networking'. I'm out of ideas.
You're not by any chance running it on localhost/127.0.0.1 on OS X and are trying to get at it using localhost/127.0.0.1 from XP?
If so, that's likely to be your problem - I would seriously doubt that the two instances of the OS share the loopback interface as that's specific to the OS.
I'd run it on OS X using the local IP and not localhost, then use the IP address to access it from XP. This should work if the XP box can see the host.