GOING NUTS said:
I am having a headache with my connection. I have a DSL
networked with two others computers in another room. All
of a sudden, the computer which has the main connection
stopped working. I mean, I can't get online. On the other
hand, the two other computer get online, either through
the network or by itself thru the modem. I already did
everything I know: restore, checked the modem, switched
the network card, use the diagnostic lights(DELL option),
SFC, delete cookies history , lower the security
settings , changed wires, took the HUB off and disconected
the other ones and tried to connect the computer itself
and so on. And NOTHING seems to work. My technical support
says that the problem is the configuration because the
modem is not being able to communicate with the computer
and that I should call a technician or use the recovery CD.
By the way, I am using a DELL OPTIPLEX GX260 with XP
professional.
Any help would be very much appreciated.
Thanks!
===============================================
Just to simplify things at this point -
Let's have the DSL modem directly connected to the
computer that is having the problem.
By the way, we are talking about an Ethernet connection right?
Is this a PPPoE connection? Meaning you have to make the
connection with a Username and Password?
Is the connection set to obtain an IP Address Automatically?
DNS set to Automatic also?
Is there a third party firewall being used and is it enabled?
Is there an Anti Virus program being used and is it kept up to date and enabled?
Do you have all of the XP critical updates installed?
What happens if you try to Repair the DSL connection in Network Connections?
What happens if you open the Command Prompt window and run the ipconfig /all command?
What IP Address do you get? Is it an APIPA in the 169.254.x.x range?
What happens if you then immediately run the ipconfig /renew command?
Do you get an error saying that an operation was attempted on
something that is not a socket? Or do you get some other error?
If you get the "something is not a socket" error, then you have damaged winsock keys in the registry.
If you get a different error then something else is going on.
If it is the winsock keys in the registry then -
Please read this whole reply before proceeding with any suggestions.
You should check System Information (winmsd)
START > RUN - type in winmsd and click OK
Expand Components / Network / click on Protocol -
if the section headings item of "Name" have a value
starting with anything other than MSAFD or RSVP
then that is probably what is causing the problem.
Examples:
MSAFD Tcpip [TCP/IP]
MSAFD Tcpip [UDP/IP]
RSVP UDP Service Provider
RSVP TCP Service Provider
MSAFD NetBIOS [\Device\NetBT_Tcpip...
and so on
It may be a third-party firewall or a Spyware or a Virus.
("New.Net" is a common spyware for example)
Make sure that MSCONFIG is in Normal Startup
and then see if uninstalling the third party firewall
(best done from its own uninstall program if available)
or the Spyware from Add Remove Programs will
resolve the issue. If it's a virus, then only an Anti Virus Program
will be able to deal with that.
You may want to try downloading either Ad-Aware 6 or Spybot
to another computer and then installing one of them on the infected XP Home/Pro
computer and try to wipe out Spyware and see if that resolves the issue.
Ad-aware 6.0 build 181
http://download.com.com/3000-2144-10214379.html?tag=list
Spybot - Search & Destroy 1.2
http://download.com.com/3000-2144-10194058.html?tag=list
If none of that works or is possible, you could try this method
for replacing the winsock and winsock2 registry keys:
Uninstall any third-party proxy software or firewall programs before proceeding.
You maybe should consider enabling the XP ICF at least temporarily, especially
if you are not current with XP critical updates.
Step 1: Delete registry keys
A)Open Regedit from the Run line
B)Go to both of the following keys, EXPORT each of them, and then delete them:
(To export a key, you right click on it and choose "export" - you can choose where to export them to -
DESKTOP is handy -
and you need to type in a file name such as "exported Winsock key" / "exported WinSock2 key"
and then click on SAVE)
HKLM\SYSTEM\CurrentControlSet\Services\Winsock
HKLM\SYSTEM\CurrentControlSet\Services\WinSock2
C)Restart the computer
NOTE: It is important to restart the computer after deleting the Winsock keys.
Doing so causes the XP operating system to recreate shell entries for those two
keys. If this is not done, the next step does not work correctly.
Step 2: Install TCP/IP on top of itself
A)Open the properties window of the network connection (Local Area Connection)
B)Click Install
C)Click Protocol, then Add
D)Click Have Disk
E)Type the path to the \%systemroot%\inf folder (usually C:\Windows\inf) and click OK
(if you try to click Browse, then browse to the \inf folder,
it may not show up in the list)
F)You should now see "Internet Protocol (TCP/IP)" in the list of available
protocols. Select it and click OK.
G)Restart the computer
When the computer reboots you will have functional Winsock keys.
If so, then be sure to delete the exported winsock and winsock2 reg files.
(You don't want to accidentally put them back in the registry)
Side effects and possible problems:
This method will restore basic functionality to the Winsock keys, but is not a
complete rebuild. On a default install of Windows XP the registry key:
HKLM\SYSTEM\CurrentControlSet\Services\Winsock2\
Parameters\Protocol_Catalog9\Catalog_Entries will have 11 sub-keys.
When applying this method, the Catalog_Entries will only have 3 sub-keys.
However, it works and there does not appear to be any side effects.
The missing entries relate back to the:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces key.
Also, third-party proxy software or firewalls may need to be reinstalled.
==========================================================
