Connecting XP Machine to Home Network trouble

[IrritatedBoy]

Server is called server because it will act as a print server for other computers. It will also have files stored on it that other computers can access. It is not a network server in the traditional sense.

[dahlarbear]

1.  What's your objective (for the new computer)?
     a.  See and access the "shared" files and printers of the network (client)?
     b.  Share some of its files and printers with the network (server)?

2.  Workgroup Name.
     a.  Is the "new" computer a member of a "Domain" or "Workgroup"?
     b.  If workgroup, does it use the same "workgroup" name as the others?

To check:  Start -> right-click My_Computer -> select Properties -> select Computer_Name tab.

3.  Loosely transcribed from reference "Troubleshooting File and Printer Sharing in Microsoft Windows XP".  (Start with guest account subsection "h".)

Verify Server Computer Configuration

When troubleshooting the server computer, you need to verify the following:
     a.  That the File and Printer Sharing for Microsoft Networks component is installed and enabled on the network connection connected to your home or small office network.

     b.  That file sharing is enabled.

     c.  That the Server service is running. If it is not, check the system event log for errors and information about why the Server service did not start.

     d.  That the server computer is sharing the desired folder or printer.

     e.  That if the server computer has ICF enabled on the network connection attached to the home or small office network, then service definitions are defined to allow incoming file and printer sharing traffic.

     f.  That if the server computer has Windows Firewall enabled, then the File and Printer Sharing exception from the Exceptions tab of the Windows Firewall Control Panel applet is enabled.

     g.  That the server computer is not using TCP/IP filtering, which might be preventing response messages from the client computer.

     h.  That the guest account is active for network connections.  In User Accounts (available from Control Panel-User Accounts) the Guest account is off by default. However this setting only applies to the ability to log on the local computer using the Guest account. Simple file sharing relies on guest access to shared folders and printers. To verify that the Guest account is active for network access, do the following:
          (1)  Log on to Windows XP with an administrator account.
          (2)  Click Start, click Run, type cmd, and then press ENTER.
          (3)  In the Command Prompt window, type net user guest, and then press ENTER.
          (4)  If the account is active, a line appears in the output of the command that states Account active               Yes.
          (5)  If the account is not active, type net user guest /active:yes and then press ENTER.
          (6)  Type exit and press ENTER to close the Command Prompt window.

3.  Reference(s):
     a.  Troubleshooting File and Printer Sharing in Microsoft Windows XP
     b.  File and Printer Sharing with Microsoft Windows

     c.  Why Can't I See My Computer on the Network?

     d.  Troubleshooting Computer Browsing on SOHO Networks with Microsoft Windows
     e.  Computer Browsing for SOHO Networks with Microsoft Windows

[IrritatedBoy]

1.  What's your objective (for the new computer)?
     a.  See and access the "shared" files and printers of the network (client)?
     b.  Share some of its files and printers with the network (server)?

Answer to 1 is b.

2.  Workgroup Name.
     a.  Is the "new" computer a member of a "Domain" or "Workgroup"?
     b.  If workgroup, does it use the same "workgroup" name as the others?

Answer to 2. a. Workgroup
Answer to 2. b. same "workgroup"

Server Computer Configuration a - g is set correctly.

Checking on h. now.

[IrritatedBoy]

net user guest command reveals "Account Active   Yes"

[dahlarbear]

1.  Observations.  You shouldn't have to do anything "special" to add the "new" computer to your network.  It should see the other computers and be seen both by IPv4 address and hostname.  You shouldn't have to resort to "static" address assignments or use of the "hosts" file.

It's best to troubleshoot networking issues using a minimum configuration.  Once it's working, add additional components desired one-by-one to see which, if any, "break" the networking.  These additional components might be optional network protocols, firewalls, antivirus/malware software, and/or security software suites.

2.  Question(s):
     a.  Is the "new" computer configured for "simple file sharing"?  To determine:  right-click Start (button) -> Explore -> Tools pull-down menu -> Folder Options... -> View tab -> Advanced settings subsection -> pull down scroll bar -> look for (last entry) "Use simple file sharing (Recommended)".
     b.  What firewall(s) are installed on the "new" computer?  Are they "disabled"?
     c.  What other security software is installed on the "new" computer?

3.  Recommendation.  Start over with your troubleshooting efforts by restricting the scope to just two computers, the router, and restoring their network configurations to a known state.
     a.  Use the "new" computer and one of the other "Windows XP SP3" computers.

     b.  For both computers, remove all of the static IPv4 address entries you added to the "hosts" file.  Only entry I would keep is "127.0.0.1    localhost".  File located at "%systemroot%\system32\drivers\etc".

     c.  Reconfigure DHCP server of router to "automatically" assign IPv4 addresses from a "pool".  This is to reduce the chance of "operator" error/misconfiguration.

If you need DNS addresses try OpenDNS "208.67.222.222", 208.67.220.220"; or Verizon "4.2.2.6", "4.2.2.5"; otherwise just let router pick up the DNS server addresses from your Internet Service Provider (ISP).

     d.  For the "new" computer, reset the Internet Protocol (TCP/IP) from a command prompt.  See http://support.microsoft.com/default.aspx/kb/299357.
         (1)  To open a command prompt, click Start and then click Run. Copy and paste (or type) the following command in the Open box and then press ENTER:
                cmd
         (2).  At the command prompt, copy and paste (or type) the following command and then press ENTER:
                netsh int ip reset c:\resetlog.txt
Note If you do not want to specify a directory path for the log file, use the following command:
                netsh int ip reset resetlog.txt
         (3). Reboot the computer.

     e.  For the "new" computer, verify it is configured for "simple file sharing".

To check:  right-click Start (button) -> Explore -> Tools pull-down menu -> Folder Options... -> View tab -> Advanced settings subsection -> pull down scroll bar -> look for (last entry) "Use simple file sharing (Recommended)".

     f.  For the "new" computer, ensure "File and Printer Sharing" is enabled. See File and Printer Sharing with Microsoft Windows.

     g.  For the Local Area Connection (LAN) of both computers ensure the Internet Protocol (TCP/IP) Properties (General tab) window is configured to:
         (1)  Obtain an IP address automatically
         (2)  Obtain DNS server address automatically

To check:  Start -> Control_Panel -> double-click Network_Connections -> double-click Local Area Connection -> General tab -> Properties button -> General tab -> select Internet Protocol (TCP/IP) -> Properties button -> General tab.

     h.  For the "new" computer, ensure NetBIOS over TCP/IP is set to "Default" and not "Disabled".

To check:  Start -> Control_Panel -> double-click Network_Connections -> double-click Local Area Connection -> General tab -> Properties button -> General tab -> select Internet Protocol (TCP/IP) -> Properties button -> General tab -> Advanced button -> WINS tab -> NetBIOS subsection.

     i.  Reboot both computers.

4.  Basic test algorithm.
     a.  From command prompt on both computers, run "ipconfig /all" to verify TCP/IP configuration.
     b.  Ensure each computer can successfully ping the other both by IPv4 address and hostname.
     c.  Ensure each computer can access the other both by IPv4 address and hostname.  Use Start -> Run -> "\\<IPv4_address>" and "\\<hostname>" without the quotes where you substitute the other computer's address and hostname in place of "<IPv4_address>" or "<hostname>".

5.  Reference(s):
     a.  Diagnose And Repair SOHO networks

[IrritatedBoy]

----------------
1.  Observations.  You shouldn't have to do anything "special" to add the "new" computer to your network.  It should see the other computers and be seen both by IPv4 address and hostname.  You shouldn't have to resort to "static" address assignments or use of the "hosts" file.
----------------

I agree I shouldn't have to do this. However, simply adding the new machine DID NOT WORK!

ALL FIREWALLS ARE OFF! Unless there is a hidden firewall I don't know about they are all off. Is there a way to detect HIDDEN firewalls? That would be helpful.

As far as adding a machine one at a time. I have already done that! Simple sharing is on, and has been on. EVERYTHING works on this network but the new machine. The new machine has the same WORKGROUP as the other machines and simple sharing is ON. NetBios over TCP/IP is set to default. At one point I put it to ON to see if that made a difference. It didn't !

Before I asked for help in this forum I shut everything down but the new machine and one of the XP machines. No luck. Tried to find it with the other XP machine. no luck. Tried it with the WIndows 7 machine. no luck. Can ping by IP address for it on any of the machines and vice versa, but cannot ping by name.

If I add other computers to the network I get better results. Windows 7 is able to locate the computer IF other computers are on the network and I refresh. However, I cannot access anything on the new computer. None of the XP machines can locate the new computer.

The hosts files have allowed me to ping by name and by IP address from ANY computer to ANY other computer. To me that is some progress, but obviously useless from a usable network standpoint.

I know no one gets paid for the advice offered here, but I'm starting to get repeated advice, just in different ways.

This machine not working on the network does not make sense to me, and it doesn't seem to make sense to people here either, so the advice is to start over because this shouldn't be happening.

I'm hoping I can isolate what the problem is. I'm beginning to think it's hardware related. Please read below to see if this helps to determine where the problem is.

NEW INFORMATION

Being frustrated over this whole thing I downloaded Cisco's Network Magic Pro (NMP) and installed it on the new computer. NMP immediately wants to connect to the router. For some reason it cannot find the router from the new XP machine. I also installed NMP on the Windows 7 machine. NMP found the router and mapped my network for me. It found the new computer, but listed it as a device. I changed it to a computer in NMP and it remapped the network. It found the new computer and recognized that it had Windows XP with SP3. However it said that NMP was NOT installed on the new computer. That might be because NMP never found the router on the new XP machine.

I can't figure why NMP is unsuccessful at finding the router. ipconfig gives the correct IP address, which is what NMP seems to be looking for. I have tried all the router plugs and switched cables etc. It makes no difference.

I AM tempted to try one part of starting over. Is it possible to uninstall the network software on the new machine and reinstall it clean--like it was never on the machine before?

I'm wondering if something is corrupted somehow.

Anyway I appreciate all the help.

That is the state I am in at this point.