Seeminly Unsolveable Problem! Reply ASAP!

Status
Not open for further replies.
Well that's called a power cycle, there is also the hard reset (small black button) and a soft reboot (usually done from a web interface with a router/modem).
Nothing wrong with starting off with a power cycle though, fixes most glitches.

Out of curiosity, and if you feel so inclined, would you do the following for me:

run this command at the command prompt:

netsh diag show test > c:\test.txt

then if you wait a minute and go to your C drive you should see a file called test.txt - copy and paste the content here.

I expect your network settings are all fine, but its well to check. you obviously have an internet connection as you're picking up DNS information.

Edit: Having looked through the thread again I can't help thinking this might all be resolved with a repair install and a trip to windows update. I looked though and I can't see anywhere that you've confirmed that you have done a repair install (which is different from the repair console). And all those hotfix uninstallers picked up by ccleaner indicate that the SFC scan invalidated a whole butt load of updates.
Either way, fresh install or repair install you are going to have to spend some time on windows update.
 
Thanks! I am just waiting on my dad for the disks i need to reformat! Here is the info:

efault 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

Network Adapters ([00000001] Broadcom NetXtreme Gigabit Ethernet Adapter)
DefaultIPGateway = 192.168.0.254 Same Subnet
Pinging 192.168.0.254 with 32 bytes of data:
Reply from 192.168.0.254: bytes=32 time<1ms TTL=0
Reply from 192.168.0.254: bytes=32 time<1ms TTL=0
Reply from 192.168.0.254: bytes=32 time<1ms TTL=0
Reply from 192.168.0.254: bytes=32 time<1ms TTL=0
Ping statistics for 192.168.0.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
DHCPServer = 192.168.0.254
Pinging 192.168.0.254 with 32 bytes of data:
Reply from 192.168.0.254: bytes=32 time<1ms TTL=0
Reply from 192.168.0.254: bytes=32 time<1ms TTL=0
Reply from 192.168.0.254: bytes=32 time<1ms TTL=0
Reply from 192.168.0.254: bytes=32 time<1ms TTL=0
Ping statistics for 192.168.0.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
DNSServerSearchOrder = 192.168.0.254
Pinging 192.168.0.254 with 32 bytes of data:
Reply from 192.168.0.254: bytes=32 time<1ms TTL=0


There it is!
 
well yeah, that looks absolutly fine. Just go ahead with the reinstall, its the simplest, cleanest solution at this point.
 
K Thanks! I am going to try a repair install first since I still don't have all the cds I need.
 
Status
Not open for further replies.
Back
Top Bottom