Help with initial DNS IP address set up on Windows 10

I have successfully created my droplet and have installed Ubuntu 16.04 with Putty on my machine that’s running Windows 10. When I set up LAMP successfully on the console, the installation did not give me any errors in the console installation. However, when I try and access my IP address for my droplet on the address bar which is supposed to give me the apache default page, I get a “This site can’t be reached took too long to respond.” message. I’m thinking Windows 10 is blocking the IP address or a port is being blocked.

I’ve temporarily shut off the Windows 10 firewall but that hasn’t resolved the issue.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

When you assign a static IP address, you need to tell the computer the IP address you want to use, the subnet mask for this IP address, and, if necessary, the default gateway to use for internetwork communications. An IP address is a numeric identifier for a computer. Ip addressing schemes vary according to how your network is configured, but they’re normally assigned based on a particular network segment.

IPv6 addresses and IPv4 addresses are very different. With IPv6, the first 64 bits represent the network id and the remaining 64 bits represent the network interface. With IPv4, a variable number of the initial bits represent the network id and the rest of the bits represent the host id. kmspico For example, if you’re working with IPv4 and a computer on the network segment with a subnet mask of, the first 24 bits represent the network id and the address range you have available for computer hosts is from to In this range, the address is reserved for network broadcasts.

Hey friend,

It seems that is not responding to ping. I would propose that it’s network settings may have been damaged somewhere along the way. I posted this a bit ago, it may offer some insight. At the very least, it will give you a path to double check settings and then tell you what we may need to investigate further:

Kind Regards, Jarland