[Essexboy]

Could you confirm that the DNS client is running in administrative tools > services

[Advertisements]

its setup as follows:
Startup: Automatic
Service status: Started

[jaydog11]

its setup as follows:
Startup: Automatic
Service status: Started

[Essexboy]

Well according to all I have read then this should not be happening, the only thing I can think of now is a limitation on threads. That would probably still enable windows updates but very little else

Could you now run the SP3 disc again to see if that helps

[Essexboy]

OK we have the eyes back on this again

There are a few more options to try .. The first is to run some commands we have done previously but in a specific sequence

From the command prompt type the following pressing enter after each line

ipconfig /release
ipconfig /flushdns
ipconfig /renew

If that fails then are you happy to go into the registry and also amend an ini file ?

If so then follow the instructions here

Starting at :

RESOLUTION

all the way down to

27.Restart your computer.

[jaydog11]

The article you have a link to says it is for a Windows Server 2003 domain controller?
When I pulle it up on my good XP laptop it says it is the article is for a different version of Windows?
I'm not sure what to do in step 1?

[jaydog11]

Man! Still didn't work. I am again trying to locate the proper recovery cd for this laptop. It may be the only wat to reset everything. The downside to that, if I can even get a cd, is that I have software on here that I no longer have the installation CDs for so I will lose a lot of stuff I use. It works fine except for the internet. I dont get it?

[Essexboy]

It worked on my XP system (I tried it out first)

However, a fresh thought.... There are a lot of people racking their brains over this one

At cmd prompt C:\>
type
netsh -c diag


then when that loads
type
show test

From what I have read and I may NOT be correct it will fail on the DNS
If so uninstall this update
KB951748

http://support.microsoft.com/kb/951748

reboot

and reinstall it and then test

[jaydog11]

Below is from the netsh -c diag:

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Show User>netsh -c diag
netsh diag>show test

Default Outlook Express Mail (Not Configured)

Default Outlook Express News (Not Configured)

Internet Explorer Web Proxy (Not Configured)

Loopback (127.0.0.1)
Loopback = 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=0
Reply from 127.0.0.1: bytes=32 time<1ms TTL=0
Reply from 127.0.0.1: bytes=32 time<1ms TTL=0
Reply from 127.0.0.1: bytes=32 time<1ms TTL=0
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Modems (TOSHIBA Software Modem)

Network Adapters
2. [00000011] Intel® PRO/Wireless 2200BG Network Connection
DefaultIPGateway = 192.168.1.1 Same Subnet
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=3
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=2ms TTL=2
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 1ms
DHCPServer = 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
DNSServerSearchOrder = 66.133.170.2
Pinging 66.133.170.2 with 32 bytes of data:
Reply from 66.133.170.2: bytes=32 time=46ms TTL=46
Reply from 66.133.170.2: bytes=32 time=43ms TTL=43
Reply from 66.133.170.2: bytes=32 time=42ms TTL=42
Reply from 66.133.170.2: bytes=32 time=42ms TTL=42
Ping statistics for 66.133.170.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 46ms, Average = 43ms
66.133.150.12
Pinging 66.133.150.12 with 32 bytes of data:
Reply from 66.133.150.12: bytes=32 time=42ms TTL=42
Reply from 66.133.150.12: bytes=32 time=38ms TTL=38
Reply from 66.133.150.12: bytes=32 time=38ms TTL=38
Reply from 66.133.150.12: bytes=32 time=38ms TTL=38
Ping statistics for 66.133.150.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 42ms, Average = 39ms
IPAddress = 192.168.1.104
Pinging 192.168.1.104 with 32 bytes of data:
Reply from 192.168.1.104: bytes=32 time<1ms TTL=0
Reply from 192.168.1.104: bytes=32 time<1ms TTL=0
Reply from 192.168.1.104: bytes=32 time<1ms TTL=0
Reply from 192.168.1.104: bytes=32 time<1ms TTL=0
Ping statistics for 192.168.1.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

netsh diag>

[jaydog11]

not sure what to about your note that read:

"Quote

From what I have read and I may NOT be correct it will fail on the DNS
If so uninstall this update
KB951748

http://support.microsoft.com/kb/951748

reboot

and reinstall it and then test"

[Essexboy]

The thought behind it was that if the netsh diag returned that error we could then continue to that fix

But the diag states that this computer is sending and receiving packets quite happily

Passing that back to the Techs now

[jaydog11]

i did notice that sometimes the trip times were 0ms. How is that possible? Wouldn't there have to be some amount of time?

[jaydog11]

by the way, i thought i should note that this whole time I have only 1 windows update so not sure that its getting them.

Also, my Norton software was trying to connect for updates and it gave me some messages that it would try to fix the problem. It noted that it "...detected entries within the host file that are blocking us from connecting".

Edited by jaydog11, 20 February 2012 - 02:25 PM.

[Essexboy]

The only things in the host file are the google/yahoo IP's that we added

Delete those in reverse to the way you added them

So that all you have in it is

127.0.0.1 localhost

The 0ms are to the host file on the computer

[Essexboy]

OK next step or two

Download the MS update from here

Uninstall update XP (KB951748)
Reboot
Install the update you have just downloaded
Reboot

THEN

From the command prompt type

nslookup att.com

Do you get this

Non-authoritative answer:
Name: att.com
Addresses: 144.160.155.43
144.160.36.42)

[jaydog11]

I think so.
I have downloaded the update.
Will go to add/remove programs and uninstall the KB951748 update.
Then reboot.
Then install new update.
Then reboot.

Not sure what the quote box means?