|
Posted by Warren on April 12, 2005, 10:39 pm
If you were Registered and logged in, you could reply and use other advanced thread options
$Bill wrote:
> Being a programmer, ...
That's the other thing. Most users are not savvy enough to have any idea how
to troubleshoot a problem, let alone understand any results of their
troubleshooting.
I'd like to think that most people would have enough experience to try
rebooting their computer, but I'm not holding my breath. I have no delusions
that they'd know to reset their router and reboot, and know enough to do it
in the right order.
So if we're talking about the group of people who would know enough to reset
and reboot their equipment in the right order, and we don't have to worry
about those savvy enough to know how to manually set public DNS servers,
we're down to a pretty small group of people.
There might be a situation when it would be worth it to switch the DNS
servers that DHCP is serving, but I don't think that there would be many
cases in which you'd want to divert available engineers from fixing the
problem to setting-up a work-around that would benefit such a small number
of users.
Now I'm starting to get real curious about just what the heck is going on.
And why such a major problem has hit twice in less than a week. There's
probably a good story behind this.
--
Warren H.
==========
Disclaimer: My views reflect those of myself, and not my
employer, my friends, nor (as she often tells me) my wife.
Any resemblance to the views of anybody living or dead is
coincidental. No animals were hurt in the writing of this
response -- unless you count my dog who desperately wants
to go outside now.
Care for your landscape with Black and Decker cordless tools
http://www.holzemville.com/mall/blackanddecker/index.html
| 
NewsGroups 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map