Target Goal: Be able to ping my VM which has a bunch of SOAP calls at localhost:1337/service.asmx
Current VM Settings: Set to Bridged with Replicate Physical Network Connection State enabled.
Known issues:
I cant hit the internet at all from within the VM. test via cnn.com fails.
I can hit localhost:1337 from within the VM
I cant hit VM localhost from the host computer.
What sort of adjustments am I going to need to make in order to open up my VM of MS Server 2012 R2 to the network for testing?
Since I set up a custom port: 1337 there was actually a firewall issue.
On the VM, set it back to NAT from Bridged (in the adapter settings)
On the Windows Virtual Machine, go into Firewall Settings.
Go into Inbound Rules.
Add New Rule for the defined port.
save it.
Now the host can access via that port the page i created.
Related
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.
We have created 2 x VMs (both with the same spec - Windows 2012 R2, 2 x cores, 12Gb, 1 static IP).
I have deployed our tomcat application to one server and the app responds on both localhost and the internal ip address of the VM e.g.
http://localhost:90/integrationmanager
http://10.150.4.11:90/integrationmanager
So that all works normally on that server.
On the the second server, the app responds ok on localhost but it does not respond on the internal IP address of 10.150.4.8
http://localhost:90/integrationmanager
but this fails http://10.150.4.8:90/integrationmanager
The tomcat server.xml is the same for both servers so it is not an app config issue. since the test is being done direct on the local server it is not a VPC firewall issue as the request is not going off-box.
I have switched back to an ephemeral address from a static and that made no difference.
Windows Firewall is disabled on both private and public networks, it is not a member of a domain so that is not applicable.
Any ideas ? I am considering blowing away the VM and starting again
it turns out that McAfeee (which has its own firewall) had been installed on the server which had the issue. Now disabled and all is working ok.
I have running node.js app in my docker container in Container Station in my QNAP NAS. It's working on my local network on the port I have specified.
Typically I would set reverse proxy pointing fe. my-domain.com/my-app :80 => :<local-port>
On NAS I have static IP provided, I have even a domain for public access (my-server.myqnapcloud.com) and I'd like to set up somehow my server to be visible outside. It doesn't have to be QNAP domain, I can set my own domain pointing to QNAP local address, but still I'm not able to forward local port to another in server scope.
What is the best way to setup such enviroment? It seems to be much easier without NAS at all...
If i'm not wrong, your QNAP server is over the router. If so, you have to change some settings...
Steps to do:
Open a Container Station and find the instance of your container.
Go to "Settings" then "Advanced settings" and find LAN bookmark (sieć)
There must be a grid: "Port Routing" with 2 columns: "Host" and "Container".
"Container" - a port on which container is listening incoming internal connections
"Host" - a port on which QNAP server is listening incoming external connections. You have to remeber this value!
Close Container Station and open myQNAPcloud application
If you don't see the service which is responsible for port forwarding, you have to add appropriate service.
After that you have to execute changes in a router.
Note:
I've struggled with the configuration of PostgreSQL database installed on container. Finally, i was able to achieve that. Here is detailed description: How to enable remote connections to your PostgreSQL server (in Container Station) on QNAP NAT server over the router
Hope this help.
I have configured jetty-maven-plugin in my eclipse Mars and I can run the server using jetty start and stop goals. I can able to access the website using http://localhost:8080/myapp but not using local IP address(i.e., http://192.168.0.5:8080/myapp) from my own computer or other computers connected in the same network via LAN and Wi-Fi.
As mentioned as a solution in these posts,
how to make jetty server accessible from LAN?
Configuring Jetty to accept connections from all hosts
I configured the server host to 0.0.0.0 from localhost to listen on all hosts. With this setting I can see on server start log,
INFO:oejs.AbstractConnector:Started SelectChannelConnector#0.0.0.0:8080
and it works only on http://localhost:8080 but it's not accessible from http://192.168.0.5:8080.
I also tried running that if the interface is accessible using the Networks Interface Listing as mentioned in this comment. and I got,
Display name: NETGEAR WNA1000M N150 Wireless USB Micro Adapter
Name: wlan4
InetAddress: /192.168.0.5
I also tried turning off my Windows Firewall/antivirus but din't help. My jetty version is <jetty.version>9.3.0.M1</jetty.version> and JDK 1.7. What could be the problem? Any help is appreciated.
McAfee Endpoint Security was the culprit here. It was blocking the requests with IP addresses from my very own computer. Turned off the firewall inside the Antivirus and I was able to access the site with http://192.168.0.5:8080/mysite from the browser and other devices connected through the network.
Sometimes some other program opens your port on external address before you do that with Jetty. It will receive all traffic instead. On Windows you will not know it if you reuse port (that is Jetty's default behavior). Check with netstat -ano what is the IP of the process that is indeed listening on 0.0.0.0:8080. Verify if it is your Jetty process only.
Then try connecting with telnet or netcat and see if you can open the connection and what is the response.