windows 7 Professional 64-bit winsock problem

January 1, 2011 at 06:14:36
Specs: Windows 7 Proffesional x64, 2.5 GHZDual Core Athlon / 4 GB RAM
Hi, thanks in advance for help. Oh and english is not my first language so apologize for that.

So here is my situation: My brother gave me his old pc and it was crawling with malware. It has two disks - System (C:) and Data (D:). I used Malwarebytes's Antimalware to get rid of them. Then I formated C: and installed fresh new Windows 7.

The problem is, the internet doesn't work, I use ethernet cable. It tries to connect at first, but the only result is yellow exclamation mark in the corner. The packets are only sent, but not received. The internet is working fine on other two pc's (XP and Win 7)

So here is what I tried.
- TCP/IP set on auto
- Disabling Firewall
- Trying different version of Windows
- Reinstalling TCP/IP protocols
- ipconfig /all shows no DNS gates

After I did some research I think it might be winsock error.
msinfo32 -> winsock has only 8 parts.

I tried allsorts of winsock reset with no success.
I think I covered all.

Do you think it might be cause by some remnants of malware on Data disk (D:) ?
Or any idea how to fix it?


See More: windows 7 Professional 64-bit winsock problem

Report •

#1
January 1, 2011 at 06:50:37
I assume, you are connected to a router through the internet, right?

ipconfig /all should show an entry for the default gateway as well as for the DNS server.

Can you ping an ip address on the internet?
E.g.: ping 192.53.103.108
The ip address 192.53.103.108 is the ip of ptbtime1.ptb.de time server.

If that works, try this:
ping ptbtime1.ptb.de

If this ping ptbtime1.ptb.de fails, you problem is located in the DNS section.

You may also post the output of you ipconfig /all here.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#2
January 1, 2011 at 07:42:17
I cannot ping IP adress on internet,
And I had to translate the ipconfig /all
I hope it will be understandable

Windows IP Configuration
Host name . . . . . . . . . . . . : Rodinne - PC
Primary DNS Suffix . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled . . . . . . : No
WINS Proxy Enabled . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . : Realte RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
Physical Address . . . . . . . . . . . : 00-1D-7D-AF-7D-8C
Dhcp Enabled . . . . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . . . : fe80::b91c:acf0:fb8f:5e98%11(Preferred)
IPv4 Address . . . . . . . . . . . . . . : 169.254.94.152(Preferred)
Subnet Mask . . . . .. . .. . . . . .. . : 255.255.0.0
Default Gateway . . . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . . . : 234888573
DHCPv6 Client DVID . . . . . . . . . .: 00-01-00-01-14-AF-C4-50-00-1D-7D-AF-7D- AF-7D-8C
DNS Servers . . . . . . . . . . . . . . .: fec0:0:0:0:ffff::1%1
fec0:0:0:0:ffff::2%1
fec0:0:0:0:ffff::3%1
NetBIOS over Tcpip . . . . . . . . . . Enabled

Tunnel adapter isatap.{2557D946-3553-4FDB-AAA1-5E52DDAA27D9}:
Media State . . . . . . .. .. . . . . . : Media disconnected
Connection-specific DNS Suffix . . :
Description . . . . . . . .. . . . . . . . : Microsoft ISATAP Adapter
Physical Address . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled . . . . . . . . . . . . . : No
Autoconfiguration Enabled . . . . . .: Yes


Report •

#3
January 1, 2011 at 07:59:10
So again, if you are connected to a router, is the LINK LED for your computers LAN cable connection lit on the router?

You haven't got a vialid ip address because ipconfig /all shows:
[SNIP]
IPv4 Address . . . . . . . . . . . . . . : 169.254.94.152(Preferred)
Subnet Mask . . . . .. . .. . . . . .. . : 255.255.0.0
Default Gateway . . . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . . . : 234888573
DHCPv6 Client DVID . . . . . . . . . .: 00-01-00-01-14-AF-C4-50-00-1D-7D-AF-7D- AF-7D-8C
DNS Servers . . . . . . . . . . . . . . .: fec0:0:0:0:ffff::1%1
fec0:0:0:0:ffff::2%1
[/SNIP]

Causes for that could be:
1. corrupt LAN cable
2. corrupt LAN port at the router (therefore I asked for the LED at the router)
3. corrupt LAN card (therefore I asked for the LED at the router)
And some other things, we might talk about later.

So first check the LED at the router.
If it isn't lit, use another LAN cable and check again.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

Related Solutions

#4
January 1, 2011 at 08:32:21
It is connected from router, but there are no LED's. Cable is checked, works on two other PC's. I've tried direct connection from modem, doesn't help either.

Report •

#5
January 1, 2011 at 08:56:50
I assume, when you tried another computer, connected to you LAN cable, an additional LED is lit at the router, isn't it?

If you connect your PC's network card to one of the routers LAN ports and no additional LED is lit, that's a bad sign.

Is the network card listed in the device manager without and sign like a yellow exclamation mark or a red cross?

Is there a LED lit at the network card itself?
Maybe the connector your the network card itself has a problem or the network card is corrupt.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#6
January 1, 2011 at 09:00:06
- I tried and there are no LED's. The router looks really old, but it works with thoseo ther pc's.

- Network card is listed, drivers are ok and there are no conflicts.

-There is a LED lit at network card. It looks ok.


Report •

#7
January 1, 2011 at 09:09:47
What message did you get, when trying the following, while connected to the router:
1. open command prompt (CMD)
2. ipconfig /release
3. ipconfig /renew

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#8
January 1, 2011 at 10:01:10
Ok, I'll have to translate it again, so bear with me:

after ipconfig /renew
- An error occurred while renewing the interface Local Area Connection: An address has not yet been associated with the network endpoint.

after ipconfig /renew
- An error occurred while renewing interface Local Area Connection: DHCP server canno't be contacted. Request timed out


Report •

#9
January 1, 2011 at 13:46:01
Ok, I have one last idea, to figure out, whether your network card is working or it has died.

Download a Linux Live CD, burn it and boot your system with this CD.
Normally the current hardware will be automatically recognized be the Linux Live CD and network should work with this.
If not I fear, the network card is dead.
Linux Live CD download

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#10
January 1, 2011 at 15:28:04
I have a backup network card (older, but functional), I will install it tommorow and see if that helps. I will post results. Thanks for everything.

Report •

#11
January 2, 2011 at 04:49:51
The backup network card didn't help and I dislike Linux too much. Thanks for everything, I give up.

Report •

#12
January 2, 2011 at 06:23:45
This Linux Live CD were only to boot from and test, whether Linux can handle the network card and figure out, whether the network card is working in general.

But anyway, while you will give up at this stage, I will also.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

Ask Question