🚀 go-pugleaf

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