how to solve this problem?

After booting, every now and then my browser doesn't seem to work.
Sometimes solved after swiching off and on of modem.
But what is a real solution?

(I had modem FW update, multiple Windows 7 updates and Comodo internet
security updates)

Sometimes it boots without this problem.
I would surely like to have this solved.
It's taking me ages every evening to get started :-((




------------------------------------------------
Deze webpagina is niet beschikbaar

ERR_NAME_NOT_RESOLVED
Opnieuw ladenDetails verbergen
De server op www.telegraaf.nl kan niet worden gevonden, omdat de DNS-lookup
is mislukt. DNS is de netwerkservice die de naam van een website vertaalt in
het internetadres. Deze fout wordt meestal veroorzaakt door een verbroken
internetverbinding of een verkeerd geconfigureerd netwerk. Deze kan ook
worden veroorzaakt door een niet reagerende DNS-server of een firewall die
de toegang van Google Chrome tot het netwerk blokkeert.
Een gecacht exemplaar van http://www.telegraaf.nl/ openen
------------------------------------------------


--


|\ /|
| \/ |@rk
\../
\/os

Linea Recta wrote on 09/14/2015 12:40 PM:
After booting, every now and then my browser doesn't seem to work.
Sometimes solved after swiching off and on of modem.
But what is a real solution?

(I had modem FW update, multiple Windows 7 updates and Comodo internet
security updates)

Sometimes it boots without this problem.
I would surely like to have this solved.
It's taking me ages every evening to get started :-((


Fyi...it might be appropriate to let folks now 'which browser' is your
browser.

--
...winston
msft mvp windows experience

". . .winston" schreef in bericht
...
Linea Recta wrote on 09/14/2015 12:40 PM:
After booting, every now and then my browser doesn't seem to work.
Sometimes solved after swiching off and on of modem.
But what is a real solution?

(I had modem FW update, multiple Windows 7 updates and Comodo internet
security updates)

Sometimes it boots without this problem.
I would surely like to have this solved.
It's taking me ages every evening to get started :-((


Fyi...it might be appropriate to let folks now 'which browser' is your
browser.

--


Both Chrome and IE refuse working today.



--


|\ /|
| \/ |@rk
\../
\/os

On 14/09/2015 17:40, Linea Recta wrote:
After booting, every now and then my browser doesn't seem to work.
Sometimes solved after swiching off and on of modem.
But what is a real solution?

(I had modem FW update, multiple Windows 7 updates and Comodo internet
security updates)

Sometimes it boots without this problem.
I would surely like to have this solved.
It's taking me ages every evening to get started :-((


Does anything work which requires internet access (email, usenet, etc.)
or is it all dead?

When the problem occurs, what lights are lit on your router?

What DNS servers are you using?
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.

"Roger Mills" schreef in bericht
...
On 14/09/2015 17:40, Linea Recta wrote:
After booting, every now and then my browser doesn't seem to work.
Sometimes solved after swiching off and on of modem.
But what is a real solution?

(I had modem FW update, multiple Windows 7 updates and Comodo internet
security updates)

Sometimes it boots without this problem.
I would surely like to have this solved.
It's taking me ages every evening to get started :-((


Does anything work which requires internet access (email, usenet, etc.)


Email and usenet seem to work. (although images in email appear not or VERY
slow.


or is it all dead?

When the problem occurs, what lights are lit on your router?


Power DSL and WLAN (as usual)



What DNS servers are you using?



preferred DNS
194.109.6.66
194.109.9.99




--


|\ /|
| \/ |@rk
\../
\/os

Linea Recta wrote:

After booting, every now and then my browser doesn't seem to work.
Sometimes solved after swiching off and on of modem.
But what is a real solution?

(I had modem FW update, multiple Windows 7 updates and Comodo internet
security updates)

Sometimes it boots without this problem.
I would surely like to have this solved.
It's taking me ages every evening to get started :-((

------------------------------------------------
Deze webpagina is niet beschikbaar

ERR_NAME_NOT_RESOLVED
Opnieuw ladenDetails verbergen
De server op www.telegraaf.nl kan niet worden gevonden, omdat de DNS-lookup
is mislukt. DNS is de netwerkservice die de naam van een website vertaalt in
het internetadres. Deze fout wordt meestal veroorzaakt door een verbroken
internetverbinding of een verkeerd geconfigureerd netwerk. Deze kan ook
worden veroorzaakt door een niet reagerende DNS-server of een firewall die
de toegang van Google Chrome tot het netwerk blokkeert.
Een gecacht exemplaar van http://www.telegraaf.nl/ openen
------------------------------------------------

Are you trying other web sites or is it just www.telegraaf.nl that you
cannot access?

Instead using the the FQDN (fully qualified domain name), I tried
connecting using their IP address (http://217.196.36.3/). That got "403
no such site". http://www.telegraaf.nl/ works for me. Looks like this
web site is using a web hoster who uses the hostname to select which
site they are hosting. You have to use a hostname to get to the
webhosted site rather than an IP address (which goes to the webhoster
but doesn't let them know to which of their webhosted sites to transfer
the connection).

In a command shell (cmd.exe), can you trace to the site? For example:

tracert www.telegraaf.nl

Or does the trace die before reaching the site?

Have you tried disabling Comodo Internet Suite (or just their firewall)?
Might require a reboot to truly get Comodo Firewall out of the way.

Linea Recta wrote:
"Roger Mills" schreef in bericht

What DNS servers are you using?

preferred DNS
194.109.6.66
194.109.9.99

Do you enter those in Windows manually ?

I leave my Windows networking set to automatic, and
my local DNS queries are sent to my 4 port home router
box at gateway 192.168.2.1 . The router has queried
the ISP and obtained a primary and secondary IP of
the ISP DNS server. That's what the router box
forwards my requests to. And if the ISP chooses to change
those, then the router takes care of the details
and I don't have to manage the values within
a Windows control panel at all. I leave my DNS
set to automatically acquire it.

With my old ISP, I did manage DNS IP addresses manually.
And that's because the old ISP had two annoying habits.

1) Reboot both the primary and secondary DNS servers at
the same time, causing a 15 minute outage.
2) Operate with the primary DNS resolver dead, and the
secondary one still running. Windows it too dumb to
preferentially select the secondary one, so if the
primary fails, each DNS request continues to be sent
to the primary first, the primary times out, then and only
then is the request sent to the secondary server. This
causes web surfing to slow down a lot.

So in your example, if I encountered (2) with the old ISP,
I would change the order of the DNS in the Windows
control panel

194.109.9.99
194.109.6.66

so that the secondary would be selected first, assuming
"66" was dead.

With the current ISP, this isn't necessary, as the DNS
resolution isn't handled in such a way.

My old ISP had 50 different DNS server pairs. My new ISP
chooses to hide all the details, so only the one address
is necessary at their end, and their network infrastructure
takes care of load balancing and distribution. So I no longer
have to fix it manually. You cannot tell when my current
ISP reboots DNS, as the fail-over inside their network
takes care of things for us.

So in my Windows, DNS is set to Automatic, and Windows
goes to 192.168.2.1 (my gateway) with its DNS requests,
and the router has the (well-known) ISP primary and
secondary values. And those values are fetched when the
ADSL connection is set up. And I don't have to interact
with it at all, because the ISP automation seems to work
perfectly well.

Windows 192.168.2.1 effectively

4 port router dns.myispname.whatever
dns2.myispname.whatever

And the latter two are taken care of within the
network of my ISP. I have no idea what hardware hides
behind the addresses provided, because they've never
failed, and analysis has never been necessary.

You can switch to Google DNS at 8.8.8.8 in Windows,
if you're stuck for a good DNS upstream choice.
Running this 8.8.8.8 server, costs Google some money,
but on the other hand, they get to track your IP requests.
For whatever value that has. You could run with
8.8.8.8 for a while and see if it helps.

https://en.wikipedia.org/wiki/Google_Public_DNS

Paul

"Paul" schreef in bericht
...
Linea Recta wrote:
"Roger Mills" schreef in bericht

What DNS servers are you using?

preferred DNS
194.109.6.66
194.109.9.99

Do you enter those in Windows manually ?


Yes that's what I did for a long time. Sometimes it worked, sometimes it
didn't. Very annoying as I had my own agenda to do some work this evening.
Now I have struggled the whole evening trying to solve something I don't
know enough about. This is all the Windows 7 computer, connected by cable.
BTW the notebook connected by wifi to the same modem works fine all the
time. No browser problems.

Because I sometimes want to run an FTP server I had set a static IP. Somehow
I figured these out long time ago. I kept the ipv4 settings:

ip adres 192.168.178.30
subnet masker 255.255.255.0
standard gateway 192.168.178.1

pref dns server 194.109.6.66
alt dns server 194.109.9.99




I leave my Windows networking set to automatic, and
my local DNS queries are sent to my 4 port home router
box at gateway 192.168.2.1 . The router has queried
the ISP and obtained a primary and secondary IP of
the ISP DNS server. That's what the router box
forwards my requests to. And if the ISP chooses to change
those, then the router takes care of the details
and I don't have to manage the values within
a Windows control panel at all. I leave my DNS
set to automatically acquire it.


OK, as an experiment I set all ipv4 entries to automatic (ipv6 was already
set to automatic) and rebooted.
Now the browser has internet access again (and reacting much faster!)
Nice, but what am I going to do when I need the FTP server?


I hope to dig into the rest tomorrow.


Thanks very much!

--


|\ /|
| \/ |@rk
\../
\/os

On 9/14/2015 9:40 AM, Linea Recta wrote:
After booting, every now and then my browser doesn't seem to work.
Sometimes solved after swiching off and on of modem.
But what is a real solution?

(I had modem FW update, multiple Windows 7 updates and Comodo internet
security updates)

Sometimes it boots without this problem.
I would surely like to have this solved.
It's taking me ages every evening to get started :-((

When my browser sporadically froze, I would disable my Internet
connection and then re-enable it. I did not have to reboot my PC.
Although I did not have to reboot my router or modem, this indicated a
problem with one of them.

I do not remember which of them I replaced (I think it was the router).
Since I made a replacement well over a year ago, I have not had this
problem.

--
David E. Ross

The Crimea is Putin's Sudetenland.
The Ukraine will be Putin's Czechoslovakia.
See http://www.rossde.com/editorials/edtl_PutinUkraine.html.

On 14/09/2015 23:33, Linea Recta wrote:
"Paul" schreef in bericht
...
Linea Recta wrote:
"Roger Mills" schreef in bericht

What DNS servers are you using?

preferred DNS
194.109.6.66
194.109.9.99

Do you enter those in Windows manually ?


Yes that's what I did for a long time. Sometimes it worked, sometimes it
didn't. Very annoying as I had my own agenda to do some work this evening.
Now I have struggled the whole evening trying to solve something I don't
know enough about. This is all the Windows 7 computer, connected by cable.
BTW the notebook connected by wifi to the same modem works fine all the
time. No browser problems.

Because I sometimes want to run an FTP server I had set a static IP.
Somehow I figured these out long time ago. I kept the ipv4 settings:

ip adres 192.168.178.30
subnet masker 255.255.255.0
standard gateway 192.168.178.1

pref dns server 194.109.6.66
alt dns server 194.109.9.99




I leave my Windows networking set to automatic, and
my local DNS queries are sent to my 4 port home router
box at gateway 192.168.2.1 . The router has queried
the ISP and obtained a primary and secondary IP of
the ISP DNS server. That's what the router box
forwards my requests to. And if the ISP chooses to change
those, then the router takes care of the details
and I don't have to manage the values within
a Windows control panel at all. I leave my DNS
set to automatically acquire it.


OK, as an experiment I set all ipv4 entries to automatic (ipv6 was already
set to automatic) and rebooted.
Now the browser has internet access again (and reacting much faster!)
Nice, but what am I going to do when I need the FTP server?

I have a similar situtation here. Have a dynamic IP address, but we have
a server, which is a web server and FTP server.And more. Also on this
server it requires DHCP to get it's IP address and the DNS addresses
from the router. On the router a reservation is made, based on the MAC
address of the server, so the server gets the same IP address all the time.
Because we have a dynamic IP address, I use DynDNS to make sure our
server keeps working, even when our IP address might change. It's worth
wile looking on the site of DynDNS. They have free services there, but I
choose for a subscription.

Fokke


I hope to dig into the rest tomorrow.


Thanks very much!

On 14/09/2015 18:58, Linea Recta wrote:
"Roger Mills" schreef in bericht
...



What DNS servers are you using?



preferred DNS
194.109.6.66
194.109.9.99



That could be your problem! I can't get a PING response from either of
those.

Try the OpenDNS addresses instead:
208.67.222.222 and
208.67.220.220

--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.

Roger Mills wrote:
On 14/09/2015 18:58, Linea Recta wrote:
"Roger Mills" schreef in bericht
...



What DNS servers are you using?



preferred DNS
194.109.6.66
194.109.9.99



That could be your problem! I can't get a PING response from either of
those.

Try the OpenDNS addresses instead:
208.67.222.222 and
208.67.220.220

What if the DNS servers only respond to ISP-vetted nodes ?

Paul

On 15/09/2015 10:57, Paul wrote:
Roger Mills wrote:
On 14/09/2015 18:58, Linea Recta wrote:
"Roger Mills" schreef in bericht
...



What DNS servers are you using?



preferred DNS
194.109.6.66
194.109.9.99



That could be your problem! I can't get a PING response from either of
those.

Try the OpenDNS addresses instead:
208.67.222.222 and
208.67.220.220

What if the DNS servers only respond to ISP-vetted nodes ?

Paul

Are there any like that? I'm sure that the OpenDNS servers will respond
to anyone.
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.

On Tue, 15 Sep 2015 16:38:32 +0100, Roger Mills
wrote:

On 15/09/2015 10:57, Paul wrote:

What if the DNS servers only respond to ISP-vetted nodes ?

Paul

Are there any like that?

I think most ISP DNS servers are like that, as in, configured to respond
only to requests that originate from allowed subnets.

I'm sure that the OpenDNS servers will respond to anyone.

They have 'open' right in their name. ;-)

--

Char Jackson

On 9/14/2015 10:58 AM, Linea Recta wrote:
"Roger Mills" schreef in bericht
...
On 14/09/2015 17:40, Linea Recta wrote:
After booting, every now and then my browser doesn't seem to work.
Sometimes solved after swiching off and on of modem.
But what is a real solution?

(I had modem FW update, multiple Windows 7 updates and Comodo internet
security updates)

Sometimes it boots without this problem.
I would surely like to have this solved.
It's taking me ages every evening to get started :-((


Does anything work which requires internet access (email, usenet, etc.)


Email and usenet seem to work. (although images in email appear not or VERY
slow.


or is it all dead?

When the problem occurs, what lights are lit on your router?


Power DSL and WLAN (as usual)



What DNS servers are you using?



preferred DNS
194.109.6.66
194.109.9.99

If the problem is truly with DNS and not with a failing modem or router,
I suggest using Domain Name Speed Benchmark from
https://www.grc.com/dns/benchmark.htm. This will identify servers
that are dead, respond with errors, or launch advertisements when a bad
domain is submitted. It will also rank DNSes by their response speeds.
I use it about once a month to see if I should change the DNS settings
in my router.

--
David E. Ross

Why do we tolerate political leaders who
spend more time belittling hungry children
than they do trying to fix the problem of
hunger? http://mazon.org/