Re: WinSock Problem



"Andyve" wrote:

i have pretty much the same problem except that i am able to make an https
and ftp connection. the bigger issue is that on reboot i am able to access
the internet for about 15 minutes, intially vey good and then the connection
slows down to nil and i get the same error reports from the diagnostic tool.
i can send and receive mail at any time.
i have tried all the suggestion nass but it does not help. i have installed
a port reporter but it is not picking up anything that appears to be blocking
port 80 after this time period.
i have uninstalled my A-V without success and also re-installed ie7. have
deleted the winsock reg entries but had to restore working entries frim
another computer to get my nic working again. i have used various winsock and
lsp fixes and still the problem exists. i also re-applied sp2 and the time i
m able to access the internet went form 2-5 minutes to about 15 minutes.
is there perhaps another way to reset/delete and recreate the winsock
catalog without using the cmd line? my diagnostics error msg says "not all
base provder enties can be found in the winsock catalog". i had a few vpn
programs installed to test but have uninstalled them. the port reporter keeps
on reporting that my wsus server is not available but i have unistalled this
a long time ago. i run reg mechanic every time time i reboot but this does
not appear to have cleared the wsus server issue. i do not think the wsus has
something to do with it but i am grasping at ANY possibility right now.
any help would be appreciated
Andy

Hi Andy,

= Click Start >> Control Panel>>Network and Internet Connections >> Double
click Internet Options.
On the IE properties windows you will see these Tabs:
General | Security | Privacy | Content | Connections | Programs |
Advanced.

Click on Connections Tab then click on LAN Settings Button, make sure
nothing checked there (clear all boxes) then click [OK] and [OK] again.

This could be due to:
1- A Power management settings for the NIC, to know if the Power management
settings correct try this:
Right click " MY Computer" select Properties and then click on Hardware Tab
then click on Device Manager button.
On Device Manager locate this:
[+] Network Adapters, click on the Plus [+] to expand to [-] and locate the
Wireless NIC, then while highlighting the NIC click on the Properties Button.
On the NIC Properties window click on Power management and make sure this
check box is unchecked:
[ ] Let the computer Turn OFF this Device for power saving.

Click [Ok] and out, does it help retain the connection.

Make sure the machine is configured to get Auto IP address and DNS, by
performing these steps:
Click start >> Control panel >> Network and Internet Connections >> Network
Connections >> Right click the wireless connection and select properties.
On the Wireless properties click on General tab then highlight the Internet
Protocol TCP/IP then click on properties, make sure the machine getting the
IP address Auto and the DNS Auto too!.
Click Advanced button click IP Settings Tab, make sure the DHCP Enabled and
Automatic metric check box is checked.
Click DNS tab, see these check boxes/Radio button:
(*)Append Primary and connection specific DNS suffixes
[ ] Append parent suffixes of the primary DNS suffix.
Click WINS, make sure the LMHOST is checked and the default radio for the
NeTbios settings is checked.

How to remove and reinstall TCP/IP on a Windows Server 2003 domain controller
http://support.microsoft.com/kb/325356


resetting the Winsock:
http://support.microsoft.com/kb/811259

You may receive a "Limited or no connectivity" message
http://support.microsoft.com/kb/892896

Another is to uninstall the TCP/IP and reinstall it:
Reset TCP/IP:
http://support.microsoft.com/kb/299357
Note: Did you update the firmware for the Modem/Router you are using, did
you checked it is not the hardware going Bad, also could you let us know the
Network design/implementation on your System, like do you use Router (wired
or wireless, any encryption of Wireless?).
I have an experience in the past that a left over debris from a protection
suite can cause this, try to make sure the Old protection suite are
completely removed and there are no traces left!.
HTH.
nass
---
http://www.nasstec.co.uk
.