Malware messing with Avast net connection

Welcome to Major Geeks!

This is pointing out part of your problems. The current date is not August 18, 2010. It is now September 20, 2010 ( 2010-09-20 ). You need to fix the date and time on your PC so that ComboFix can run. The logs from MGtools also show you have the wrong date, so a new log from MGtools should be obtained too.

Normal.

Not normal and not sure why this is happening yet.

 

Correct. You need to redownload the current version to run a scan now that you fixed your date.

No there was nothing in the other logs. What malware problems do you believe you are currently having? You no longer have Avast installed and any update problems with it may have been due to your date being set incorrectly.

 

Also clean.

Not necessarily. You may have some kind of hardware issue. There is absolutely no sign of any malware being at play. The only issue I see ( and it is not malware ) is that your ping times are delayed or not being answered and that your network settings do not look correct. I'm referring to the below information which is seen in the nwktst.txt log inside of MGlogs.zip

Code:

================================================================ 
 
Pinging 66.249.80.104 with 32 bytes of data:
 
Request timed out.
Reply from 66.249.80.104: bytes=32 time=52ms TTL=55
 
Ping statistics for 66.249.80.104:
    Packets: Sent = 2, Received = 1, Lost = 1 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 52ms, Maximum = 52ms, Average = 52ms
 
================================================================= 
 
Pinging [URL="http://www.l.google.com"]www.l.google.com[/URL] [173.194.32.104] with 32 bytes of data:
 
Request timed out.
Request timed out.
 
Ping statistics for 173.194.32.104:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
 
================================================================= 
Doing nslookup google.com 
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  216.58.97.21
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.

And also the below which shows a node type of unknown and then you have IP Routing Enabled which I would expect not to be the case. And also shows that your DHCP lease should have already expired ( you should release and renew)

Code:

Checking ipconfig 
 
Windows IP Configuration
 
        Host Name . . . . . . . . . . . . : anonymous
        Primary Dns Suffix  . . . . . . . : 
[COLOR=darkred][B]      Node Type . . . . . . . . . . . . : Unknown[/B][/COLOR]
[COLOR=darkred][B]      IP Routing Enabled. . . . . . . . : Yes[/B][/COLOR]
        WINS Proxy Enabled. . . . . . . . : No
 
Ethernet adapter Local Area Connection:
 
        Connection-specific DNS Suffix  . : 
        Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.0.134
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1
        DHCP Server . . . . . . . . . . . : 192.168.0.1
        DNS Servers . . . . . . . . . . . : 216.58.97.21
                                            216.58.97.20
        Lease Obtained. . . . . . . . . . : Samschdeg 21 August 2010 13:13:19
        Lease Expires . . . . . . . . . . : Samschdeg 28 August 2010 13:13:19

Based on your symptoms and the content of your logs it is extremely unlikely (but not impossible) that your problems are malware. So yes I suggest posting in the Networking Forum and refer them to this thread too. I would have ever use ipconfig to release and renew your connection, and I would try to figure out why your node type is unknown. Are you really supposed to be using IP Routing? Did your ISP configure this?

 

You really need to continue this discussion in the Networking Forum but I will give you a couple things to try. For additional help, please goto the Networking Forum.


First let's make sure that you have set your PC to obtain an IP address automatically ( NOTE: I'm assuming that you do not use a static IP address ) This is also commonly called setting your PC for DHCP. Thus DHCP means you should be set to Obtain an IP address automatically.

• From the Start menu select Settings and then Control Panel. (Or just Start, Control Panel if it already shows)
• Double-click Network Connections
  • For a wired network connection, right-click Local Area Connection, and then select Properties
  • For a wireless network connection, right-click Wireless Network Connection, and then select Properties
• From the General tab, scroll to locate and click Internet Protocol (TCP/IP) , make sure it is checked, and then click the Properties button.
• Click Obtain an IP Address Automatically
• Also make sure that down below you have Obtain DNS server address automatically selected
• Then click OK.

Now copy the bold text below to notepad. Save it as fixme.reg to your desktop. Be sure the "Save as" type is set to "all files" Once you have saved it double click it and allow it to merge with the registry.

Make sure that you tell me if you receive a success message about adding the above to the registry. If you do not get a success message, it definitely did not work.

Now reboot your PC. After reboot, do the below.

Click Start, Run, and enter cmd and click OK to open a command prompt window. At the command prompt enter the below command and then hit the enter key. Note there is a space after the iconfig and after the all

ipconfig /all > C:\ipinfo.txt


Now attach the C:\ipinfo.txt log to your next message.

 

Yes this is typcial and perhaps even may explain why your network interface is showing up as enabling routing.

Sorry but you need to continue in the Networking Forum or work this out with your ISP.