|Home||Reviews||Tools||Forums||FAQs||Find Service||ISP News||Maps||About|
how-to block ads
Continue to read here to fix the problem.
got feedback?WinXP Prof Network Verification
got feedback?Windows XP Home Edition Network Verification
#1 File and Print Sharing Service
Install the “File and Print sharing service” on each machine. Nothing need be shared but the service must be running for the machine to show up in the Neighborhood.
File and print sharing must be bound to a communication protocol. My recommendation is to use TCP/IP for everything. If you want to use NetBEUI for sharing go to Network setting for each adapter and unbind TCP/IP. By default Windows binds each adapter to all protocols.
Security Tip - If your system includes an interface connected directly to the Internet such as a dialup, Cable, or DSL modem unbind file and print sharing service from that interface. Failure to do so results in sharing your system with millions of your best friends on the Internet.
#3 Workgroup name
Network neighborhood is organized by workgroup. You can have as many workgroups as desired. In a small LAN it makes sense to use a single name, such as HomeLAN, because each workgroup requires its own Browse Master.
#4 Browse Master
Ideally the Browse Master runs on an always computer. This is the reason to use the same workgroup name for all machines. Browse Master is selected in an election process during power up. If you have a PC that is always on go into File and Print sharing properties and change Browse Master from Automatic to Enabled. This forces that Browse Master to win the election.
If you don't have a machine that is always on it may take a few minutes for the neighborhood to appear after power up. The neighborhood will disappear for a while when the host running the Browse Master is shutdown until the lack of a Browse Master is noticed and a new election held.
If network logon (in network properties) is set for Client for Microsoft Networks you must enter a password at boot time for the Neighborhood to be accessible. If you bypass the password most communication continue to function but you will not be able to browse the neighborhood. If you do no want to enter a password at boot time select Windows Logon. You may have to delete any existing passwords. Search for *.pwd files and delete them.
#6 Enabling Shares
On a machine running the file and print sharing service pick the subdirectory to share and check sharing. That directory and all subdirectories will be shared. In a peer-to-peer network shares can be password protected to control access.
#7 User Account
Some versions of Windows need user account in order to share files.
If you are running a software firewall on the PC be sure it does not block NetBIOS ports used to discover local host names and share files.
As mentioned in step 2, these ports are used on the LAN but should not be accessible on the Internet.
Security Tip - In general it is a good idea not to share files unless necessary. Some of the most damaging Viruses search for file shares and destroy them.
Windows Configuration Tip – There appears to be a compatibility problem between Win2000 and Win98/ME network neighborhood. We had trouble getting a Win 98 laptop to show up in a network of Win 2000 machines. The solution to was to create separate workgroup for Win 2000 and Win98 machines. The laptop was put in a workgroup by itself and the laptop Browse Master was enabled.
To fix this problem, users of Win2k and WinXP should start a command prompt window. Then they should type 'ipconfig /release'. An error message of some sort may (or may not) be displayed. Now, type 'ipconfig /renew'. This should have your connection working immediately, but if not, restart.
Users of Win9x/ME should go to the start menu, then 'run'. Type in 'winipcfg'. There are graphical buttons to release and renew the IP addresses of NIC cards. Try to make sure the correct NIC card is selected (if you have more than one installed).
got feedback?Microsoft Knowledge Base Article - Q299357
From command prompt and type netsh int ip reset.
this command requires logfile to be specified, for example: netsh int ip reset c:\resetip.log
This is where IRPStackSize values come into play. An IRPStackSize value, controls the amount of physical storage space and RAM are available for applications. This value may be incorrect, with regard to your network. You will find IRPStackSize in Windows NT, 2000 and XP.
The value ranges from 11-15 for NT and 2000 and from 11-20 for XP (these are conservative value ranges as the software vendor reports higher ranges, but warns, setting the values too high results in wasted system resources.) A value setting of less than 11 in NT and 2000, and less than 12 in XP may cause the infamous ˇ§not enough storage spaceˇ¨ or ˇ§not enough memoryˇ¨ errors when attempting to open/retrieve file folders on your other networked computers.
The following instructions will allow you to safely change the IRPStackSize value. But please always use caution when you are changing values in your registry, as a wrong entry can cause serious problems with the functionality of your computer. If you are not confortable in making these changes, request the services of a computer professional to assist you.
NOTE: Back up your registries first!!!
- Start -> Run
- Type in "regedit" (without the quotation marks)
- Navigate to the following path by single left mouse clicking as you go:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\lanmanserver\parameters
- Double-left mouse click on IRPStackSize
- In the event the IRPStackSize registry setting doesn't exist, create it by single left mouse clicking on "Edit" in the menu bar and then single left mouse click on "New" followed by a single left mouse click on "DWORD Value". The new value will then appear, name the value "IRPStackSize" (without quotation marks) and double left mouse click on the icon.
- Set the decimal under Base to 11 for NT and 2000, and 15 for XP - (Note: I have set my Windows XP to 12 and it works fine. However, when setting the decimal under Base, you may want to increase it by three with-in the range (example: 11 to 14 and so on ,up to 15 for NT and 2000 - 12 to 15 up to 20 for XP) Try the defaults first and if you are still getting the error, try moving up the range until you no longer get the error.
- Close the Registry Editor and Reboot the computer after each edit.
This should take care of the error and allow you to access your other file folders on your networked computers.
For additional reading, concerning this type of error, refer to here
The information concerning XP values are found in this information under the "More Information" paragraph and follow the "Q" numbers related to the error.
Scroll down to PROBLEM: Why do I receive memory or storage space errors after I install new software.
1. Go to your registry [Start->Run-> type in regedit] and find winsock2 at:
2. Rename the file to something like winsock2old.
3. Then goto: control panel -> add/remove programs -> Windows Setup
4. Unclick COMMUNICATIONS, then click apply
5. Click COMMUNICATIONS, then click apply, this should reinstall a working copy of winsock2.
6. Reboot, then you should be back up and running.
If you want to learn more on Winsock, click here.
HOW TO Diagnose and Test TCP-IP or NetBIOS Network Connections in Windows 2000
With Windows XP the tcp/ip stack can be reset by following the instructions here.
If the problem occurs with Windows XP when trying to renew a dynamically assigned address and the error is "An operation was attempted on something that is not a socket" the repair is described here
With other OS versions there are free utilities to help repair the stack. Most of them are covered in section 3.0 of this FAQ.
If all else fails it is time to remove the drivers for the network card and reboot. Upon restarting Windows will start the "Found New Hardware" wizard. Reinstall the card with the latest drivers if possible. Then rebind TCP/IP to the card.
This sit is very helpful to me.
tcp/ip only has 4 "layers" in the stack The OSI model has 7 layers
netsh int ip reset \resetlog.txt Finally I no longer have to restart my computer when the TCP/IP stack decides it won't listen to DHCP anymore. Thank you for the hint!
The three most common causes of basic link problems are a bad cable, bad hardware or duplex mismatches. A basic link problem will show up as the link lights not lighting on one or both networking devices.
This is probably the most common reason for failure. The first thing to do when one or both of the link lights are out is to change the cable to a known working cable.
Use a standard patch cable to connect a Hub/Switch/Router to a computer. Use a crossover cable to connect two networking devices or two computers together. Some ports are able to automatically configure themselves allowing a Patch cable to be used everywhere. Be careful of homemade cables. EIA/TIA 568 cabling use 4 twisted pair. Improper termination may work at low speed but fail at high.
To learn how to correctly make an internet cable look here
B) Duplex Mismatch
There are instances where loss of link could be caused by a duplex mismatch , so it is best to have the network interface cards configured to autonegotiate for the testing. Consult the documentation on your NIC (Network Interface Card) on how to change its speed and duplex settings. Since most home switches are unmanaged there is no way to set their link speed and duplex.
C) Failed equipment
If you still do not see a link light on both devices it's time to start swapping with known working devices.
2) Basic Network connectivity.
Basic network connectivity is limited in this section to seeing other computers on your lan by using the ping tool with a network address. The various methods of name resolution are beyond the scope of this FAQ.
The most frequent causes for loss of basic network connectivity are incorrectly configured IP addresses, firewalls and a corrupted TCP/IP stack.
For a basic introduction into TCP/IP addressing click this link.
A) Correct Address scheme
To see the IP configuration on a computer with NT/2000/XP/98 open a command prompt and type in ipconfig /all. The GUI command in Windows 9X is winipcfg. If one of the two machines is a router see its documentation on how to find the LAN address.
Verify that both machines are on the same subnet. If the addresses are statically assigned then correct one of the machines. Most home lans use automatically assigned (DHCP) addressing with the address coming from a router or an Internet connection sharing (ICS) server.
When one of the devices is set up to hand out the IP address verify that the second device is configured to receive an ip address automatically. This link explains setting up the adapter for 2K/XP, follow these instructions for 98/NT.
If you get an address in the 169.254.x.x range after configuring for basic link then the DHCP server is not working or the client is unable to “see” the DHCP server. Also ensure that the DHCP server's scope is large enough for the amount of PC's on the lan.
If the address is 0.0.0.0 then the problems is most likely the TCP/IP stack.
B) Firewalls blocking
Assuming you have two devices 192.168.0.2 & 192.168.0.3 open a command prompt on .2 and type ping 192.168.0.3. From 192.168.0.3 open a command prompt and type ping 192.168.0.2. If you get replies back both times you're done, good job.
If you received "Request timed out" errors then a firewall on the receiving machine (the one you're not on) is preventing it from replying. Consult the firewall documentation or help for instructions on setting up a "trusted zone". Windows XP has a built in firewall that is turned on as part of the Network Wizard this link explains how to enable and disable ICF.
Having XP's ICF and another firewall on at the same time can cause problems, so pick one firewall and stick with it. If the "trusted zone" or lan is set up and the pings still time out the firewalls must be uninstalled until the network is working. Do not leave the internet connection up with no firewalls installed.
Note: Ping uses Internet Control Message Protocol (ICMP). The Firewall may be configured to pass Ping while blocking ports used for TCP and UDP. If Ping works but other access does not suspect a misconfigured Firewall.
C)Corrupt TCP/IP stack
If all of the above steps are followed or you received a ping reply other than request timed out then the problem is in the TCP/IP stack. This link explains troubleshooting the stack. If the stack was corrupted because of malware, the malware must be completely removed before the stack can be repaired.
Very helpful for layman which doesn't know about networking they can easily manage for troubleshoot the problem. thank you
Assumptions:You can successfully connect to the Internet without the router by connecting your computer directly to the modem (sometimes requiring a special "crossover" cable). If you have a wireless connection, this assumes that the problem is the same whether wired or wireless. Your router and computer are configured to automatically receive IP assignment information through DHCP (usually true by default). Your router is configured with an enabled DHCP server that gives IP addresses to the computers that connect with it (usually true by default).
1. Unplug power to your broadband modem. Unplug power to your router.
2. Shut down your network computers.
3. Check that your devices are connected to the right ports of each device. Wall-to-modem, modem-to-router(WAN port), router(LAN port)-to-computer.
4. Wait for about 20-30 seconds for the modem's circuits to completely discharge before restoring power to the modem.
5. Wait for another 20-30 seconds. This wait allows time for the broadband modem to resynchronize with the network. When you see the lights become stable, and the DSL or Cable light indicates a proper connection, plug in the router.
6. Wait for another 20-30 seconds. This wait allows time for the router to negotiate port speeds and synchronize with the broadband modem. When you see the lights begin to flicker randomly (indicating network traffic), and a light indicating your WAN port is connected, turn on your network computers.
7. After your computers reboot, log in. Wait for 20-30 seconds after your personal settings have finished loaded. This wait allows your computers to automatically receive a renewed or updated IP address, Gateway, and DNS assignment through DHCP.
Notes: If the trouble returns or persists:
A. Your ISP may require that the router's ISP-facing MAC address be registered to your account. Some routers have a setting to use a different MAC address to the WAN port. You can use the MAC address of a device that was previously plugged into the modem (often called "Cloning the MAC"). Or you can call your ISP and give them the MAC address of your router.
B. Consider the possibility that the cable or the ports between the router and broadband modem is defective.
C. If you have a DSL modem, consider putting your DSL modem into Bridge mode -- or, on the modem, choose the option to deliver your IP address to the computer. Visit the support site for your modem's manufacturer or visit the appropriate Equipment Support or ISP forum. As this is a common procedure, searching the posts and FAQs is likely to find your answer.
D. The provider of your modem, router, or ISP service may have additional settings or tips to help you. See the links above.
E. The person who set up your modem may have added firewall rules or filters that are preventing the connection.
F. If this is a brand new product, it may simply have a manufacturing defect that cannot be corrected by the consumer. To be sure, contact technical support for the manufacturer of the product, or if it was provided by your ISP, contact your ISP.