installed XP updates, no longer have DNS service

  • Thread starter Thread starter David Teague
  • Start date Start date
D

David Teague

PLEASE both post a reply here, and COPY the reply by EMAIL
to (e-mail address removed), since I cannot receive mail at this email
address ([email protected]) at all.


The subject says almost all of: THE PROBLEM:

I installed the updates that MS said were necessary (listed below)
I then rebooted pre instruction, and voila! I could not connect to
my mail server with Outlook Express nor to any domain name with
IE.

I can connect to the ISP, but neither Outlook Express nor IE
work. IE will work if I specify an IP number, but not a domain
name. No browser links connect. OEx fails to find the mail
server, but I can ping the mail server by IP number.

When I use nslookup, the DNS server specified in the setup is not
used. When I tell nslookup to use a known good DNS server,
nslookup times out.

My ISP says I am connected. He specified Knowledge base article
318378, "Reinstall or Repair IE and Outlook Express"which I read.

I have run spybot and ad-aware, I have Norton AV running on the
machine with latest updates. My ISP has gone through the settings
with me, twice to be sure that nothing is wrong there.

I want someone who knows XP either to recommend another
course of action or ask questions to confirm that reinstalling IE and
OEx is a necessary course of action. He says that the browser and
other applications are not being advised that the connection is made.
It appears to me that something is stopping the domain name service
software locally.

Patches Applied:
Cumulative Security Update for IE6 SP1 KB832894
Security Update for Windows XP KB828028
Security Update for Microsoft Windows XP KB825229
Critical Update for Microsoft Windows Media Player Script Commands KB828026
Security Update for Microsoft Windows XP KB 823182
Security Update for Microsoft Windows XP KB82414
Security Update for Microsoft Windows XP KB810217

Many thanks!

--David Teague
 
How to Troubleshoot Possible Causes of Internet Connection Problems
http://support.microsoft.com/default.aspx?scid=kb;en-us;314095&Product=winxp

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect your PC!
http://www.microsoft.com/security/protect/

-------------------------------------------------------------------------------

|
| The subject says almost all of: THE PROBLEM:
|
| I installed the updates that MS said were necessary (listed below)
| I then rebooted pre instruction, and voila! I could not connect to
| my mail server with Outlook Express nor to any domain name with
| IE.
|
| I can connect to the ISP, but neither Outlook Express nor IE
| work. IE will work if I specify an IP number, but not a domain
| name. No browser links connect. OEx fails to find the mail
| server, but I can ping the mail server by IP number.
|
| When I use nslookup, the DNS server specified in the setup is not
| used. When I tell nslookup to use a known good DNS server,
| nslookup times out.
|
| My ISP says I am connected. He specified Knowledge base article
| 318378, "Reinstall or Repair IE and Outlook Express"which I read.
|
| I have run spybot and ad-aware, I have Norton AV running on the
| machine with latest updates. My ISP has gone through the settings
| with me, twice to be sure that nothing is wrong there.
|
| I want someone who knows XP either to recommend another
| course of action or ask questions to confirm that reinstalling IE and
| OEx is a necessary course of action. He says that the browser and
| other applications are not being advised that the connection is made.
| It appears to me that something is stopping the domain name service
| software locally.
|
| Patches Applied:
| Cumulative Security Update for IE6 SP1 KB832894
| Security Update for Windows XP KB828028
| Security Update for Microsoft Windows XP KB825229
| Critical Update for Microsoft Windows Media Player Script Commands KB828026
| Security Update for Microsoft Windows XP KB 823182
| Security Update for Microsoft Windows XP KB82414
| Security Update for Microsoft Windows XP KB810217
|
| Many thanks!
|
| --David Teague
 
Security Update MS04-007 (KB828028) posted on Feb10 may be the culprit.
This was reported in the windowsupdate newsgroup (
http://tinyurl.com/3dfmn ). Flushing the Domain Name Service cache is not a
permanent solution, but at least it verifies where the problem lies. If you
have a Restore Point that far back, it is worth a try.

Sorry, no email reply.

Bee.
 
Bee

You mention flushing the domain name cache. The post you cite says to ru

ipconfig /flushdns at the command line

I have many restore points, one in fact just before each of the patches tha
I installed. Are you recommending that I roll back to just before the security
update KB828028 then reinstall the other updates

David Teague
(aka DavidBassPlayer
 
I flushed the dns name cache, but no joy. I still am able
to ping ip numbers but not domain names. There is no
name resolution.

Are there other suggestions other than backing up my data
and reinstalling?

I still can roll back to just prior to the updates, and tolerate
the risks that the updates are supposed to fix.

DavidBassPlayer,
Really bugged by this.
 
David, I have not found that manoeuvre helpful either, but my intermittent
server connection failure may be caused by something else. At present, it
is all quiet. I have no other plan for this intermittent ailment; until it
strikes again, I just have to put up with MS04-007.

Regards,

Bee.
 
I flushed the dns name cache, but no joy. I still am able
to ping ip numbers but not domain names. There is no
name resolution.

Are there other suggestions other than backing up my data
and reinstalling?
Click to expand...

Is there a firewall in the picture?
 
Yup, Microsoft's firewall, on the dialup, where those updates come from
Hasn't meant anything in the pas, but do you have suggestions?

--David Teague
 
Yup, Microsoft's firewall, on the dialup, where those updates come from
Hasn't meant anything in the pas, but do you have suggestions?
Click to expand...

XP's native firewall shouldn't be causing the problem, so I'll second the
other suggestion of using System Restore to a point before you installed
the updates. If all is well you can then reinstall them one at a time and
see what happens.
 
It is certainly preferable to roll back than to Reinstall/Repair IE/OEx
per KB 318378. I have that set of instructions printed out. THAT
would be a pill.

I'll roll my system back, if successful, then I'll download the patches
and apply them one at a time.

I am tempted to back up all the data, wipe and install Linux. I would
except that while Linux really is more stable, and less vulnerable to
malware, the user interface still isn't as good on the applications I
actually use as is the MS application interface.

Many thanks. I'll report the effects of my efforts.

David Teague
 
Thanks for the attempts to help me!

Finally, I got this licked. It was a flaky modem. I am guilty of a classic
logic error.
"Post hoc, proper hoc." which means "After this therefore because of this."
I had
just installed the MS security updates, and after rebooting, I had a
problem.

It was a modem that would let me connect but would not let me do anything.

Thankfully I had not done anything beyond remove and reinstall the network
protocols, which did nothing. My friend at the local computer store has a
bit
more of a hardware bent. When nothing worked but then we connected the
network, everything worked perfectly, he said all the software was working,
but
the modem was the only thing left.

Changing the modem fixed things.

David Teague, aka DavidBassPlayer
 
Excellent. Thanks for the feedback.

Bee.


David Teague said:
Thanks for the attempts to help me!

Finally, I got this licked. It was a flaky modem. I am guilty of a classic
logic error. "Post hoc, proper hoc." which means "After this therefore
because of this." I had just installed the MS security updates, and
after rebooting, I had a problem.

It was a modem that would let me connect but would not let me do anything.

Thankfully I had not done anything beyond remove and reinstall the network
protocols, which did nothing. My friend at the local computer store has a
bit more of a hardware bent. When nothing worked but then we connected
the network, everything worked perfectly, he said all the software was
working, but the modem was the only thing left.

Changing the modem fixed things.
Click to expand...
 
Finally, I got this licked. It was a flaky modem. I am guilty of a
classic logic error.
"Post hoc, proper hoc." which means "After this therefore because of
this."
I had
just installed the MS security updates, and after rebooting, I had a
problem.
Click to expand...

Ah, bitten by the old non causa pro causa thing. Been there many times
myself. Glad you got it worked out.
 
Back
Top