Azure – Configure Azure IaaS VM to allow access by IP

azureazure-networkingwindows-server-2012-r2

I have an Azure IaaS Windows 2012R2 VM which is hosting a test website. The site is accessible externally by the hostname.

What do I need to do to enable access to that same site by IP address?
When I try to ping the IP address I get the message:

Request timed out.

When I try to ping the working hostname for the site, I get

Pinging myhostname.com [nnn.nnn.nnn.nnn] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

On the VM I tried to enable File and Printer Sharing (Echo Request ICMPv4 - In). I also followed these steps to enable IP and Domain Restrictions, though I'm not sure that's necessary?
I also tried disabling the windows firewall and this did not seem to do anything. I have re-started the VM.

Best Answer

Azure's load balancer does not support PING (ICMP), which is why you cannot ping your VM's IP address. You can use tcp-based ping tools to achieve this. Note: You will be able to ping between VMs internally (via each VM's internal IP address), assuming they're deployed into the same vnet / cloud service.

You can absolutely access your VM by IP address though.

Related Solutions

Not all settings in Printing Defaults applying to clients

While this question is old, it still got bumped to front page and C2*0 units might still be in use...

Konica C2*0 series drivers don't store job hold (and PIN and other print security settings) configuration with the rest of the configuration. I debugged this years ago and the driver creates these settings under HKCU\Software\Konica or something similar. I'll have to check my notes as I've forgotten over the years and we've retired most of C2*0 series.

Easiest way for you to find out (until I get to my notes). Start up Sysinternals ProcMon, filter only registry events and then configure job hold in print driver on your client (or server, doesn't matter). You should see that driver sets some registry values. Copy these values to GPP registry preferences and voilà!

Edit a bit later: So I went and looked up how it worked. To push out Secure Print for a print queue, you need to set following settings in GPP Registry

Key: HKEY_CURRENT_USER\Software\KONICA MINOLTA\KONICA MINOLTA C360SeriesPCL\Print server name\Print queue name\SecurePrint Value: Pass Type: REG_BINARY Encoded password for secure print. This must be obtained from client after manually configuring Secure Print.

Key: HKEY_CURRENT_USER\Software\KONICA MINOLTA\KONICA MINOLTA C360SeriesPCL\Print server name\Print queue name\SecurePrint Value: OutputMethodValue Type: REG_BINARY Output type. 03 seems to be Secure Print (hold job until user and password are entered at MFP)

Key: HKEY_CURRENT_USER\Software\KONICA MINOLTA\KONICA MINOLTA C360SeriesPCL\Print server name\Print queue name\SecurePrint Value: ID Type: REG_SZ User name for job, just a string

Azure Virtual Machine can’t serve websites

You are limiting incoming connection to port 80 only. Client browsers can use a port number ranging from 1024 and 65536 for their outgoing connection.

You need to change your security group settings to allow incoming connections from Any port:

allow-http    source: any    source port: any    dest: any    dest port: 80    service: tcp/80    action: allow
allow-https    source: any    source port: any    dest: any    dest port: 80    service: tcp/443    action: allow

Best Answer

Related Solutions

Not all settings in Printing Defaults applying to clients

Azure Virtual Machine can’t serve websites

Related Topic