🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.dcom.modems.cable
Article #615

Re: New AT&T Broadband Internet DHCP problem!!

#615
From: Hakeem
Date: Sat, 15 Dec 2001 17:34
79 lines
4136 bytes
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...
Technical Details
Message-ID: <cQLS7.2048$KY.91203@rwcrnsc54>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!wn4feed!wn1feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc54.POSTED!not-for-mail
References: <Xns916EE6793ADD4aphotographerhomecom@63.240.76.16>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10298d,9036b507d9187c3d
X-Google-Attributes: gid10298d,public
X-Google-Thread: 113850,9036b507d9187c3d
X-Google-Attributes: gid113850,public
X-Google-Thread: 10f392,9036b507d9187c3d
X-Google-Attributes: gid10f392,public
X-Google-ArrivalTime: 2001-12-15 09:34:01 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!wn4feed!wn1feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc54.POSTED!not-for-mail
From: "Hakeem" <hodulate@attbi.com>
Newsgroups: comp.dcom.modems.cable,alt.cable-ip,cableinet.cable_modems
References: <Xns916EE6793ADD4aphotographerhomecom@63.240.76.16>
Subject: Re: New AT&T Broadband Internet DHCP problem!!
Lines: 81
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <cQLS7.2048$KY.91203@rwcrnsc54>
NNTP-Posting-Host: lOLS7-35866-KY-90924@rwcrnsc54
X-Complaints-To: abuse@attbi.com
X-Trace: rwcrnsc54 1008437640 lOLS7-35866-KY-90924@rwcrnsc54 (Sat, 15 Dec 2001 17:34:00 GMT)
NNTP-Posting-Date: Sat, 15 Dec 2001 17:34:00 GMT
Organization: AT&T Broadband
Date: Sat, 15 Dec 2001 17:34:00 GMT