🚀 go-pugleaf

Michael Feinberg wrote:
> In at least my region, there is a problem with the DNS server settings
being
> provided by the DHCP server. It is responding with 4 DNS servers, but only
> the first 2 are true DNS servers. The last two appear to be DHCP servers.
> The first 2 DNS servers appear to be timing out on requests. This is
causing
> secondary, and then tertiary servers to be queried. In my case, once DNS
> cycled to the third server I was toast as there was no way I could have a
> chance to resolve DNS again as the OS (Windows) doesn't reset to the
primary
> DNS server on it's own.

I think we have a winner!

And the reason why those of us with both 2000/XP and 9x/ME machines are only
seeing the problem on the 2000/XP machines but not the 9x/ME machines is
that 9x/ME apparently will go back to the primary DNS server first each
time, while 2000/XP will not reset.

I changed my DNS settings in XP to only specify the first two (the real) DNS
servers, and it appears to have resolved the issue.

Excellent!

> I did call in this to AT&T, but I dount it will get forwarded to whoever
> would need to see it. Eventually they will figure it out...

Well I certainly hope they will figure this out!

--
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.

Thanks for the fix!  Worked for me :)
Now if only AT&T can get it fixed.


> In at least my region, there is a problem with the DNS server settings
being
> provided by the DHCP server. It is responding with 4 DNS servers, but only
> the first 2 are true DNS servers. The last two appear to be DHCP servers.
> The first 2 DNS servers appear to be timing out on requests. This is
causing
> secondary, and then tertiary servers to be queried. In my case, once DNS
> cycled to the third server I was toast as there was no way I could have a
> chance to resolve DNS again as the OS (Windows) doesn't reset to the
primary
> DNS server on it's own.
>

mfeinberg@NotAtHome.com (Michael Feinberg) wrote in
<Xns916EE6793ADD4aphotographerhomecom@63.240.76.16>: 

>The first 2 DNS servers appear to be timing out on requests. This is
>causing secondary, and then tertiary servers to be queried. In my case,
>once DNS cycled to the third server I was toast as there was no way I
>could have a chance to resolve DNS again as the OS (Windows) doesn't
>reset to the primary DNS server on it's own.

Good catch, but I think you've misdiagnosed the failure state. If the 3rd 
and 4th servers failed to respond, 2k/XP (not NT, which acts like 9x) should 
cycle back to the 1st server. Instead, I think the 3rd and 4th servers are 
likely to be real DNS servers but unconfigured. That would allow them to 
answer negatively to all queries, which would keep your client "stuck" to 
them. (Ie. they answer, therefore they must be authoritative, and there's no 
need to cycle back to #1.)

Try using nslookup with each of the 4 addresses and see what answers each 
gives. Better, use the free Sam Spade for Windows (http://www.samspade.org/) 
to query each server, as it gives more diagnostic information. I'll bet you 
find live servers on the 3rd and 4th address but they always answer in the 
negative.

Here's the 3 servers I get from DHCP:

216.148.227.68 204.127.202.4 12.242.17.50

The first two successfully return a positive answer to a query for 
www.msn.com. The last reports "NXDOMAIN" (ie. non-existent domain).

(I first ran into this problem on my company LAN, when a 2nd server didn't 
have all the domains served by the primary. My Win2k clients would start 
failing to resolve if network congestion caused them to fail over to the 
secondary. This feature is intended to automatically balance load on the 
DNS servers, but it screws you if your servers aren't identically 
configured.)

This makes some level of sense. I was experiencing the symptoms on both my
Win2k machines. I have a Linksys router but was manually setting the DNS
entires in both win2k computer since I use port forwarding. I also tried one
machine just using DHCP from the Linksys and I still had problems. It wasn't
until I set my Win2k machines with only one DNS entry (just pointed to the
Linksys router address) that my problems went away completely. Appently the
Linksys knows enough to forward DNS packets on to a DNS server. And
apparently it knows enough to always try the first DNS initially.
Interesting.

Wes

"Michael Feinberg" <mfeinberg@NotAtHome.com> wrote in message
news:Xns916EE6793ADD4aphotographerhomecom@63.240.76.16...
> In at least my region, there is a problem with the DNS server settings
being
> provided by the DHCP server. It is responding with 4 DNS servers, but only
> the first 2 are true DNS servers. The last two appear to be DHCP servers.
> The first 2 DNS servers appear to be timing out on requests. This is
causing
> secondary, and then tertiary servers to be queried. In my case, once DNS
> cycled to the third server I was toast as there was no way I could have a
> chance to resolve DNS again as the OS (Windows) doesn't reset to the
primary
> DNS server on it's own.
>
>
> SYMPTOMS:
>
> You will have full Internet access, but at some point will loose the
ability
> to reach any servers. Programs such as AIM or ICQ will continue to
function
> and you still still have an connection indicated on your cable modem.
>
> What has happened is you have lost the ability to resolve DNS names. To
> demonstrate this you could put the following IP address in your browser
and
> it will work: 207.68.171.253 (which is WWW.MSN.COM)
>
> What is happening is a request to resolve a DNS name is timing out. When
> this happen the next DNS server in line is used, and so on. The OS does
not
> reset back to the original server unless rebooted (which is why your
system
> would work if support told you to reboot). The same is true if you release
> and renew your IP settings (if that means anything to you, it's not
> important anyway)
>
>
> RESOLUTION:
>
> *NT / WIN2K / Win XP?
> I corrected the problem by disabling DHCP supplied DNS settings and
manually
> set the first 2 DNS servers that had been supplied by DHCP.
>
> (alternate)
> If you prefer not to do this, you can just run IPCONFIG /RENEW from a
> command line and your DNS should be restored for a while.
>
> *Win9x / Win ME
> If I recall, this is not an option in Win9x as the DHCP response overrides
> the configured settings.
>
> What you can do is launch WINIPCFG
> select the SHOW ALL button and write down the following:
> IP ADDRESS
> SUBNET MASK
> GATEWAY
> and the FIRST TWO DNS servers
>
> Now change yor TCP/IP settings to manual and configure using the numbers
you
> noted.
>
> (alternate)
> You still launch WINIPCFG, but just click the RENEW ALL button and DNS
will
> be restored for a while.
>
>
> I did call in this to AT&T, but I dount it will get forwarded to whoever
> would need to see it. Eventually they will figure it out...

Thanks for the info.  I wrote down all the info but your mentioned the first
2 DNS server but my config shows primary WINS server and secondary WINS
server which are both blank.

--

Russ d8-)

Russ's Signature Page @ http://home.attbi.com/~rblwood/signature.html

Russ wrote:
> Thanks for the info.  I wrote down all the info but your mentioned the
first
> 2 DNS server but my config shows primary WINS server and secondary WINS
> server which are both blank.

WINS servers are irrelevant to your situation. ATTBI doesn't have them, and
doesn't need them. Totally irrelevant.

DNS servers are listed near the top. Only one number shows at a time. Press
the " ... " button next to that number to cycle through all the DNS servers.

--
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.

Yes, I cycled through and found 4.  You mentioned just doing through 2.  How
might I do that?

--

Russ d8-)

Russ's Signature Page @ http://home.attbi.com/~rblwood/signature.html

Russ wrote:
> Yes, I cycled through and found 4.  You mentioned just doing through 2.
How
> might I do that?
>

Start > Settings > Control Panel > Network

Click on "TCP/IP" (or "TCP/IP ->(network card name)"), and then press
Properties.

Click on the DNS Settings tab. Choose Enable DNS.

Hostname is generally the same as your computer name (from the
Identification tab in Network properties), but doesn't have to be. Domain
would be attbi.com. Then type in the first address, and press Add. Type in
the second address, and press Add. Press OK. Press OK again.

You might be asked for your Windows 9x CD, or to point to the folder where
the CAB files for your OS are. (Or the files may be found automatically.)
After that you will need to reboot your computer. After rebooting, go back
to WINIPCFG and check your results.

--
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.

Made the changes.  Guess we will just have to monitor this to see if things
speed up.  I did notice that my there was a check mark in a box called
NetBIOS Resolution Use DSN that wasn't checked before.  Thanks for all the
help

--

Russ d8-)

Russ's Signature Page @ http://home.attbi.com/~rblwood/signature.html

Your fix works for me Michael, thank you, I added DNS numbers to the TCP/IP
setting on my XP machine.  I left the router with DHCP enabled and no DNS
entered.  Everything works fine, but I wonder what will happen when the
connection expires.  I ran an ipconfig/release and then an ipconfig/renew to
test and it still works, but wondering if this is a permanent solution as I
am not always around to reset things.  I also wonder why ATT is not
addressing this situation and we need to gather fixes from fellow
users/consumers.
Thanks again for the info.

Andy

I found a better solution (and the reason why we need a solution at
all) regarding the recent DNS problems. As it turns out, AT&T *is*
actually serving up DNS!! Problem is, they're changing which server is
doing this *very* often - much more often than Windows 2000 or XP
expects it. Seems that these latest flavors of Windows have a little
service running known as "DNS caching". It's supposed to lock onto a
DNS server (dynamically assigned, in AT&T's case) and use that server
for the next 300 seconds (the default setting - hackable in the
registry). The idea is, if your machine doesn't have to sense which
DNS server is being assigned to it each time you click a link, your
online experience should be marginally faster. Problem is, AT&T is
probably switching between DNS servers faster than the expected 300
seconds and this explains why I can only get to about 7 sites at a
time. If I leave it alone for a few minutes, I can grab another few
pages - or I can force this process by refreshing my connection.
 
All I had to do is go into "Services" and change DNS caching from
Automatic to Manual and stop the service. DNS is once again set to
dynamically grab whatever AT&T is throwing at me and pages are once
again flying! My speed is still nailed at about 1.5mb/sec and I have
the "piece of mind" of knowing that AT&T is at least providing the
service they're being paid to provide.
 
Win9x (Linux? Mac?) doesn't suffer from this new "feature" in 2000 or
XP. While disabling it as I have is supposed to decrease web page
flipping (since the system has to sense the DNS server each time), I
honestly haven't noticed any difference. At least I have connectivity
for all apps again!
 
Just in case you're wondering, I found mention of this little goodie
at: http://www.dslreports.com/forum/remark,1932223~root=attbi~mode=flat
 
Please forward this tidbit to anyone you know might benefit from it.

"A Schwartz" <aschwartz12@attbi.com> wrote in message news:<6BWP7.7359$ER5.259417@rwcrnsc52>...
> Your fix works for me Michael, thank you, I added DNS numbers to the TCP/IP
> setting on my XP machine.  I left the router with DHCP enabled and no DNS
> entered.  Everything works fine, but I wonder what will happen when the
> connection expires.  I ran an ipconfig/release and then an ipconfig/renew to
> test and it still works, but wondering if this is a permanent solution as I
> am not always around to reset things.  I also wonder why ATT is not
> addressing this situation and we need to gather fixes from fellow
> users/consumers.
> Thanks again for the info.
> 
> Andy

Jeff wrote:
> I found a better solution (and the reason why we need a solution at
> all) regarding the recent DNS problems. As it turns out, AT&T *is*
> actually serving up DNS!! Problem is, they're changing which server is
> doing this *very* often - much more often than Windows 2000 or XP
> expects it.

ROFLO!  Re-read what you just wrote. When you say "much more often than
Windows 2000 or XP expects it", do you mean more often than once every 4
days? My lease is for 4 days. Are you saying that they change DNS servers
more often than that? Then explain why it wouldn't affect other OS's?

> Seems that these latest flavors of Windows have a little
> service running known as "DNS caching". It's supposed to lock onto a
> DNS server (dynamically assigned, in AT&T's case) and use that server
> for the next 300 seconds (the default setting - hackable in the
> registry). The idea is, if your machine doesn't have to sense which
> DNS server is being assigned to it each time you click a link, your
> online experience should be marginally faster. Problem is, AT&T is
> probably switching between DNS servers faster than the expected 300
> seconds and this explains why I can only get to about 7 sites at a
> time. If I leave it alone for a few minutes, I can grab another few
> pages - or I can force this process by refreshing my connection.

Okay. Let's try a better explaination:

AT&T is sending along up to 4 server addresses for DNS servers when you get
your lease. Only the first two work. When Windows 9x/ME/NT come to the ones
that don't work, they cycle through to the ones that do work. Windows
2000/XP stay "stuck" on the bad server for 5 minutes.

There are at least four ways we can overcome this problem until AT&T fixes
it.

1. Hack the Registry, to reduce the caching time to near zero, effectively
turning off DNS caching. (Will you remember to undo this hack when the time
comes?)

2. Go into Services and disable DNS caching. (Setting it to manual simply
stops it from loading at boot, but it will load when an application asks for
it to load.)

3. Specify only the two working DNS servers in the connection settings.

4. Specify the router (if you're using one) as your only DNS server in the
connection settings. (The router doesn't get "stuck" on the bad server.)


Each method has it's pro's and con's. If you're looking to save every
micro-milli-nano second you can, option 3 has a slight edge. If you're
concerned that the real DNS servers will change soon, option number 4 would
be the best. If you want to just forget about using DNS caching, then
options 1 and 2 will do that, but option 2 is probably better than option 1
because it actually turns the feature off rather than just crippling it.

My personal choice would be 3 or 4, depending upon whether you have a
router, and if that router will actually handle DNS resolution.

--
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.

Never anonymous Bud wrote:
> Using crayons of red and green, "Warren H." <wholzem@hotmail.com>
scribbled
>
> >ROFLO!  Re-read what you just wrote. When you say "much more often than
> >Windows 2000 or XP expects it", do you mean more often than once every 4
> >days? My lease is for 4 days. Are you saying that they change DNS servers
> >more often than that? Then explain why it wouldn't affect other OS's?
>
> You're obviously confusing DNS with DHCP.
>

No, you're missing the point.

The DNS servers are configured by DHCP. If my lease doesn't expire for 4
days, then I'm not going to get a new set of DNS servers to use for 4 days.
And that's going to apply to any OS I use.

So if AT&T is changing their DNS servers "much more often than Windows 2000
or XP expects it", then they would also be changing those servers more often
than any other OS expects it because we're all using 4 day leases.

The DNS servers are NOT changing "much more often than Windows 2000 or XP
expects it". Or more often than any other OS expects it. As a matter of
fact, I've had the same DNS servers since ATTBI came online last Saturday
morning.

Once more for those in the back rows: What DNS servers are to be used is
something that is delivered in the lease you get through DHCP. Thus your DNS
servers can't change until you get a new lease regardless of what OS you're
using -- unless you go in there and manually set different DNS settings from
what was delivered through DHCP.


--
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.

"Warren H." <wholzem@hotmail.com> wrote in message
news:vQcQ7.15019$ER5.265784@rwcrnsc52...
> Jeff wrote:
> > I found a better solution (and the reason why we need a solution at
> > all) regarding the recent DNS problems. As it turns out, AT&T *is*
> > actually serving up DNS!! Problem is, they're changing which server is
> > doing this *very* often - much more often than Windows 2000 or XP
> > expects it.
>
> ROFLO!  Re-read what you just wrote. When you say "much more often than
> Windows 2000 or XP expects it", do you mean more often than once every 4
> days? My lease is for 4 days. Are you saying that they change DNS servers
> more often than that? Then explain why it wouldn't affect other OS's?
>

 Hmm, my lease seems to be for 24 hours.
 win 2K Pro, SP2

> > Seems that these latest flavors of Windows have a little
> > service running known as "DNS caching". It's supposed to lock onto a
> > DNS server (dynamically assigned, in AT&T's case) and use that server
> > for the next 300 seconds (the default setting - hackable in the
> > registry). The idea is, if your machine doesn't have to sense which
> > DNS server is being assigned to it each time you click a link, your
> > online experience should be marginally faster. Problem is, AT&T is
> > probably switching between DNS servers faster than the expected 300
> > seconds and this explains why I can only get to about 7 sites at a
> > time. If I leave it alone for a few minutes, I can grab another few
> > pages - or I can force this process by refreshing my connection.
>
> Okay. Let's try a better explaination:
>
> AT&T is sending along up to 4 server addresses for DNS servers when you
get
> your lease. Only the first two work. When Windows 9x/ME/NT come to the
ones
> that don't work, they cycle through to the ones that do work. Windows
> 2000/XP stay "stuck" on the bad server for 5 minutes.
>
> There are at least four ways we can overcome this problem until AT&T fixes
> it.
>
> 1. Hack the Registry, to reduce the caching time to near zero, effectively
> turning off DNS caching. (Will you remember to undo this hack when the
time
> comes?)
>
> 2. Go into Services and disable DNS caching. (Setting it to manual simply
> stops it from loading at boot, but it will load when an application asks
for
> it to load.)
>
> 3. Specify only the two working DNS servers in the connection settings.
>
> 4. Specify the router (if you're using one) as your only DNS server in the
> connection settings. (The router doesn't get "stuck" on the bad server.)
>
>
> Each method has it's pro's and con's. If you're looking to save every
> micro-milli-nano second you can, option 3 has a slight edge. If you're
> concerned that the real DNS servers will change soon, option number 4
would
> be the best. If you want to just forget about using DNS caching, then
> options 1 and 2 will do that, but option 2 is probably better than option
1
> because it actually turns the feature off rather than just crippling it.
>
> My personal choice would be 3 or 4, depending upon whether you have a
> router, and if that router will actually handle DNS resolution.
>
> --
> 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.
>
>
>
>

 I goofed in my last reply. Actually, my lease shows 12 hours, not 24.
 I overlooked that it started at PM and expires at AM...
 this could be my settings, but I dunno.
 It has not been a problem anyway.

"Warren H." <wholzem@hotmail.com> wrote in message
news:bReQ7.14636$L51.31622@rwcrnsc54...
> Never anonymous Bud wrote:
> > Using crayons of red and green, "Warren H." <wholzem@hotmail.com>
> scribbled
> >
> > >ROFLO!  Re-read what you just wrote. When you say "much more often than
> > >Windows 2000 or XP expects it", do you mean more often than once every
4
> > >days? My lease is for 4 days. Are you saying that they change DNS
servers
> > >more often than that? Then explain why it wouldn't affect other OS's?
> >
> > You're obviously confusing DNS with DHCP.
> >
>
> No, you're missing the point.
>
> The DNS servers are configured by DHCP. If my lease doesn't expire for 4
> days, then I'm not going to get a new set of DNS servers to use for 4
days.
> And that's going to apply to any OS I use.
>
> So if AT&T is changing their DNS servers "much more often than Windows
2000
> or XP expects it", then they would also be changing those servers more
often
> than any other OS expects it because we're all using 4 day leases.
>
> The DNS servers are NOT changing "much more often than Windows 2000 or XP
> expects it". Or more often than any other OS expects it. As a matter of
> fact, I've had the same DNS servers since ATTBI came online last Saturday
> morning.
>
> Once more for those in the back rows: What DNS servers are to be used is
> something that is delivered in the lease you get through DHCP. Thus your
DNS
> servers can't change until you get a new lease regardless of what OS
you're
> using -- unless you go in there and manually set different DNS settings
from
> what was delivered through DHCP.
>
>
> --
> 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.
>
>
>

On 7 Dec 2001 11:22:41 -0800, JeffChapnet@hotmail.com (Jeff) wrote:

>All I had to do is go into "Services" and change DNS caching from
>Automatic to Manual and stop the service. DNS is once again set to
>dynamically grab whatever AT&T is throwing at me and pages are once
>again flying!

Could someone please explain how to do this?

I would call myself an "intermediate user":  not ready to go into
registries, probably, but if this is a "reasonable" approach....

You're information won't get forwarded becuase it's wrong.
The ATT network uses true DHCP, if you set your IP static you will not get
online for any longer than a day. Manually setting the DNS servers is also a
temp fix.

XP and Win2k has a service called "DNS Client" that affects the way your
system performs a DNS search.
Here's the fix:
Open control panel, go to Administrative Tools, open Computer Managment,
click Services and Applications, clickServices, double click DNS Client:
change startup type to manual, and change service status to stop.

Michael Feinberg <mfeinberg@NotAtHome.com> wrote in message
news:Xns916EE6793ADD4aphotographerhomecom@63.240.76.16...
> In at least my region, there is a problem with the DNS server settings
being
> provided by the DHCP server. It is responding with 4 DNS servers, but only
> the first 2 are true DNS servers. The last two appear to be DHCP servers.
> The first 2 DNS servers appear to be timing out on requests. This is
causing
> secondary, and then tertiary servers to be queried. In my case, once DNS
> cycled to the third server I was toast as there was no way I could have a
> chance to resolve DNS again as the OS (Windows) doesn't reset to the
primary
> DNS server on it's own.
>
>
> SYMPTOMS:
>
> You will have full Internet access, but at some point will loose the
ability
> to reach any servers. Programs such as AIM or ICQ will continue to
function
> and you still still have an connection indicated on your cable modem.
>
> What has happened is you have lost the ability to resolve DNS names. To
> demonstrate this you could put the following IP address in your browser
and
> it will work: 207.68.171.253 (which is WWW.MSN.COM)
>
> What is happening is a request to resolve a DNS name is timing out. When
> this happen the next DNS server in line is used, and so on. The OS does
not
> reset back to the original server unless rebooted (which is why your
system
> would work if support told you to reboot). The same is true if you release
> and renew your IP settings (if that means anything to you, it's not
> important anyway)
>
>
> RESOLUTION:
>
> *NT / WIN2K / Win XP?
> I corrected the problem by disabling DHCP supplied DNS settings and
manually
> set the first 2 DNS servers that had been supplied by DHCP.
>
> (alternate)
> If you prefer not to do this, you can just run IPCONFIG /RENEW from a
> command line and your DNS should be restored for a while.
>
> *Win9x / Win ME
> If I recall, this is not an option in Win9x as the DHCP response overrides
> the configured settings.
>
> What you can do is launch WINIPCFG
> select the SHOW ALL button and write down the following:
> IP ADDRESS
> SUBNET MASK
> GATEWAY
> and the FIRST TWO DNS servers
>
> Now change yor TCP/IP settings to manual and configure using the numbers
you
> noted.
>
> (alternate)
> You still launch WINIPCFG, but just click the RENEW ALL button and DNS
will
> be restored for a while.
>
>
> I did call in this to AT&T, but I dount it will get forwarded to whoever
> would need to see it. Eventually they will figure it out...

On Mon, 10 Dec 2001 04:29:20 GMT, "Phil Parker" <phlprkr@attbi.com>
wrote:

>
>XP and Win2k has a service called "DNS Client" that affects the way your
>system performs a DNS search.
>Here's the fix:
>Open control panel, go to Administrative Tools, open Computer Managment,
>click Services and Applications, clickServices, double click DNS Client:
>change startup type to manual, and change service status to stop.
>
Wow, and Billy wants ME to buy XP?!!

larry

So, you're saying that this won't work for ME?

--

Russ d8-)

Russ's Signature Page @ http://home.attbi.com/~rblwood/signature.html

On Mon, 10 Dec 2001 02:33:16 GMT, davidis4@home.com (David Silberberg)
wrote:

>On 7 Dec 2001 11:22:41 -0800, JeffChapnet@hotmail.com (Jeff) wrote:
>
>>All I had to do is go into "Services" and change DNS caching from
>>Automatic to Manual and stop the service. DNS is once again set to
>>dynamically grab whatever AT&T is throwing at me and pages are once
>>again flying!
>
>Could someone please explain how to do this?
>
>I would call myself an "intermediate user":  not ready to go into
>registries, probably, but if this is a "reasonable" approach....

start-run-mmc, file, add/remove snap in, click on services, add,
finish, close, ok, click on services, right click dns client, click
properties, change automatic to manual

On Mon, 10 Dec 2001 04:29:20 GMT, "Phil Parker" <phlprkr@attbi.com>
wrote:

>You're information won't get forwarded becuase it's wrong.
>The ATT network uses true DHCP, if you set your IP static you will not get
>online for any longer than a day. Manually setting the DNS servers is also a
>temp fix.
>
>XP and Win2k has a service called "DNS Client" that affects the way your
>system performs a DNS search.
>Here's the fix:
>Open control panel, go to Administrative Tools, open Computer Managment,
>click Services and Applications, clickServices, double click DNS Client:
>change startup type to manual, and change service status to stop.
>

Thank's for your help on this - seems to have worked.

Can someone answer this please,cant I just go into computer
management,services and applications, services, select DHCP client, then
select properties, then select the recovery tab then where its says
subsequent failures select (restart the service) instead of take no action.
Do you think this would fix it.......

I mean DNS client..........
"dj" <davej610@hotmail.com> wrote in message
news:KluS7.48677$wL4.359239@rwcrnsc51...
>
> Can someone answer this please,cant I just go into computer
> management,services and applications, services, select DHCP client, then
> select properties, then select the recovery tab then where its says
> subsequent failures select (restart the service) instead of take no
action.
> Do you think this would fix it.......
>
>

I noticed this same problem the same day my cable came back up.  I have
pretty much given up calling for support,
so I decided to use someone else DNS server that I know works for sure is
probably more reliable.  Haven't had any problems
since then.


"Michael Feinberg" <mfeinberg@NotAtHome.com> wrote in message
news:Xns916EE6793ADD4aphotographerhomecom@63.240.76.16...
> In at least my region, there is a problem with the DNS server settings
being
> provided by the DHCP server. It is responding with 4 DNS servers, but only
> the first 2 are true DNS servers. The last two appear to be DHCP servers.
> The first 2 DNS servers appear to be timing out on requests. This is
causing
> secondary, and then tertiary servers to be queried. In my case, once DNS
> cycled to the third server I was toast as there was no way I could have a
> chance to resolve DNS again as the OS (Windows) doesn't reset to the
primary
> DNS server on it's own.
>
>
> SYMPTOMS:
>
> You will have full Internet access, but at some point will loose the
ability
> to reach any servers. Programs such as AIM or ICQ will continue to
function
> and you still still have an connection indicated on your cable modem.
>
> What has happened is you have lost the ability to resolve DNS names. To
> demonstrate this you could put the following IP address in your browser
and
> it will work: 207.68.171.253 (which is WWW.MSN.COM)
>
> What is happening is a request to resolve a DNS name is timing out. When
> this happen the next DNS server in line is used, and so on. The OS does
not
> reset back to the original server unless rebooted (which is why your
system
> would work if support told you to reboot). The same is true if you release
> and renew your IP settings (if that means anything to you, it's not
> important anyway)
>
>
> RESOLUTION:
>
> *NT / WIN2K / Win XP?
> I corrected the problem by disabling DHCP supplied DNS settings and
manually
> set the first 2 DNS servers that had been supplied by DHCP.
>
> (alternate)
> If you prefer not to do this, you can just run IPCONFIG /RENEW from a
> command line and your DNS should be restored for a while.
>
> *Win9x / Win ME
> If I recall, this is not an option in Win9x as the DHCP response overrides
> the configured settings.
>
> What you can do is launch WINIPCFG
> select the SHOW ALL button and write down the following:
> IP ADDRESS
> SUBNET MASK
> GATEWAY
> and the FIRST TWO DNS servers
>
> Now change yor TCP/IP settings to manual and configure using the numbers
you
> noted.
>
> (alternate)
> You still launch WINIPCFG, but just click the RENEW ALL button and DNS
will
> be restored for a while.
>
>
> I did call in this to AT&T, but I dount it will get forwarded to whoever
> would need to see it. Eventually they will figure it out...

What server did you use to avoid the problems you were having, if I may ask.

--

Russ d8-)

Russ's Signature Page @ http://home.attbi.com/~rblwood/signature.html

I am using the DNS from the university I went attended, and I wouldn't want
to give that out because I don't want them to get a lot of traffic from AT&T
customers :), but what you can go is look for a big enough school around you
(most big schools use T3 lines) and do
an "nslookup" on the domain name (syntax is "nslookup <web address>).  That
should give you the dns server.  If you have any problems, let me know the
school and I can find it for you.

Good Luck.


"Russ" <rblwood@attbi.com> wrote in message
news:FQOS7.2985$KY.135238@rwcrnsc54...
> What server did you use to avoid the problems you were having, if I may
ask.
>
> --
>
> Russ d8-)
>
> Russ's Signature Page @ http://home.attbi.com/~rblwood/signature.html
>
>