I have IIS running in Windows 8 in a VM on my Mac. With the Networking set to Bridged mode I can access IIS from my Mac using the IP address. This works fine when I'm connected to my network.
What I need to be able to do is access IIS from my Mac when there is no network connection available, and I can't figure it out.
Background: This is so that I can demo a web app to clients in situations where I have no 3G coverage and they don't have wifi I can connect to.
Turns out you need to go to Virtual Machine -> Network Adapter -> Network Adapter Settings, then select Private To My Mac.
The VM won't be able to connect to the internet, but your Mac should be able to connect to the VM on the IP that it's assigned, even when there's no internet connection.
Remember to add rules, or turn off Windows firewall in order to let traffic through to IIS though.
Related
I have a windows server 2016 running in Azure with RRAS VPN + NAT.
I use this RRAS VPN to be able to RDP to my other VM's in the virtual network.
However, when I connect my client (windows 10) computer to the RRAS VPN, my internet will stop working on the client (because internet access is blocked on the RRAS VM).
How can I prevent the client from trying to use the internet that my RRAS VPN VM provides? I tried disabling the use-default-gateway checkbox, but then I can no longer connect to my other VM's in the virtual network.
Thanks!
According to this link it seems that when you disable the "use-default-gateway checkbox" that the default routes are not added to your machine. In specific:
If “User default gateway on remote network” is turned on, the VPN client on successful VPN tunnel connection adds the default route on VPN interface with highest precedence. This way all the IP packets (except those destined to local subnet) go to VPN server. If this parameter is turned off, the default route is not added on VPN tunnel. This scenario will require user to add specific network specific route on the VPN interface – in order to reach the corpnet resources
So, you are left with editing your routes manually to ensure that they work. You can do this pretty easily in windows by working with the route table. The following article gives the basics of how to set this.
Essentially you will want to run something like this:
route ADD <azure network> MASK <azure mask> <azure gw ip>
After you have done this, you should be able to use the internet (via your local configuration) and access to your Azure servers (via the route you created above).
I have a VMware workstation which has Ubuntu in it and I've also installed LAMPP on it, I have already created a full running website using php. I could access the website on my local computer(where the vmware is installed) by using the ip address however if i try using other computers, I couldn't open the website. What am I missing?
One possible cause is that you probably have the VM interface card in NAT mode. If the interface is in NAT mode, your Ubuntu VM will be "hidden" behind the VM host.
Change the Virtual Machine network interface card to bridged mode, in Virtual Machine settings -> Network Adapter.
After setting the interface do Bridged mode, if you have a DHCP server on your network, you only have to renew the IP address of the Ubuntu machine (if it didn't do it automatically).
Check the new IP address of the Ubuntu machine (should be an IP address of your LAN). Use this IP to contact the web server.
I created a VM on Windows Azure. My actions
1) "File and Printer Sharing (Echo Request - ICMPv4-In)" set On
2) Windows Wirewall set Off
It still does not ping.
UPD: The network is working properly.
What do you mean by not pinged?
ICMP as protocol is disabled/blocked at Azure LoadBalancer level. So no matter what you do in your VM, you will never get ICMP traffic from the Internet inside the VM. The only way to get ISMP traffic into a VM is via Azure Virtual Network, and Azure Connect and from a valid joined computer.
Your actions (1) and (2) will help you get ICMP traffic from either:
Another Virtual Machine in the same Cloud Service
Another Virtual Machine in the same Virtual Network
Your computer, if it is part of the same Virtual Network
Your Computer if it and the target VM are in the same Group from Windows Azure Connect
** UPDATE **
After clarifying the question, you still will never be able to successfully execute ping whatever.cloudapp.net. In order to "make visible iis site", you need to add an Endpoint to your VM from the portal or the Management API for the port you need. In your case - port 80.
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.