Quantcast
Channel: Azure Networking (DNS, Traffic Manager, VPN, VNET) forum
Viewing all articles
Browse latest Browse all 6513

Cannot access the Internet on new VMs

$
0
0

I'm new to Microsoft Azure but have several years of experience with Windows and Hyper-V. Im currently running a Trial version of Azure.

Problem -My VMs cannot access the Internet...

I have created a virtual network and registered the Microsoft DNS server with it. Its has IP address 168.63.129.16.

I've then created two new servers each of which use this virtual network. They can both see one another on the network and I can ping between them.

Server 1 - DC1 has IP address 10.200.0.4

Server 2 - WEBSRV has IP address 10.200.0.5

Gateway - 10.200.0.1

All using DHCP assigned IP addresses from the Microsoft Azure DHCP server.

DNS is 168.63.129.16

The problem is neither can access the internet. Internet Explorer results in "Page cannot be displayed" messages and I can download updates either.

DNS resolution is working as I can resolve IP addresses.

I've noticed though that I can't ping the gateway address of 10.200.0.1. I'm guessing this is because Microsoft don't allow ICMP packets to the gateway?

Use a Local DNS Server?

I read several posts about using local DNS servers so decided to go down that road...

I setup my first server as a domain controller and DNS server and rebooted it. It still could not access the Internet though.

It was using 127.0.0.1 as its DNS server.

I then registered the local DNS server on the virtual network. So I added DC1 as a DNS server with IP address 10.200.0.4.

I restarted the server - Still no access.

It was still using 127.0.0.1 as its DNS server.

I then switched off the firewall and restarted it - Still no access.

I reset Internet Explorer - Still no access.

I restarted the server and finally I got Internet Access.

Why? What's changed? Answer: Internet Explorer was reset. I suspect this is a fluke though!

So I tried resetting Internet Explorer on my second server but still cannot access the Internet.

I rebooted it - Still no access.

My second server is using the local DNS servers of 10.200.0.4 (my DC1 server) and the Microsoft DNS server 168.63.129.16

It can resolve IP addresses successfully.

2 days later and I still cant get it to work.

We are going to be using either Amazon Web Services or Azure.

So far it's Amazon Web Services as its a lot easier to understand and works without all these ridiculous access issues.

I must be doing something wrong. If so what?

Thanks for any advice you can give me..

Alex



Viewing all articles
Browse latest Browse all 6513

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>