We have a machine - Windows Server 64 bit in MS Azure Cloud, where we have installed Denodo 5.5 full package with license.
The VM has two IPs, one being Internet IP by which we connect the VM and one Internal IP.
We have made changes in the Virtual Dataport >> JVM options >> RMI Host to reflect External IP in the Hostname.
We tried restarting the Virtual Dataport Server and VM multiple times. We also ensured that the above RMI configuration has been successfully saved in the Denodo configuration files.
Yet we are unable to open up the Denodo Virtual Dataport Admin Server from network machines (in internet) using the external IP. The firewall is also turned off in the Azure VM.
Please help resolve this issue if you have any idea on this one.
Many thanks!
You mentioned "We have made changes in the Virtual Dataport >> JVM options >> RMI Host to reflect External IP in the Hostname." but in this case you need to use the Internal IP so Denodo knows what network interface it needs to use. You can find more information in the following link https://community.denodo.com/kb/view/document/Installation%20steps%20on%20a%20cloud%20environment?category=Installation+%26+Updates
Related
I'm newbie to OpenStack! I've installed Openstack in Ubuntu Server 18.04 LTS on Microsoft Azure virtual machine (for my learning purpose because I don't have the required resources like 16GB RAM and 4 CPUs). I'm able to access the Openstack Dashboard with the help of public ip address of that VM using the browser in my machine. I've assigned floating ip address to the instance (here it is 172.24.4.8).
My instance specs are
This is my network topology and my azure virtual machine's network configurations
azure vm's private ip = 192.168.0.4
azure vm's public ip = 20.193.227.12
I can access the OpenStack Dashboard using azure vm's public ip address, But I'm unable to access the instance via SSH from my local machine and from that azure virtual machine too. Help me how to access them!
From your network topology screenshot, I guess that you used Devstack to create the cloud. Can you confirm that?
The external network named public is not connected to the world outside the cloud in any way. This is so because by default, Devstack creates an isolated external network for testing purposes. You should be able to access the instance from the Azure VM, however. The information given is not sufficient to explain why you can't.
See the Devstack networking page. It states that the
br-ex interface (...) is not connected to any physical interfaces
This is the technical reason for not being able to access instances.
The Shared Guest Interface section of the above page documents how to connect a Devstack cloud to a real external network.
EDIT:
The Shared Guest Interface instructions ask you to set this:
PUBLIC_INTERFACE= NIC connected to external network. *eth0* in your case.
HOST_IP= *192.168.0.4* for you
FLOATING_RANGE= Your netmask is 255.255.255.128, which translates to a network prefix of 25,
I think. If I am right, the value is *192.168.0.0/25*.
PUBLIC_NETWORK_GATEWAY= The IP address of the router on the *192.168.0.0/25* network.
Q_FLOATING_ALLOCATION_POOL= The range of addresses from FLOATING_RANGE
that you want to use as floating IPs for
your OpenStack instances.
FLAT_INTERFACE might be an old setting for the defunct Nova-Network service. I don't see it mentioned at all in the Ussuri version of Devstack.
I followed this tutorial (Elasticsearch 2.X on Microsoft Azure) and now I got the following question: How do I access elasticsearch 2.3.4 running on the VM from my Asp.Net MVC 5 website?
The VM is not reachable from the internet. So the only solution would be to access the Virtual Network from the WebApp?! But I don't know how to configure the Ubuntu VM to allow access to elasticsearch (I used iptables to allow port 9200 and in the elasticsearch.yml I added network.host: 0.0.0.0) and how to access the Virtual Network from my WebApp.
In the guideline (the link above) stood, that the WebApp and the VM have to be in the same Virtual Network - but I can't add my WebApp to the Virtual Network...
Thanks for any help or ideas! Azure is driving me crazy :|
EDIT: Okay, I found another tutorial (secure communications between azure web-apps and virtual machines), but that did not work either. Right now I can access the elasticsearch VM via an url from everywhere in the internet. When I try to access the VM from the Web-App via the private IP of the VM, it does not work :( Maybe because the Azure team changed something? Some screenshots look different to mine.
I have deployed a NFS server on an Azure Ubuntu 14.04LTS VM using this tutorial.
The problem that I'm facing is this: While I am able to successfully mount the folder I want when the client is my laptop or another physical machine, I can't do the same with another VM posing as a client.
I have configured the required endpoints (ports 2049 both udp and tcp) and I have, followed the exact same steps. What I get is this:
azureuser#testNode2:~$ sudo mount public.Azure.IP.ofNode1:export/users /export
mount.nfs: Connection timed out
I have also tried to mount using internal IP addresses but the outcome is the same.
If anyone could tell me what causes this or help me with this issue I'd be grateful.
You also need to open TCP/UDP 111. If the two VMs are in Azure, you should make them part of the same cloud service, or connect them to a virtual network in which case given Ubuntu in Azure ships with no default software firewall you wouldn't need to open anything.
I'm new to Azure (strike 1) and totally suck at networking (strike 2).
Nevertheless, I've got two VMs up and running in the same virtual network; one will act as a web server and the other will act as a SQL database server.
While I can see that their internal IP addresses are both in the same network I'm unable to verify that the machines can communicate with each other and am sort of confused regarding the appropriate place to address this.
Microsoft's own documentation says
All virtual machines that you create in Windows Azure can
automatically communicate using a private network channel with other
virtual machines in the same cloud service or virtual network.
However, you need to add an endpoint to a machine for other resources
on the Internet or other virtual networks to communicate with it. You
can associate specific ports and a protocol to endpoints. Resources
can connect to an endpoint by using a protocol of TCP or UDP. The TCP
protocol includes HTTP and HTTPS communication.
So why can't the machines at least ping each other via internal IPs? Is it Windows Firewall getting in the way? I'm starting to wonder if I've chose the wrong approach for a simple web server/database server setup. Please forgive my ignorance. Any help would be greatly appreciated.
If both the machines are in the same Virtual Network, then just turn off Windows Firewall and they will be able to ping each other. Other way is to just allow all incoming ICMP traffic in Windows Firewall with Advanced Settings.
However there is a trick. Both the machines will see each other by IP Addresses, but there will be no name resolution in so defined Virtual Network. Meaning that you won't be able to ping by name, but only by direct IP address. So, if want your Website (on VM1) to connect to SQL Server (on VM2), you have to address it by full IP Address, not machine name.
The only way to make name resolution within a Virtual Network is to use a dedicated DNS server, which you maintain and configure on-premises.
This article describes in details name resolution scenarios in Windows Azure. Your particular case is this:
Name resolution between virtual machines and role instances located in
the same virtual network, but different cloud services
You could potentially achieve name resolution, if you put your VMs is same cloud service. Thus you will not even require dedicated virtual network.
If your VMs are inside a Virtual Network in Azure, then you have to make sure two things.
Required Port is enabled.
Firewall is disabled on the server.
I was trying to connect to one VM where SQL Server DB was installed, from another VM. I Had to enable 1433 port in the VM where SQL was installed. For this you need to add an MSSQL endpoint to the VM on the azure management portal. After that i disabled windows firewall. Then i was able to connect to the VM from another.
I am basically a windows developer and very new to Sharepoint. I have Designed a small site in sharepoint on my virtual PC environment.
I want to access it from out side of VPC environment and also from other local LAN machines [like intranet].
How do i configure (IIS/Sharepoint Adm) to make my site as an intranet site?
I googled it, but not able to get desired information. I don't have much knowledge in ISS setting also, kindly provide any help in layman style.
You need to configure Virtual PC to use Virtual Networking:
In this case a virtual machine acts as
an independent computer in a network
with the host computer. If there is a
DHCP server in the network (Dynamic
Host Configuration Protocol) to assign
IP addresses, a virtual machine will
get it and will work as an independent
system in the network (otherwise, you
will have to specify an external IP
manually)
This is actually the default option in Virtual PC. You should be able to access the VM on the network as you would your own machine. Of course this means the VM's network settings must be valid for your network.
You shouldn't have to reconfigure anything is IIS/Sharepoint Adm to get this to work.