Follow that guide, and post the required logs in the Malware Forum.
Can't connect to internet
Started by
jones082
, May 12 2009 10:53 AM
#16
Posted 22 May 2009 - 05:21 PM
Follow that guide, and post the required logs in the Malware Forum.
#17
Posted 23 May 2009 - 04:47 PM
Okay. Thanks for trying to help.
#18
Posted 23 May 2009 - 05:55 PM
Did you post in the Malware Forum?
We will just make sure that malware isn't causing this problem.
If you have problems after receiving a clean bill of health from the malware techs, then post back here.
We will just make sure that malware isn't causing this problem.
If you have problems after receiving a clean bill of health from the malware techs, then post back here.
#19
Posted 23 May 2009 - 09:55 PM
Yes, thanks, I followed the directions and posted my logs.
#20
Posted 23 May 2009 - 11:28 PM
Ok then. Wait for a response to your post.
#21
Posted 01 June 2009 - 05:26 PM
Ok, Essexboy said that there didn't appear to be Malware so he sent me back here.
One thing I have discovered. When I have lost conncetion, or when it has slowed down to a standstill, I can go to TCP/IP properties, select "alternate configuration", and put in previous numbers which have worked in the past.
That, in itself, doesn't connect me; but for some reason, THEN when I hit "Repair this connection," it is able to assign me a new ip address and connect me.
One thing I have discovered. When I have lost conncetion, or when it has slowed down to a standstill, I can go to TCP/IP properties, select "alternate configuration", and put in previous numbers which have worked in the past.
That, in itself, doesn't connect me; but for some reason, THEN when I hit "Repair this connection," it is able to assign me a new ip address and connect me.
#22
Posted 01 June 2009 - 06:11 PM
Start -> Run -> cmd
Type in these commands. Then open up C:\results.txt, and post it's contents.
route print >> C:\results.txt
ping 127.0.0.1 >> C:\results.txt
ping google.com >> C:\results.txt
ping 209.85.171.100 >> C:\results.txt
Do this when you have not yet put in the alternate configuration or repaired your connection.
(The instructions are from Dan.)
Then try setting a static IP.
Click Start, select Run, type ncpa.cpl and press OK
In the new window, right-click on your Wireless Network Connection and select Properties.
Select Internet Protocol Version (TCP/IP) and then press the Properties button.
Select the option Use the following IP Address: and then enter in the following details:
IP Address: 192.168.1.110
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Select Use the following DNS Servers and enter in two DNS Servers.
Preferred DNS Server: 68.94.156.1
Alternate DNS Server: 68.94.157.1
Press OK.
Type in these commands. Then open up C:\results.txt, and post it's contents.
route print >> C:\results.txt
ping 127.0.0.1 >> C:\results.txt
ping google.com >> C:\results.txt
ping 209.85.171.100 >> C:\results.txt
Do this when you have not yet put in the alternate configuration or repaired your connection.
(The instructions are from Dan.)
Then try setting a static IP.
Click Start, select Run, type ncpa.cpl and press OK
In the new window, right-click on your Wireless Network Connection and select Properties.
Select Internet Protocol Version (TCP/IP) and then press the Properties button.
Select the option Use the following IP Address: and then enter in the following details:
IP Address: 192.168.1.110
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Select Use the following DNS Servers and enter in two DNS Servers.
Preferred DNS Server: 68.94.156.1
Alternate DNS Server: 68.94.157.1
Press OK.
#23
Posted 01 June 2009 - 08:37 PM
I am connected and stable for now with my alternate connection. Should I change the "Alternate configuration" radio button back to "Automatic Private Ip Address" and then wait until I cannot connect, to follow the above instructions?
#24
Posted 01 June 2009 - 08:53 PM
Try the instructions right now, when your connection is stable. Just want to make sure that it is connecting without any issues.
So now when you reboot, you have to go through this process to revive your weak or lost connection?
So now when you reboot, you have to go through this process to revive your weak or lost connection?
#25
Posted 02 June 2009 - 06:02 PM
I lost connection and the static IP did not work, so I ran this one first:
Windows IP Configuration
Host Name . . . . . . . . . . . . : your-xktpas8d47
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ph.cox.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : ph.cox.net
Description . . . . . . . . . . . : VIA Rhine III Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0C-76-A5-F4-0E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 68.2.174.141
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 68.2.168.1
DHCP Server . . . . . . . . . . . : 172.19.73.22
DNS Servers . . . . . . . . . . . : 68.105.28.12
68.105.29.12
68.105.28.11
Lease Obtained. . . . . . . . . . : Thursday, May 21, 2009 5:06:04 AM
Lease Expires . . . . . . . . . . : Friday, May 22, 2009 5:06:04 AM
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c 76 a5 f4 0e ...... VIA Rhine III Fast Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 72.208.45.1 72.208.45.50 30
72.208.45.0 255.255.255.0 72.208.45.50 72.208.45.50 30
72.208.45.50 255.255.255.255 127.0.0.1 127.0.0.1 30
72.255.255.255 255.255.255.255 72.208.45.50 72.208.45.50 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 72.208.45.50 72.208.45.50 30
255.255.255.255 255.255.255.255 72.208.45.50 72.208.45.50 1
Default Gateway: 72.208.45.1
===========================================================================
Persistent Routes:
None
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
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
Ping request could not find host google.com. Please check the name and try again.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 209.85.171.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
I shut the computer down overnight, turned it on today, and was able to connect, then crashed three times.
I tried Winsocketxpfix, and that got me back on.
Then, I ran this:
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c 76 a5 f4 0e ...... VIA Rhine III Fast Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 72.201.16.1 72.201.16.104 30
72.201.16.0 255.255.252.0 72.201.16.104 72.201.16.104 30
72.201.16.104 255.255.255.255 127.0.0.1 127.0.0.1 30
72.255.255.255 255.255.255.255 72.201.16.104 72.201.16.104 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 72.201.16.104 72.201.16.104 30
255.255.255.255 255.255.255.255 72.201.16.104 72.201.16.104 1
Default Gateway: 72.201.16.1
===========================================================================
Persistent Routes:
None
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
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
Pinging google.com [209.85.171.100] with 32 bytes of data:
Reply from 209.85.171.100: bytes=32 time=70ms TTL=244
Reply from 209.85.171.100: bytes=32 time=70ms TTL=245
Reply from 209.85.171.100: bytes=32 time=70ms TTL=244
Reply from 209.85.171.100: bytes=32 time=69ms TTL=245
Ping statistics for 209.85.171.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 70ms, Average = 69ms
Pinging 209.85.171.100 with 32 bytes of data:
Reply from 209.85.171.100: bytes=32 time=70ms TTL=245
Reply from 209.85.171.100: bytes=32 time=69ms TTL=244
Reply from 209.85.171.100: bytes=32 time=70ms TTL=245
Reply from 209.85.171.100: bytes=32 time=73ms TTL=244
Ping statistics for 209.85.171.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 73ms, Average = 70ms
Now that I got this posted, I'll try to set a static IP, and add the result.
Windows IP Configuration
Host Name . . . . . . . . . . . . : your-xktpas8d47
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ph.cox.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : ph.cox.net
Description . . . . . . . . . . . : VIA Rhine III Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0C-76-A5-F4-0E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 68.2.174.141
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 68.2.168.1
DHCP Server . . . . . . . . . . . : 172.19.73.22
DNS Servers . . . . . . . . . . . : 68.105.28.12
68.105.29.12
68.105.28.11
Lease Obtained. . . . . . . . . . : Thursday, May 21, 2009 5:06:04 AM
Lease Expires . . . . . . . . . . : Friday, May 22, 2009 5:06:04 AM
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c 76 a5 f4 0e ...... VIA Rhine III Fast Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 72.208.45.1 72.208.45.50 30
72.208.45.0 255.255.255.0 72.208.45.50 72.208.45.50 30
72.208.45.50 255.255.255.255 127.0.0.1 127.0.0.1 30
72.255.255.255 255.255.255.255 72.208.45.50 72.208.45.50 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 72.208.45.50 72.208.45.50 30
255.255.255.255 255.255.255.255 72.208.45.50 72.208.45.50 1
Default Gateway: 72.208.45.1
===========================================================================
Persistent Routes:
None
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
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
Ping request could not find host google.com. Please check the name and try again.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 209.85.171.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
I shut the computer down overnight, turned it on today, and was able to connect, then crashed three times.
I tried Winsocketxpfix, and that got me back on.
Then, I ran this:
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0c 76 a5 f4 0e ...... VIA Rhine III Fast Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 72.201.16.1 72.201.16.104 30
72.201.16.0 255.255.252.0 72.201.16.104 72.201.16.104 30
72.201.16.104 255.255.255.255 127.0.0.1 127.0.0.1 30
72.255.255.255 255.255.255.255 72.201.16.104 72.201.16.104 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 72.201.16.104 72.201.16.104 30
255.255.255.255 255.255.255.255 72.201.16.104 72.201.16.104 1
Default Gateway: 72.201.16.1
===========================================================================
Persistent Routes:
None
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
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
Pinging google.com [209.85.171.100] with 32 bytes of data:
Reply from 209.85.171.100: bytes=32 time=70ms TTL=244
Reply from 209.85.171.100: bytes=32 time=70ms TTL=245
Reply from 209.85.171.100: bytes=32 time=70ms TTL=244
Reply from 209.85.171.100: bytes=32 time=69ms TTL=245
Ping statistics for 209.85.171.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 70ms, Average = 69ms
Pinging 209.85.171.100 with 32 bytes of data:
Reply from 209.85.171.100: bytes=32 time=70ms TTL=245
Reply from 209.85.171.100: bytes=32 time=69ms TTL=244
Reply from 209.85.171.100: bytes=32 time=70ms TTL=245
Reply from 209.85.171.100: bytes=32 time=73ms TTL=244
Ping statistics for 209.85.171.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 73ms, Average = 70ms
Now that I got this posted, I'll try to set a static IP, and add the result.
#26
Posted 02 June 2009 - 07:04 PM
Ok. The 2nd set of into, after you ran WinsockFix looks good.
Post it with the static IP.
What problems are you having with your connection now?
Post it with the static IP.
What problems are you having with your connection now?
#27
Posted 03 June 2009 - 08:21 AM
Continuous crashing. Was unable to connect the whole day.
Also, Not able to connect with the static ip you gave me.
Winsockfix hasn't worked. I was able to connect by manually putting in the settings that previously worked.
But even when I manage to connect, it still only lasts a few hours.
And the crashing is getting worse. I keep getting the blue screen and system dumps and freezing.
Also, Not able to connect with the static ip you gave me.
Winsockfix hasn't worked. I was able to connect by manually putting in the settings that previously worked.
But even when I manage to connect, it still only lasts a few hours.
And the crashing is getting worse. I keep getting the blue screen and system dumps and freezing.
#28
Posted 03 June 2009 - 06:50 PM
These appear to be related.Continuous crashing. Was unable to connect the whole day.
Go to the directory C:\Windows\Minidump
Make sure that hidden files are visible.
Then zip up the recent files in that folder (made within a week) and attach the .zip archive to your next post.
#29
Posted 03 June 2009 - 07:21 PM
The folder is empty. Unfortunately, in trying to keep up and running, I ran CCleaner, ATF Cleaner, Defrag, etc., and I guess that empties the dumps?? I can post again after I crash.
#30
Posted 03 June 2009 - 07:28 PM
http://www.cakewalk....er/minidump.asp
http://www.lazybit.c...ing_tips?blog=2
Follow the instructions, and recreate your BSOD, and post.
http://www.lazybit.c...ing_tips?blog=2
Follow the instructions, and recreate your BSOD, and post.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users