IE cannot display web page

  • Thread starter Thread starter Jo-Anne
  • Start date Start date
Indeed it does, Daave! (Sorry I misspelled your name in the last post.)



Jo-Anne



"Daave" wrote in message

news:%23Mcjb8ByKHA.4008@TK2MSFTNGP02.phx.gbl...

> Jo-Anne wrote:

>> 2. With the command nslookup, I got this:

>> Server: Illuminationsbydesign.net

>> Address: 216.69.164.196

>

> Same as:

> http://www.plaza-lighting.com/e/index.asp

>

> The plot thickens. :-)

>
 
I can open it if I use an anonymous proxy such as http://freesurfproxy.org

Maybe some of the computer whizes can explain that?

"Jo-Anne" wrote in message

news:%23iUTUWwxKHA.1796@TK2MSFTNGP02.phx.gbl...

> I'm using WinXP and IE7 on one computer and WinXP and IE8 on another. Both

> are fully updated--the OS and Flash and Java.

>

> Neither computer has been able to display one website. It's for a light

> fixture store; and when I phoned the store today, the people who work

> there said they use WinXP and IE and the site displays just fine (although

> someone else told them last week that the web page couldn't be displayed).

>

> Any idea how I can get to this site? It's

>

> http://lightoptions.net/

>

> Thank you!

>

> Jo-Anne

>
 
On Sat, 20 Mar 2010 11:23:25 -0500, "Jo-Anne"

wrote:



>Thank you, Robert! I was sure there must be a way, but I had no idea what it

>was. The mouse worked fine after Mark.

>

>Jo-Anne



For a more permanent fix for the command copy/paste, click on the icon

in the upper left hand corner of the command window, choose

Properties, on the Options tab make sure that "Quick Edit Mode" is

selected. You can then use the mouse to select but you will have to

press Enter to copy to the clipboard. (I can't figure out why that

isn't the default... why you have to press Enter to copy, and

right-click to paste... but I'm sure there's some archaic reason :-)
 
On Sat, 20 Mar 2010 00:57:30 -0500, "Jo-Anne"

wrote:



>2. With the command nslookup, I got this:

>Server: Illuminationsbydesign.net

>Address: 216.69.164.196

>

>Name: lightoptions.net

>Address: 66.29.206.232



What you have done here is to lookup lightoptions.net using their own

DNS server. That tells me that in general DNS is working on your

server.



However, it's clear that DNS is not working properly when the request

is forwarded to your router from your system. I see four

possibilities:

1. There is a table in your router that needs flushing that is

preventing you from looking up the lightoptions.net domain



2. THere is a table in the PC that needs flushing. I think you did

that already via someone else's earlier post.



3. You router can't get to the upstream DNS server when it doesn't

know where a site is located. That seems unlikely since you were able

to get to example.com and I am guessing that you have never been there

before (few people have)- so the router was able to look it up and

therefore verified that it can find the upstream DNS server.



4. There is something wrong with the upstream DNS server that your

router is using.



5. There is something VERY funky in the PC's configuration.



I assume you are working through a home router? Are you comfortable

accessing the router with username/password and poking around the

settings?
 
"+Bob+" wrote in message

news:ltncq5dtrkvdu0soo46o2ge9qb2elp1e8t@4ax.com...

> On Sat, 20 Mar 2010 11:23:25 -0500, "Jo-Anne"

> wrote:

>

>>Thank you, Robert! I was sure there must be a way, but I had no idea what

>>it

>>was. The mouse worked fine after Mark.

>>

>>Jo-Anne

>

> For a more permanent fix for the command copy/paste, click on the icon

> in the upper left hand corner of the command window, choose

> Properties, on the Options tab make sure that "Quick Edit Mode" is

> selected. You can then use the mouse to select but you will have to

> press Enter to copy to the clipboard. (I can't figure out why that

> isn't the default... why you have to press Enter to copy, and

> right-click to paste... but I'm sure there's some archaic reason :-)

>

>

Thank you, Bob! Works perfectly once I told it to start that way all the

time, not just for the one session.



Jo-Anne
 
"+Bob+" wrote in message

news:86ocq5hv7254pqq3kqn5ga6e9eqhjv2tk3@4ax.com...

> On Sat, 20 Mar 2010 00:57:30 -0500, "Jo-Anne"

> wrote:

>

>>2. With the command nslookup, I got this:

>>Server: Illuminationsbydesign.net

>>Address: 216.69.164.196

>>

>>Name: lightoptions.net

>>Address: 66.29.206.232

>

> What you have done here is to lookup lightoptions.net using their own

> DNS server. That tells me that in general DNS is working on your

> server.

>

> However, it's clear that DNS is not working properly when the request

> is forwarded to your router from your system. I see four

> possibilities:

> 1. There is a table in your router that needs flushing that is

> preventing you from looking up the lightoptions.net domain

>

> 2. THere is a table in the PC that needs flushing. I think you did

> that already via someone else's earlier post.

>

> 3. You router can't get to the upstream DNS server when it doesn't

> know where a site is located. That seems unlikely since you were able

> to get to example.com and I am guessing that you have never been there

> before (few people have)- so the router was able to look it up and

> therefore verified that it can find the upstream DNS server.

>

> 4. There is something wrong with the upstream DNS server that your

> router is using.

>

> 5. There is something VERY funky in the PC's configuration.

>

> I assume you are working through a home router? Are you comfortable

> accessing the router with username/password and poking around the

> settings?

>

>

Hi, again, Bob,



I just got back from Starbucks. I cleared the temporary internet files from

my netbook, and then I logged in and typed www.lightoptions.net -- and got

the Google search engine results rather than the website. I did it again and

got the same thing. I clicked on the link at Google and received the usual

error message.



So...I'm guessing it's not my router.



Jo-Anne
 
"Jo-Anne" wrote in message

news:O28wQbUyKHA.1548@TK2MSFTNGP02.phx.gbl...

> "+Bob+" wrote in message

> news:86ocq5hv7254pqq3kqn5ga6e9eqhjv2tk3@4ax.com...

>> On Sat, 20 Mar 2010 00:57:30 -0500, "Jo-Anne"

>> wrote:

>>

>>>2. With the command nslookup, I got this:

>>>Server: Illuminationsbydesign.net

>>>Address: 216.69.164.196

>>>

>>>Name: lightoptions.net

>>>Address: 66.29.206.232

>>

>> What you have done here is to lookup lightoptions.net using their own

>> DNS server. That tells me that in general DNS is working on your

>> server.

>>

>> However, it's clear that DNS is not working properly when the request

>> is forwarded to your router from your system. I see four

>> possibilities:

>> 1. There is a table in your router that needs flushing that is

>> preventing you from looking up the lightoptions.net domain

>>

>> 2. THere is a table in the PC that needs flushing. I think you did

>> that already via someone else's earlier post.

>>

>> 3. You router can't get to the upstream DNS server when it doesn't

>> know where a site is located. That seems unlikely since you were able

>> to get to example.com and I am guessing that you have never been there

>> before (few people have)- so the router was able to look it up and

>> therefore verified that it can find the upstream DNS server.

>>

>> 4. There is something wrong with the upstream DNS server that your

>> router is using.

>>

>> 5. There is something VERY funky in the PC's configuration.

>>

>> I assume you are working through a home router? Are you comfortable

>> accessing the router with username/password and poking around the

>> settings?

>>

>>

> Hi, again, Bob,

>

> I just got back from Starbucks. I cleared the temporary internet files

> from my netbook, and then I logged in and typed www.lightoptions.net --

> and got the Google search engine results rather than the website. I did it

> again and got the same thing. I clicked on the link at Google and received

> the usual error message.

>

> So...I'm guessing it's not my router.

>

> Jo-Anne

>



Actually, it sounds more and more like your router. What happens if you

power the router down, then turn it back on? Can you get to the site shortly

after start up?



I have a couple of Netgear routers that often used to have DNS problems, so

I switched the DNS settings on my PC to use the IPs of the servers that the

router was assigned by the ISP. This solved the DNS timeouts I was getting -

it might help you too.



--

Dan
 
DNS - when you use that proxy it's not your PC requesting a DNS lookup to

whatever server is assigned in your DNS settings, and so on up the chain,

it's the proxy that's requesting the IP address via DNS. If the address

happens to be cached by one of it's upstream DNS servers then it doesn't

matter if the authoritative servers for the domain are down as the proxy

will get the IP address from a cached entry, whereas if none of the DNS

servers between your PC and the authoritative have a cached entry for the

hostname then it'll fail if the authoritative DNS servers don't answer.



Dan



"Robin" wrote in message

news:eDK5wERyKHA.5776@TK2MSFTNGP06.phx.gbl...

> I can open it if I use an anonymous proxy such as http://freesurfproxy.org

> Maybe some of the computer whizes can explain that?





> "Jo-Anne" wrote in message

> news:%23iUTUWwxKHA.1796@TK2MSFTNGP02.phx.gbl...

>> I'm using WinXP and IE7 on one computer and WinXP and IE8 on another.

>> Both are fully updated--the OS and Flash and Java.

>>

>> Neither computer has been able to display one website. It's for a light

>> fixture store; and when I phoned the store today, the people who work

>> there said they use WinXP and IE and the site displays just fine

>> (although someone else told them last week that the web page couldn't be

>> displayed).

>>

>> Any idea how I can get to this site? It's

>>

>> http://lightoptions.net/

>>

>> Thank you!

>>

>> Jo-Anne

>>

>
 
Dan wrote:

> "Jo-Anne" wrote in message

> news:O28wQbUyKHA.1548@TK2MSFTNGP02.phx.gbl...

>> "+Bob+" wrote in message

>> news:86ocq5hv7254pqq3kqn5ga6e9eqhjv2tk3@4ax.com...

>>> On Sat, 20 Mar 2010 00:57:30 -0500, "Jo-Anne"

>>> wrote:

>>>

>>>> 2. With the command nslookup, I got this:

>>>> Server: Illuminationsbydesign.net

>>>> Address: 216.69.164.196

>>>>

>>>> Name: lightoptions.net

>>>> Address: 66.29.206.232

>>>

>>> What you have done here is to lookup lightoptions.net using their

>>> own DNS server. That tells me that in general DNS is working on your

>>> server.

>>>

>>> However, it's clear that DNS is not working properly when the

>>> request is forwarded to your router from your system. I see four

>>> possibilities:

>>> 1. There is a table in your router that needs flushing that is

>>> preventing you from looking up the lightoptions.net domain

>>>

>>> 2. THere is a table in the PC that needs flushing. I think you did

>>> that already via someone else's earlier post.

>>>

>>> 3. You router can't get to the upstream DNS server when it doesn't

>>> know where a site is located. That seems unlikely since you were

>>> able to get to example.com and I am guessing that you have never

>>> been there before (few people have)- so the router was able to look

>>> it up and therefore verified that it can find the upstream DNS

>>> server. 4. There is something wrong with the upstream DNS server

>>> that your

>>> router is using.

>>>

>>> 5. There is something VERY funky in the PC's configuration.

>>>

>>> I assume you are working through a home router? Are you comfortable

>>> accessing the router with username/password and poking around the

>>> settings?

>>>

>>>

>> Hi, again, Bob,

>>

>> I just got back from Starbucks. I cleared the temporary internet

>> files from my netbook, and then I logged in and typed

>> www.lightoptions.net -- and got the Google search engine results

>> rather than the website. I did it again and got the same thing. I

>> clicked on the link at Google and received the usual error message.

>>

>> So...I'm guessing it's not my router.

>>

>> Jo-Anne

>>

>

> Actually, it sounds more and more like your router.



But others have reported problems accessing that site, too, Dan.
 
"Daave" wrote in message

news:#a5T62cyKHA.5132@TK2MSFTNGP05.phx.gbl...

> Dan wrote:

>> "Jo-Anne" wrote in message

>> news:O28wQbUyKHA.1548@TK2MSFTNGP02.phx.gbl...

>>> "+Bob+" wrote in message

>>> news:86ocq5hv7254pqq3kqn5ga6e9eqhjv2tk3@4ax.com...

>>>> On Sat, 20 Mar 2010 00:57:30 -0500, "Jo-Anne"

>>>> wrote:

>>>>

>>>>> 2. With the command nslookup, I got this:

>>>>> Server: Illuminationsbydesign.net

>>>>> Address: 216.69.164.196

>>>>>

>>>>> Name: lightoptions.net

>>>>> Address: 66.29.206.232

>>>>

>>>> What you have done here is to lookup lightoptions.net using their

>>>> own DNS server. That tells me that in general DNS is working on your

>>>> server.

>>>>

>>>> However, it's clear that DNS is not working properly when the

>>>> request is forwarded to your router from your system. I see four

>>>> possibilities:

>>>> 1. There is a table in your router that needs flushing that is

>>>> preventing you from looking up the lightoptions.net domain

>>>>

>>>> 2. THere is a table in the PC that needs flushing. I think you did

>>>> that already via someone else's earlier post.

>>>>

>>>> 3. You router can't get to the upstream DNS server when it doesn't

>>>> know where a site is located. That seems unlikely since you were

>>>> able to get to example.com and I am guessing that you have never

>>>> been there before (few people have)- so the router was able to look

>>>> it up and therefore verified that it can find the upstream DNS

>>>> server. 4. There is something wrong with the upstream DNS server that

>>>> your

>>>> router is using.

>>>>

>>>> 5. There is something VERY funky in the PC's configuration.

>>>>

>>>> I assume you are working through a home router? Are you comfortable

>>>> accessing the router with username/password and poking around the

>>>> settings?

>>>>

>>>>

>>> Hi, again, Bob,

>>>

>>> I just got back from Starbucks. I cleared the temporary internet

>>> files from my netbook, and then I logged in and typed

>>> www.lightoptions.net -- and got the Google search engine results

>>> rather than the website. I did it again and got the same thing. I

>>> clicked on the link at Google and received the usual error message.

>>>

>>> So...I'm guessing it's not my router.

>>>

>>> Jo-Anne

>>>

>>

>> Actually, it sounds more and more like your router.

>

> But others have reported problems accessing that site, too, Dan.

>



Which could all be attributed to DNS issues, and the router could be making

that problem worse. Changing settings at the browser will make no difference

in this case. Switching to using the ISP DNS servers rather than the router

proxy server may help, if there's something very odd with the DNS responses

for that hostname. It's just something else to try. I myself have had

problems getting to it, but once I've got a cached DNS request it seems to

be fine, pointing to a DNS issue.



--

Dan
 
"Dan" wrote in message

news:4C83F1BF-C05F-4251-BAAA-80126E3C61D1@microsoft.com...

>

> "Jo-Anne" wrote in message

> news:O28wQbUyKHA.1548@TK2MSFTNGP02.phx.gbl...

>> "+Bob+" wrote in message

>> news:86ocq5hv7254pqq3kqn5ga6e9eqhjv2tk3@4ax.com...

>>> On Sat, 20 Mar 2010 00:57:30 -0500, "Jo-Anne"

>>> wrote:

>>>

>>>>2. With the command nslookup, I got this:

>>>>Server: Illuminationsbydesign.net

>>>>Address: 216.69.164.196

>>>>

>>>>Name: lightoptions.net

>>>>Address: 66.29.206.232

>>>

>>> What you have done here is to lookup lightoptions.net using their own

>>> DNS server. That tells me that in general DNS is working on your

>>> server.

>>>

>>> However, it's clear that DNS is not working properly when the request

>>> is forwarded to your router from your system. I see four

>>> possibilities:

>>> 1. There is a table in your router that needs flushing that is

>>> preventing you from looking up the lightoptions.net domain

>>>

>>> 2. THere is a table in the PC that needs flushing. I think you did

>>> that already via someone else's earlier post.

>>>

>>> 3. You router can't get to the upstream DNS server when it doesn't

>>> know where a site is located. That seems unlikely since you were able

>>> to get to example.com and I am guessing that you have never been there

>>> before (few people have)- so the router was able to look it up and

>>> therefore verified that it can find the upstream DNS server.

>>>

>>> 4. There is something wrong with the upstream DNS server that your

>>> router is using.

>>>

>>> 5. There is something VERY funky in the PC's configuration.

>>>

>>> I assume you are working through a home router? Are you comfortable

>>> accessing the router with username/password and poking around the

>>> settings?

>>>

>>>

>> Hi, again, Bob,

>>

>> I just got back from Starbucks. I cleared the temporary internet files

>> from my netbook, and then I logged in and typed www.lightoptions.net --

>> and got the Google search engine results rather than the website. I did

>> it again and got the same thing. I clicked on the link at Google and

>> received the usual error message.

>>

>> So...I'm guessing it's not my router.

>>

>> Jo-Anne

>>

>

> Actually, it sounds more and more like your router. What happens if you

> power the router down, then turn it back on? Can you get to the site

> shortly after start up?

>

> I have a couple of Netgear routers that often used to have DNS problems,

> so I switched the DNS settings on my PC to use the IPs of the servers that

> the router was assigned by the ISP. This solved the DNS timeouts I was

> getting - it might help you too.

>

> --

> Dan



I'm confused, Dan. Why would it be my router if I have the same problem at

Starbucks as at home? More info: I called my ISP (a local company) today.

The tech person couldn't reach the website from his office computer using

his company, but he could reach it from his home computer, which uses

Comcast. He suggested a DNS issue with the website rather than with my

router.



Jo-Anne
 
On Mon, 22 Mar 2010 12:08:42 -0500, "Jo-Anne"

wrote:



>

>I'm confused, Dan. Why would it be my router if I have the same problem at

>Starbucks as at home? More info: I called my ISP (a local company) today.

>The tech person couldn't reach the website from his office computer using

>his company, but he could reach it from his home computer, which uses

>Comcast. He suggested a DNS issue with the website rather than with my

>router.

>

>Jo-Anne



Jo-Anne:



It's them, not you. I just ran a check against about 20 DNS servers.

Roughly half of them failed looking up lightoptions.net. They have

serious DNS issues.
 
"+Bob+" wrote in message

news:hoffq5depkn0esk433qobqm1fk3ac0bq5s@4ax.com...

> On Mon, 22 Mar 2010 12:08:42 -0500, "Jo-Anne"

> wrote:

>

>>

>>I'm confused, Dan. Why would it be my router if I have the same problem at

>>Starbucks as at home? More info: I called my ISP (a local company) today.

>>The tech person couldn't reach the website from his office computer using

>>his company, but he could reach it from his home computer, which uses

>>Comcast. He suggested a DNS issue with the website rather than with my

>>router.

>>

>>Jo-Anne

>

> Jo-Anne:

>

> It's them, not you. I just ran a check against about 20 DNS servers.

> Roughly half of them failed looking up lightoptions.net. They have

> serious DNS issues.

>

>

Thank you, Bob! I just called the company and told them. Here's hoping they

can get it fixed...



Jo-Anne
 
"Jo-Anne" wrote in message

news:OcUVUJeyKHA.5292@TK2MSFTNGP06.phx.gbl...

> "Dan" wrote in message

> news:4C83F1BF-C05F-4251-BAAA-80126E3C61D1@microsoft.com...

>>

>> "Jo-Anne" wrote in message

>> news:O28wQbUyKHA.1548@TK2MSFTNGP02.phx.gbl...

>>> "+Bob+" wrote in message

>>> news:86ocq5hv7254pqq3kqn5ga6e9eqhjv2tk3@4ax.com...

>>>> On Sat, 20 Mar 2010 00:57:30 -0500, "Jo-Anne"

>>>> wrote:

>>>>

>>>>>2. With the command nslookup, I got this:

>>>>>Server: Illuminationsbydesign.net

>>>>>Address: 216.69.164.196

>>>>>

>>>>>Name: lightoptions.net

>>>>>Address: 66.29.206.232

>>>>

>>>> What you have done here is to lookup lightoptions.net using their own

>>>> DNS server. That tells me that in general DNS is working on your

>>>> server.

>>>>

>>>> However, it's clear that DNS is not working properly when the request

>>>> is forwarded to your router from your system. I see four

>>>> possibilities:

>>>> 1. There is a table in your router that needs flushing that is

>>>> preventing you from looking up the lightoptions.net domain

>>>>

>>>> 2. THere is a table in the PC that needs flushing. I think you did

>>>> that already via someone else's earlier post.

>>>>

>>>> 3. You router can't get to the upstream DNS server when it doesn't

>>>> know where a site is located. That seems unlikely since you were able

>>>> to get to example.com and I am guessing that you have never been there

>>>> before (few people have)- so the router was able to look it up and

>>>> therefore verified that it can find the upstream DNS server.

>>>>

>>>> 4. There is something wrong with the upstream DNS server that your

>>>> router is using.

>>>>

>>>> 5. There is something VERY funky in the PC's configuration.

>>>>

>>>> I assume you are working through a home router? Are you comfortable

>>>> accessing the router with username/password and poking around the

>>>> settings?

>>>>

>>>>

>>> Hi, again, Bob,

>>>

>>> I just got back from Starbucks. I cleared the temporary internet files

>>> from my netbook, and then I logged in and typed www.lightoptions.net --

>>> and got the Google search engine results rather than the website. I did

>>> it again and got the same thing. I clicked on the link at Google and

>>> received the usual error message.

>>>

>>> So...I'm guessing it's not my router.

>>>

>>> Jo-Anne

>>>

>>

>> Actually, it sounds more and more like your router. What happens if you

>> power the router down, then turn it back on? Can you get to the site

>> shortly after start up?

>>

>> I have a couple of Netgear routers that often used to have DNS problems,

>> so I switched the DNS settings on my PC to use the IPs of the servers

>> that the router was assigned by the ISP. This solved the DNS timeouts I

>> was getting - it might help you too.

>>

>> --

>> Dan

>

> I'm confused, Dan. Why would it be my router if I have the same problem at

> Starbucks as at home? More info: I called my ISP (a local company) today.

> The tech person couldn't reach the website from his office computer using

> his company, but he could reach it from his home computer, which uses

> Comcast. He suggested a DNS issue with the website rather than with my

> router.

>

> Jo-Anne

>



Sorry, I didn't read your post as you having tried it at Starbucks. Being in

the UK I don't associate going to Starbucks with accessing the internet :P



--

Dan
 
"Dan" wrote in message

news:43F3DDB7-DA85-4B25-97E7-5CE5C931F420@microsoft.com...

>

> "Jo-Anne" wrote in message

> news:OcUVUJeyKHA.5292@TK2MSFTNGP06.phx.gbl...

>> "Dan" wrote in message

>> news:4C83F1BF-C05F-4251-BAAA-80126E3C61D1@microsoft.com...

>>>

>>> "Jo-Anne" wrote in message

>>> news:O28wQbUyKHA.1548@TK2MSFTNGP02.phx.gbl...

>>>> "+Bob+" wrote in message

>>>> news:86ocq5hv7254pqq3kqn5ga6e9eqhjv2tk3@4ax.com...

>>>>> On Sat, 20 Mar 2010 00:57:30 -0500, "Jo-Anne"

>>>>> wrote:

>>>>>

>>>>>>2. With the command nslookup, I got this:

>>>>>>Server: Illuminationsbydesign.net

>>>>>>Address: 216.69.164.196

>>>>>>

>>>>>>Name: lightoptions.net

>>>>>>Address: 66.29.206.232

>>>>>

>>>>> What you have done here is to lookup lightoptions.net using their own

>>>>> DNS server. That tells me that in general DNS is working on your

>>>>> server.

>>>>>

>>>>> However, it's clear that DNS is not working properly when the request

>>>>> is forwarded to your router from your system. I see four

>>>>> possibilities:

>>>>> 1. There is a table in your router that needs flushing that is

>>>>> preventing you from looking up the lightoptions.net domain

>>>>>

>>>>> 2. THere is a table in the PC that needs flushing. I think you did

>>>>> that already via someone else's earlier post.

>>>>>

>>>>> 3. You router can't get to the upstream DNS server when it doesn't

>>>>> know where a site is located. That seems unlikely since you were able

>>>>> to get to example.com and I am guessing that you have never been there

>>>>> before (few people have)- so the router was able to look it up and

>>>>> therefore verified that it can find the upstream DNS server.

>>>>>

>>>>> 4. There is something wrong with the upstream DNS server that your

>>>>> router is using.

>>>>>

>>>>> 5. There is something VERY funky in the PC's configuration.

>>>>>

>>>>> I assume you are working through a home router? Are you comfortable

>>>>> accessing the router with username/password and poking around the

>>>>> settings?

>>>>>

>>>>>

>>>> Hi, again, Bob,

>>>>

>>>> I just got back from Starbucks. I cleared the temporary internet files

>>>> from my netbook, and then I logged in and typed www.lightoptions.net --

>>>> and got the Google search engine results rather than the website. I did

>>>> it again and got the same thing. I clicked on the link at Google and

>>>> received the usual error message.

>>>>

>>>> So...I'm guessing it's not my router.

>>>>

>>>> Jo-Anne

>>>>

>>>

>>> Actually, it sounds more and more like your router. What happens if you

>>> power the router down, then turn it back on? Can you get to the site

>>> shortly after start up?

>>>

>>> I have a couple of Netgear routers that often used to have DNS problems,

>>> so I switched the DNS settings on my PC to use the IPs of the servers

>>> that the router was assigned by the ISP. This solved the DNS timeouts I

>>> was getting - it might help you too.

>>>

>>> --

>>> Dan

>>

>> I'm confused, Dan. Why would it be my router if I have the same problem

>> at Starbucks as at home? More info: I called my ISP (a local company)

>> today. The tech person couldn't reach the website from his office

>> computer using his company, but he could reach it from his home computer,

>> which uses Comcast. He suggested a DNS issue with the website rather than

>> with my router.

>>

>> Jo-Anne

>>

>

> Sorry, I didn't read your post as you having tried it at Starbucks. Being

> in the UK I don't associate going to Starbucks with accessing the internet

> :P

>

> --

> Dan



Thank you, Dan! I forget sometimes that the worldwide web really is

worldwide.



Quite a few coffee shops in the U.S. are offering free WI-FI, and from what

I just read Starbucks is doing it in England as of a few months ago.



Jo-Anne
 
"Jo-Anne" wrote in message

news:OemS3ZqyKHA.244@TK2MSFTNGP06.phx.gbl...

> "Dan" wrote in message

> news:43F3DDB7-DA85-4B25-97E7-5CE5C931F420@microsoft.com...

>>

>> "Jo-Anne" wrote in message

>> news:OcUVUJeyKHA.5292@TK2MSFTNGP06.phx.gbl...

>>> "Dan" wrote in message

>>> news:4C83F1BF-C05F-4251-BAAA-80126E3C61D1@microsoft.com...

>>>>

>>>> "Jo-Anne" wrote in message

>>>> news:O28wQbUyKHA.1548@TK2MSFTNGP02.phx.gbl...

>>>>> "+Bob+" wrote in message

>>>>> news:86ocq5hv7254pqq3kqn5ga6e9eqhjv2tk3@4ax.com...

>>>>>> On Sat, 20 Mar 2010 00:57:30 -0500, "Jo-Anne"

>>>>>> wrote:

>>>>>>

>>>>>>>2. With the command nslookup, I got this:

>>>>>>>Server: Illuminationsbydesign.net

>>>>>>>Address: 216.69.164.196

>>>>>>>

>>>>>>>Name: lightoptions.net

>>>>>>>Address: 66.29.206.232

>>>>>>

>>>>>> What you have done here is to lookup lightoptions.net using their own

>>>>>> DNS server. That tells me that in general DNS is working on your

>>>>>> server.

>>>>>>

>>>>>> However, it's clear that DNS is not working properly when the request

>>>>>> is forwarded to your router from your system. I see four

>>>>>> possibilities:

>>>>>> 1. There is a table in your router that needs flushing that is

>>>>>> preventing you from looking up the lightoptions.net domain

>>>>>>

>>>>>> 2. THere is a table in the PC that needs flushing. I think you did

>>>>>> that already via someone else's earlier post.

>>>>>>

>>>>>> 3. You router can't get to the upstream DNS server when it doesn't

>>>>>> know where a site is located. That seems unlikely since you were able

>>>>>> to get to example.com and I am guessing that you have never been

>>>>>> there

>>>>>> before (few people have)- so the router was able to look it up and

>>>>>> therefore verified that it can find the upstream DNS server.

>>>>>>

>>>>>> 4. There is something wrong with the upstream DNS server that your

>>>>>> router is using.

>>>>>>

>>>>>> 5. There is something VERY funky in the PC's configuration.

>>>>>>

>>>>>> I assume you are working through a home router? Are you comfortable

>>>>>> accessing the router with username/password and poking around the

>>>>>> settings?

>>>>>>

>>>>>>

>>>>> Hi, again, Bob,

>>>>>

>>>>> I just got back from Starbucks. I cleared the temporary internet files

>>>>> from my netbook, and then I logged in and typed

>>>>> www.lightoptions.net -- and got the Google search engine results

>>>>> rather than the website. I did it again and got the same thing. I

>>>>> clicked on the link at Google and received the usual error message.

>>>>>

>>>>> So...I'm guessing it's not my router.

>>>>>

>>>>> Jo-Anne

>>>>>

>>>>

>>>> Actually, it sounds more and more like your router. What happens if you

>>>> power the router down, then turn it back on? Can you get to the site

>>>> shortly after start up?

>>>>

>>>> I have a couple of Netgear routers that often used to have DNS

>>>> problems, so I switched the DNS settings on my PC to use the IPs of the

>>>> servers that the router was assigned by the ISP. This solved the DNS

>>>> timeouts I was getting - it might help you too.

>>>>

>>>> --

>>>> Dan

>>>

>>> I'm confused, Dan. Why would it be my router if I have the same problem

>>> at Starbucks as at home? More info: I called my ISP (a local company)

>>> today. The tech person couldn't reach the website from his office

>>> computer using his company, but he could reach it from his home

>>> computer, which uses Comcast. He suggested a DNS issue with the website

>>> rather than with my router.

>>>

>>> Jo-Anne

>>>

>>

>> Sorry, I didn't read your post as you having tried it at Starbucks. Being

>> in the UK I don't associate going to Starbucks with accessing the

>> internet :P

>>

>> --

>> Dan

>

> Thank you, Dan! I forget sometimes that the worldwide web really is

> worldwide.

>

> Quite a few coffee shops in the U.S. are offering free WI-FI, and from

> what I just read Starbucks is doing it in England as of a few months ago.

>

> Jo-Anne



Given that my laptop is currently sat in my attic awaiting spare parts

(hopefully here this week, top tip: don't use Chinese "compatible" batteries

unless you want to risk the charging circuit being burnt out!), that I don't

drink coffee, and that I rarely get to the city centre where the nearest

Starbucks is, I'd never have known had you not mentioned it :P



--

Dan
 
You must log in or register to reply here.
Back
Top