On 7/17/2010 8:26 PM, dueker1 wrote:
I installed WHS several months ago. It works like a champ, I can connect from other computers using remote desktop connection, I have a valid IP address,
however; I can't connect to the internet. This was not an issue until the WHS update was unable to complete (understandably)
w/in IE, do not have use a proxy enabled, have removed the ck mark from "automatically detect settings"
IE still says "the page cannot be displayed."
Hi Dueker1,
Since you're able to use Remote Desktop Connection to get into your server, let's try a few things. On the server, click the Start button, and under Programs > Accessories, click on Command Prompt. This should open a black window on the screen.
Type the following in and press enter at the end.
ipconfig /all
There will probably be a lot of results (depending on what networking has been installed), but the one you're concerned with is going to be something like Ethernet 1 or Local Area Network Connection 1. Assuming that you know the IP Address of your
server, it will be the connection that has that IP Address listed.
There are four pieces of information that are needed from this:
IP Address:, Subnet Mask:, Default Gateway:, and DNS Servers:. If the Default Gateway and DNS servers are blank, then that explains why you're unable to connect to the Internet. The "Default Gateway" is the IP Address of your router.
In essence it's your gateway to the Internet. The DNS Servers are the way your computer finds out where www.yahoo.com is located (and gets the page from them).
*This is an overly simplified description*
If the Default Gateway and DNS servers are not listed, you'll have to open your Network Connections (Start > Control Panel > Network Connections), then right click on the Local Area Network adapter in the window, and choose Properties. Scroll
the list down to TCP/IP version 4, click on it, then click on Properties.
There should be two groups of settings in the window. They may both be set to "Obtain IP Address Automatically", or they may have specific information in them. If they are set to "Obtain IP Address Automatically", my personal
suggestion is to change to "Use the Following IP Address" and put in the IP Address that your server is currently using, the subnet mask (which will most likely be 255.255.255.0 if your IP Address starts with 192.168.; 255.255.0.0 if your IP Address
starts with 172.; and 255.0.0.0 if your IP Address starts with 10.). Put your router's IP Address in for the Default Gateway, and also for the first DNS Server (since it will prompt you for those IP Addresses). For the DNS server, you can put any
DNS Server in, so you could do the ipconfig on your desktop and get the servers listed there, for example.
Click OK, and then close out the other networking box (the one with the TCP/IP version 4 listed in it). You'll lose connection for a few seconds while it's updating the network connection. Then you should be able to get on the Internet.
==========================================
If ipconfig shows the proper default gateway and DNS Servers, you can try pinging. Start by pinging the server's Network Interface Card (NIC) using the following (press Enter after each of these)
ping 127.0.0.1
You'll see some information that includes
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
ping router's ip address (like ping 192.168.2.1 for example)
You should hopefully see the same thing as above. If not, then try unplugging the router for about 10 seconds, and plugging it back in), then repeat the steps after it's completely powered on.
ping www.google.com
If you don't see the same results, we'll try it another way.
ping 173.194.33.104
If you do see the success results with this, then it means your DNS information is causing a problem.
Reply back with the results of the ipconfig and ping tests, if you try them, and we'll try to help you further.
Have a great day:)
Patrick.
Smile... Someone out there cares deeply for you.
Have you updated today?
http://update.microsoft.com
Smile.. Someone out there cares deeply for you.
