Computing.Net > Forums > Networking > networking problem plz plz help!!

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

networking problem plz plz help!!

Reply to Message Icon

Name: void0soul
Date: April 19, 2004 at 23:11:50 Pacific
OS: win xp pro
CPU/Ram: P4 2.00 GHz ram 256 MB
Comment:

My computer is a sub computer in a small home network which consists of two pc's mine and the main pc, the problem is that suddenly my computer can't any more connect to the interent through the network, i checked everything and reinstalled the drivers, made new connections and all the drivers are enabled, the main computer can connect to the internet but mine can't.
can u plz help me with that..
and i want to know if there are any computers errors that can affect the network, on the main pc or mine,
thanks


VOID



Sponsored Link
Ads by Google

Response Number 1
Name: Richard59
Date: April 20, 2004 at 00:51:22 Pacific
Reply:

Check firewall settings. Check that both are in the same workgroup. Can you ping each from the other? Do you have filesharing enabled? Can your systems see each other? Are you using ICS? Have you run the network wizard again?


0

Response Number 2
Name: void0soul
Date: April 20, 2004 at 22:12:38 Pacific
Reply:

i checked everything, firewall is disabled and they are both in the same work group and i can access the shared folders and the system can se the other computer and i ran the internet wizard 1000 times :(
everything seems to be working but it is actually not!!what should i do?

VOID


0

Response Number 3
Name: kmevanszoo
Date: April 21, 2004 at 16:31:49 Pacific
Reply:

After deleting 61 spyware files, I could not access internet, either. Try this WINSOCK repair. It worked for me...

Microsoft KnowledgeBase XP Document Number 811259.

How to determine and recover from Winsock2 corruption
View products that this article applies to.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry

SYMPTOMS
When you try to release and renew the IP address using the Ipconfig program, you may receive the following error message:

An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket.
When you start Internet Explorer, you may receive the following error message:

The page cannot be displayed
Additionally, you may have no IP address or no Automatic Private IP Addressing (APIPA) address, and you may be receiving IP packets but not sending them.
CAUSE
These issues may occur if the Winsock registry keys are damaged or corrupted.
RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
How to determine whether the Winsock2 key is corrupted
To determine if the symptoms are caused by a problem with the Winsock2 key, use one of the following methods.
Method 1: Use the Netdiag tool
To use the Netdiag tool, you must install the Microsoft Windows XP Support Tools. To do so, follow these steps:

Note If you already have Support Tools installed, go to the second procedure in this section.

Note If you do not have Support Tools installed and you do not have the Windows XP Setup CD, go to Method 2.
Insert your Windows XP Setup CD, and then locate the Support\Tools folder.
Double-click the Setup.exe file.
Follow the steps on the screen until you reach the Select An Installation Type screen.
On the Select An Installation Type screen, click Complete, and then click Next.
When the installation is complete, follow these steps:
Click Start, click Run, type Command, and then click OK.
Type netdiag /test:winsock, and then press ENTER.
The Netdiag tool will return the test results for several network components, including the Winsock. For more details about the test, use /v at the end of the netdiag command: netdiag /test:winsock /v
Method 2: Use the Msinfo32 program
Note Use this method only if you do not have a Windows XP Setup CD and you do not have Support Tools installed.
Click Start, click Run, type Msinfo32, and then click OK.
Expand Components, expand Network, and then click Protocol.
You will have ten sections under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:
MSAFD Tcpip [TCP/IP]
MSAFD Tcpip [UDP/IP]
RSVP UDP Service Provider
RSVP TCP Service Provider
MSAFD NetBIOS [\Device\NetBT_Tcpip...
MSAFD NetBIOS [\Device\NetBT_Tcpip...
MSAFD NetBIOS [\Device\NetBT_Tcpip...
MSAFD NetBIOS [\Device\NetBT_Tcpip...
MSAFD NetBIOS [\Device\NetBT_Tcpip...
MSAFD NetBIOS [\Device\NetBT_Tcpip...
If the names are anything different from those in this list, the Winsock2 key is corrupted, or you have a third-party add-on, such as proxy software, installed.


If you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list.

If there are more than ten sections in the list, you have third-party additions installed.

If there are fewer than ten sections, there is information missing.

Note These entries represent an installation with only the TCP/IP protocol installed. You can have a working Winsock and see additional entries if another protocol is installed. For example, if you install NWLink IPX/SPX, you will see 7 additional sections, for a total of 17. Below is an example heading of one of the new sections:
MSAFD nwlnkipx [IPX]
Also, each of the new sections that are created by installing NWLink IPX/SPX start with "MSAFD." Therefore, there are still only two sections that do not start with those letters.

If the Netdiag test fails, or if you determined that there is Winsock corruption by looking at Msinfo32, you must repair the Winsock2 key by using the steps in the next section.
How to Recover from Winsock2 corruption
To resolve this issue, delete the corrupted registry keys, and then reinstall of the TCP/IP protocol.
Step 1: Delete the corrupted registry keys
Click Start, and then click Run.
In the Open box, type regedit, and then click OK.
In Registry Editor, locate the following keys, right-click each key, and then click Delete:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

When you are prompted to confirm the deletion, click Yes.
Note Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.
Step 2: Install TCP/IP
Right-click the network connection, and then click Properties.
Click Install.
Click Protocol, and then click Add.
Click Have Disk.
Type C:\Windows\inf, and then click OK.
On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.
Restart the computer.

Hope this helps...


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Networking Forum Home


Sponsored links

Ads by Google


Results for: networking problem plz plz help!!

Networking problems WEP please help www.computing.net/answers/networking/networking-problems-wep-please-help/31376.html

RUN network command error plz help www.computing.net/answers/networking/run-network-command-error-plz-help/34490.html

(plz help) internet sharing conflic www.computing.net/answers/networking/plz-help-internet-sharing-conflic/9461.html