Solved Suspected Malware- Symantec email scanner returns spam went connected to certain ISPs

Status
Not open for further replies.
It is a IBM Thinkpad T42.
A wired connection does work though I don't have access to one at this time.
One error in an unknown device, my wireless adapter is fine.

Ping
Ping request could not find host google.com. Please check the name and try again.

IPconfig
Windows IP Configuration

An Internal error occured: The operation completed successfully.

When I try to release my IP I get:
IP Address for adapter Wireless Network Connection 4 has already been released.

When I try to renew I get:
An error occurred while renewing interface Wireless Network Connection 4: The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.
 
No, you're not doing, what I asked for.

Go Start>Run ("Start search" in Vista), type in:
cmd
Click OK (hit Enter in Vista).

At Command Prompt, paste this:
ipconfig /all>c:\ipconfig_all.txt&notepad c:\ipconfig_all.txt&exit
Hit Enter.

Copy and paste what you see in Notepad into a Reply here.

====================================================================

I'd also like to know, what that unknown device is.

1. Open Device Manager (Control Panel>System>Hardware>Device Manager)
2. The hardware whose drivers are missing will appear as Unknown device, so it's easier to locate the device.
3. Right click on the unknown device and click on Properties.
4. Under the Properties window click on Details tab and select Device Instance Id (or Device Instance Path) from the drop down box.
5. You should see a code similar to this

PCI\VEN_8086&DEV_27DC&SUBSYS_30868086
&REV_01\4&1E46F438&0&40F0

6. The portion of the code highlighted in RED is the Vendor ID and the portion highlighted in GREEN is the Device ID. In this example:

Vendor ID = 8086
Device ID = 27DC

7. Once you have obtained both the IDs, proceed to PCI Database. There you can either search for the vendor from the vendor ID or directly get information about the device along with the vendor name by searching with the device ID.

8. Then from there you can go directly to the hardware manufactureres website and get the driver.
 
When I type in the command you gave me, all I get is an empty .txt file. I wrote what happens if I just type 'ipconfig /all':
An Internal error occured: The operation completed successfully.
Please contact Microsoft Product Support Services for further help.
Additional information: Unknown media status code.

For the unknown device, in the Device Instance ID only the following is written
ROOT\*PNP0501\0000
 
Unknown media status code
The likely problem is a wired network adapter that isn't connected, and as a result has been automatically Disabled in Network Connections by its network driver, while still being enabled in Device Manager.

Try couple of workarounds and then try my command again...

1. (Verified)
1. Click Start > Control Panel > Network Connections, and for
any wired network adapters that are Disabled:
2. Right-click on My Computer, and click Manage to start Device
Manager
3. Disable wired Network Adapters that are disabled in Network
Connections
4. Run IPCONFIG as desired
5. Re-Enable wired network adapters in Device Manager

2. (Verified)
1. Click Start > Control Panel > Administrative Tools
2. Double-click Services
3. Scroll down to Routing and Remote Access
4. If Routing and Remote Access is Disabled, change it to
Manual
5. Start Routing and Remote Access, or Stop and Re-Start it if
it's already running
 
Nothing doing for either:
The Network adapter was already disabled, I toggled it with no luck.
Routing and Remote Access was Disabled, I changed it to manual and still nothing.
 
So I didn't start the Routing and Remote Access. Now I get the following:



Windows IP Configuration



Host Name . . . . . . . . . . . . : system-d002f5bf

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes



Ethernet adapter Wireless Network Connection 4:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG Network Connection

Physical Address. . . . . . . . . : 00-0E-35-D7-12-E7

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 0.0.0.0

Subnet Mask . . . . . . . . . . . : 0.0.0.0

IP Address. . . . . . . . . . . . : fe80::20e:35ff:fed7:12e7%4

Default Gateway . . . . . . . . . :

DHCP Server . . . . . . . . . . . : 255.255.255.255

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1



Tunnel adapter Teredo Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%6

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled
 
OK, your IP configuration is definitely messed up.

Let's try some basic steps...

Make sure, your computer is set to obtain IP address automatically.
1. Go Start>Settings>Control Panel (Vista/7 users: Start>Control Panel)
2. Double click Network Connections (Vista/7 users: Network and Sharing Center)
3. Vista/7 users - From the list of tasks on the left, click Manage network connections.
4. 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.
5. From the General tab (Vista/7 users: Networking tab), click Internet Protocol (TCP/IP), make sure it is checked, and then click Properties
6. Click Obtain an IP Address Automatically, and then click OK.

If that doesn't work...
Turn off computer. Disconnect router, and modem from power source for 1 minute. At the same time disconnect ethernet cable as well.
Reconnect everything.
Restart computer.

If that doesn't work, bypass router, and connect computer straight to the modem.

If that doesn't work...
Go Start>Run (Start search in Vista), type in:
cmd
Click OK (in Vista, while holding CTRL, and SHIFT, press Enter).

In Command Prompt window, type in following commands, and hit Enter after each one:
ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew
net stop "dns client"
net start "dns client"


Restart computer.

If that doesn't work...
Go Start>Run (Start search in Vista), type in:
cmd
Click OK (in Vista, while holding CTRL, and SHIFT, press Enter).

At Command Prompt, type in:
netsh int ip reset reset.log
Hit Enter.
Type in:
netsh winsock reset catalog
Hit Enter.

Restart computer.


If that doesn't work...
Download, install, and run WinSockFix: http://www.softpedia.com/get/Tweak/Network-Tweak/WinSockFix.shtml (doesn't work in Vista)
Restart computer, and check again.

If that doesn't work...
Download Dial-A-Fix (DAF) (doesn't work in Vista):
http://wiki.lunarsoft.net/wiki/Dial-a-fix#Mirrors.2Fdownload_locations.2C_and_articles

Have XP CD available in case DAF needs a file. Likely not!

Check all boxes on the screen (clear any restrictions if it shows any)
Then click GO!

When the entire page is finished click the HammerHead at bottom to go to the second DAF page.

Here, one at a time, do the below:

Reinstall BITS
Reinstall Windows Firewall
Repair Permissions
Reset networking

Watch for any File not found or other errors and make note as this may lead to the fix!

Restart computer.
 
I didn't do anything with direct LAN connection because I only have access to wireless at the minute...

The following command was not found: int ip reset reset.log

error in dail-a-fix 2147467259 while trying to unregister C:\windows\system32\msxml3.dll

I did everything front to back and still the same problem: No wireless networks were found in range.
 
That got it to detect wireless networks but when connecting I cannot get past 'Acquiring Network Address'.
It just sits and loops.
 
It looks like we had a driver problem to start with.

Now, go through steps from my reply #32 one more time.
 
Status
Not open for further replies.
Back