Network

Get firmware updates from manufacturer
Change the access point's SSID from the default ("Linksys")
Change the default administrative password
Disable SSID broadcasting
Refuse connections from systems with SSID set to "Any"
Use WEP encryption - make it required, not optional, use highest level of encryption
Change the WEP key
Specify MAC addresses to accept
(on some) disable SNMP (Simple Network Management Protocol)
(on some) disable DHCP (Dynamic Host Configuration Protocol)
As you survey your home for access point deployment, think about locating the access point toward the center of your home instead of near the windows. Plan your coverage to radiate out to the windows, but not beyond. If the access points are located near the windows, a stronger signal will be radiated outside your home making it easier for those outside the building to locate your network.
Take a notebook computer that is equipped with a wireless network adapter, and go outside your home and survey what range you get in moving around your property or neighborhood. You may be surprised how far the signal radiates. If you can connect from three or four houses away, so can someone else.
Some access points allow you to control access based on the media access control address of the network adapter trying to associate with it. If the media access control address of your adapter is not in the table of the access point, you will not associate with it. If your access point has this feature, enable it and add the media access control addresses of the network adapters you use.
If your access point is also a wireless router, think about assigning static IP addresses for your wireless adapters and turn off DHCP. By not automatically assigning IP addresses to clients who access the network, it makes it a little more difficult for an outsider to gain access. Also consider changing the IP subnet to a different subnet that does not route on the Internet. Many wireless routers default to the 192.168.1.0 network and use 192.168.1.1 as the default router.

Computers

Right-click on Network icon
Select "View Available Wireless Networks"
Click on "Advanced" button
Delete unknown access points
Click on "Advanced" button, lower-right
Choose "Access Point" under "Networks to Access"
Uncheck "Auto. Connect to non-Preferred Networks"

Cablevision Troubleshooting

Optimum Online Speed Check

Optimize Optimum Online

Vonage Speed Check

SpeedGuide.net :: Your Guide to Broadband

XP TCP/IP Repair

WinsockXPFix.exe (repair "limited or no connectivity")

SP2ConnectivityFix -

(1) Instructions

(2) WindowsXP-KB884020-x86-enu.exe

(3) FixReg.reg

Wireless Router (Windows XP)

Upgrade to WPA

TCPfix2 (link) (file)

SpeedGuide.net :: TCP Optimizer / Downloads

Qcheck - Network Performance Measurement

How to reset Internet Protocol (TCP/IP) in Windows XP

INTRODUCTION
In Microsoft Windows XP, the TCP/IP stack is considered a core component of the operating system, and you cannot remove TCP/IP. Therefore, when you view the list of components for a network interface, you may notice that the Uninstall button is disabled when Internet Protocol (TCP/IP) is selected. In extreme cases, the best solution for this issue may be to reinstall the Internet Protocol stack. But with the NetShell utility, you can reset the TCP/IP stack to restore it to its state that existed when the operating system was installed. This article describes how to use the NetShell utility for this purpose.
Back to the top Back to the top
MORE INFORMATION
The NetShell utility (netsh) is a command-line scripting interface for configuring and monitoring Windows XP networking. This tool provides an interactive network shell interface to the user.
In Windows XP, a reset command is available in the IP context of the NetShell utility. When you run the reset command, it rewrites pertinent registry keys that are used by the Internet Protocol (TCP/IP) stack to reach the same result as the removal and the reinstallation of the protocol.

Command usage
netsh int ip reset [log_file_name]
To run the command successfully, you must specify a file name for the log where actions that are taken by netsh will be recorded. For example, at a command prompt, type either of the samples that are listed in the "Command samples" section. The TCP/IP stack will then be reset on a system, and the actions that were taken will be recorded in the log file, Resetlog.txt. The first sample creates the log file in the current directory, while the second sample creates a path where the log will reside. In either case, where the specified log file already exists, the new log will be appended to the end of the existing file.
Warning Programs that access or monitor the Internet such as antivirus, firewall or proxy clients may be negatively affected when you run the netsh winsock reset command. If you have a program that no longer functions correctly after you use this resolution, reinstall the program to restore functionality.
Command samples
netsh int ip reset resetlog.txt
netsh int ip reset c:\resetlog.txt

Connecting to wrong wireless network

Find the Wireless Network Connection icon in the bottom-right corner, and right-click
Click on View Available Network Connections
Under Network Tasks: Refresh Network List
Under Related Tasks: Change the order of preferred networks
Select the Wireless Networks tab
Under Preferred Networks find your network
Use Move Up to move your network to the top
Remove other networks by selection each one and clicking on Remove
Click on OK, and that should do it

For more info: http://www.microsoft.com/technet/community/columns/cableguy/cg1102.mspx

How (and why) to re-register the Netshell.dll file

If you try to right click a network connection in the Network Connections folder and select Properties, and you get an error message that says "an unexpected error occurred," that's not very helpful. The most common cause is damaged registry settings that prevent you from viewing the network connection's properties. Here's what you need to do to repair it:

Click Start | Run/li>
In the Open box, type: regsvr32 %systemroot% \system32 \ netshell.dll/li>
Click OK in the dialog box

If this doesn't resolve the problem, try this:

Repeat step 1 above
In the Open box, type: regsvr32 %systemroot% \ system32 \ ole32.dll
Click OK in the dialog box
Reboot the computer