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.
Related
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 had a Web Server, which is configured with Ubuntu. Some web applications are hosted there and Clients from windows user browse/use those applications through the network. Application accessibility was smoother and faster and also was running without any interruptions.
But all the issues start when I configure the Windows Server and put all the users under a DOMAIN CONTROLLER. Now all the applications accessibility become too slow. Sometimes some pages are not loading at all.
I am mentioning all the IP configurations bellow-
Network Default Gateway: 172.16.0.1/16
Web Server- 172.16.2.2/16
Windows Server (Domain Controller)- 172.16.3.1/16
Using this Windows Server IP as DNS IP for all Client PC and also for the Web server.
Clients IP range: 172.16.1.1 to 172.16.10.254
Please See the Graphical view of my Configuration from the link below:
https://imgur.com/a/k3WLSg3
It was a DNS issue. I restored the Previous DNS settings in all clients and server then everything goes to normal condition.
I imported the OWASP BWA web application image into Virtual Box and started it up. Its supposed to show me the IP on which I can access my web application. Instead I see text that states that the web application can be accessed at http:///. How can I see what IP I can access BWA on? I have my Network Setting set to Host Only.
I got this problem because the VirtualBox dhcp server was disabled for the network that the BWA VM was on.
From the main VirtualBox screen:
File -> Host Network Manager and enable the dhcp server
I only had one network showing and that had the dhcp server disabled. If you have more than one network, you will have to dig around to figure out which one to enable.
**
Resetting the Host network Manager in to this configuration helped me to fix it.
**
Then Restart the instances or
service networking restart
I got this problem because I created more than one Host-only networks. After deleting till only one left, I started the VM again and it worked.
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.
Is it possible for me to run a webserver on my computer (shared ip) and access it remotely using my ip + subnet or at least some way that doesn't involve having the IT guys make changes to the machine(s) currently running our virtual servers and/or routing our subnet?
Rationale:
I'm on a computer at work, and I'm making changes to a plugin for Google Website Optimizer. I want GWO to be able to access localhost (i.e. my development environment) so that I don't have to deploy every change to the production server while I'm feeling out the system. (lots of changes; tedious deployment takes up most of the time)
I can't just supply my IP to GWO because that points to our production server (all of our computers at work are on the same IP). If I could construct a URI that points just to my computer, then I suppose I could let GWO view a page on my development environment and interact therewith.
Not only would achieving this purpose be helpful in present circumstances, but it would aid me immensely in that I could let my boss look at what I've got in dev, from his own machine, at his leisure, without deploying changes to production.
I'm not familiar with the Google Website Optimizer, or how/where a plugin for it that you might write would be executed. So I'm going to summarize what I understand about your problem (including some guesses) and go from there, please correct me if I'm wrong.
Your company has one public IP address.
Your workstation and all the hosts on your network are source NAT'ed to the internet.
Port 80 (http) on your public IP address is destination NAT'ed to your production webserver which is hosted as a virtual machine.
You have a development webserver that is hosted on your workstation.
You have reservations about involving your "IT guys" to making routing or system admin changes.
You want your development environment to be accessible from the internet.
First up (assuming everything above is correct):
access it remotely using my ip + subnet - No. Not possible.
Second up:
I could let my boss look at what I've got in dev - Easy, get him to point his browser at your workstation's IP address on your internal network.
Possible solutions for remotely accessible:
Talk to your "IT guys" about getting your dev environment made externally accessible.
Use name-based virtual hosts on your production webserver. Requires setting up a DNS record for the dev site (e.g. dev.your-company) and pointing it to your company's IP address. If SSL is in use this is harder to achieve. You could then:
Proxy requests for a different site name to your workstation (readily achievable with apache).. or
Host your development environment on your production server
Proxy a particular URL path to your workstation. (e.g. /dev/)
Get an unused port (e.g. 8080) on your public IP destination NAT'ed to port 80 on your workstation. Your dev environment URL might then be http://www.your-company:8080/