Connecting to the Internet

[Chuck]

Chuck:

I think I have a grasp of what you are saying. It is more clear after
seeing the Primary DNS of 68.238.128.12 and the Secondary DNS of 68.238.64.12
in the DSL Connection Information for the Westell modem. What I don't
understand is when I look at ipconfig /all, both the Primary and Secondary
DNS IP numbers are 192.168.1.1 and the modem is showing the true IP
address's. Why doesn't Windows recognize the true Primary and Secondary DNS
address's? Or, is Windows only looking for the modem at IP address
192.168.1.1 and it (the modem) does not have or need a Secondary IP Address
which Windows would utilize?

Regards,

Dan

Dan,

This is not a case of Windows not recognising the true addresses. For Windows,
192.168.1.1 is it. Only the router knows. To Windows, 192.168.1.1 IS the true
server. This is actually a slick setup. When your ISP changes its DNS servers,
instead of having to change the settings on each computer, you make the change
once, on the router. Or, with your router accepting automatic settings from
your ISP, you'll not even have to know when the DNS servers change.

So having learned a bit about DNS, let's see if the problem that you're having
is related to DNS. When the problem comes up, find out the IP address of the
server that you can't access. Then substitute the IP address, for the server
name, in the URL.

You just need to use another DNS server. Here's two DNS servers, by name and by
IP address, as an example. Use any of the 4 addresses, and find out the IP
address of the server that you need to reach.
All Net Tools: http://www.all-nettools.com/tools1.htm
All Net Tools: http://216.92.207.177/toolbox
DNS Stuff: http://www.dnsstuff.com/
DNS Stuff: http://69.2.200.183/
Use either server, and find out the IP address. Let us know if that makes a
difference.

 

[Guest]

--
D Roberts

Dan,

This is not a case of Windows not recognising the true addresses. For Windows,
192.168.1.1 is it. Only the router knows. To Windows, 192.168.1.1 IS the true
server. This is actually a slick setup. When your ISP changes its DNS servers,
instead of having to change the settings on each computer, you make the change
once, on the router. Or, with your router accepting automatic settings from
your ISP, you'll not even have to know when the DNS servers change.

So having learned a bit about DNS, let's see if the problem that you're having
is related to DNS. When the problem comes up, find out the IP address of the
server that you can't access. Then substitute the IP address, for the server
name, in the URL.

You just need to use another DNS server. Here's two DNS servers, by name and by
IP address, as an example. Use any of the 4 addresses, and find out the IP
address of the server that you need to reach.
All Net Tools: http://www.all-nettools.com/tools1.htm
All Net Tools: http://216.92.207.177/toolbox
DNS Stuff: http://www.dnsstuff.com/
DNS Stuff: http://69.2.200.183/
Use either server, and find out the IP address. Let us know if that makes a
difference.

Chuck:

I was able to run two tests last night. While using Firefox, I tried to use
google.com (the default home page connection), it would not connect. If I
then put the IP address in the URL, the google.com home page would load. I
had the same results usling my bookmark for netmail.verizon.net. I tried to
use Yahoo.com last night, but neither one would connect. Received error
messages on both of the Yahoo attempts.

Today, I tried a couple more times. the google test did the same thing as
last night. I tried google again this afternoon, google.com did not load. I
then clicked on Alaska Airlines bookmark (alaskaaiar.com) and the page
loaded. I will test some more sites when my computer does it's thing again.
I want to see if using a home page other than Google.com on Firefox and
Yahoo.com on IE6 will make any difference.

Regards,

Dan

 

[Guest]

--
D Roberts

--
D Roberts



Chuck:

I was able to run two tests last night. While using Firefox, I tried to use
google.com (the default home page connection), it would not connect. If I
then put the IP address in the URL, the google.com home page would load. I
had the same results usling my bookmark for netmail.verizon.net. I tried to
use Yahoo.com last night, but neither one would connect. Received error
messages on both of the Yahoo attempts.

Today, I tried a couple more times. the google test did the same thing as
last night. I tried google again this afternoon, google.com did not load. I
then clicked on Alaska Airlines bookmark (alaskaaiar.com) and the page
loaded. I will test some more sites when my computer does it's thing again.
I want to see if using a home page other than Google.com on Firefox and
Yahoo.com on IE6 will make any difference.

Regards,

Dan

Chuck:

Ran some more tests today, Saturday, May 6, 2006. Tried sears.com.
homedepot.com, firstusa.com. alaskaair.com and broadcom.com as well as their
respective IP addresses in the URL window. The first four in either Firefox
or IE6 returned an error message with both the name or IP address in the URL
box. When the name broadcom.com was entered in either IE6 or Firefox, the
error message would pop up. However, When the IP address of broadcom.com was
entered in the URL, the page would load. If I went back and tried any of
the first four names again, I obtained the same results as the initial test.

Apparently, only certain sites on the Internet are being resolved.

Any ideas?

Regards,

Dan

 

[Chuck]

:
Chuck:

Ran some more tests today, Saturday, May 6, 2006. Tried sears.com.
homedepot.com, firstusa.com. alaskaair.com and broadcom.com as well as their
respective IP addresses in the URL window. The first four in either Firefox
or IE6 returned an error message with both the name or IP address in the URL
box. When the name broadcom.com was entered in either IE6 or Firefox, the
error message would pop up. However, When the IP address of broadcom.com was
entered in the URL, the page would load. If I went back and tried any of
the first four names again, I obtained the same results as the initial test.

Apparently, only certain sites on the Internet are being resolved.

Any ideas?

Regards,

Dan

Dan,

Let's think outside the DNS issue for a bit. Look at the MTU, read my article
and some of the linked articles (which vary in technical intensity), and keep an
open mind:
<http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html>
http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html