Connecting XP Machine to Home Network trouble

[IrritatedBoy]

Hello,

I have network setup at home that works fine among the current machines. The computers can find each other and the networked printer.

I have added a new computer to the network but am unable to consistently find it. I can ping the IP of the new computer but not the name from the current computers. Conversely I can ping all the old computers and printer from the new computer but I cannot ping them by their name.

There is one portable computer off line right now--they are not here at the moment. I suspect that the new computer has been assigned it's normal IP address (103). Could this be the problem?

I was going to override the DHCP assignment, but then I have to add the DNS as well and I don't know how to find that out.

When it comes to networking, I only know what is in computer help on the machine. It always tells me to ask the network Administrator.

[IrritatedBoy]

I should have added the following. One Machine is Windows 7 x64, one is XP Home SP3, one is XP Pro SP3, and the new one is XP PRO SP3.

[IrritatedBoy]

More info I should have included!!

Firewalls on XP machines are off.

Firewall on Windows 7 machine has been turned on and off with no resolution. Network discovery is on. All passwords are set to off. Basically networking works with the exception of the new computer

[IrritatedBoy]

More info:

"ipconfig /all" on the new computer provides the following

Windows IP Configuration



        Host Name . . . . . . . . . . . . : SERVER
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : NVIDIA nForce Networking Controller #2
        Physical Address. . . . . . . . . : 00-01-6C-F4-99-DF
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.0.105
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1
        DHCP Server . . . . . . . . . . . : 192.168.0.1
        DNS Servers . . . . . . . . . . . : 192.168.0.1
        Lease Obtained. . . . . . . . . . : Wednesday, February 03, 2010 4:09:53 PM
        Lease Expires . . . . . . . . . . : Wednesday, February 10, 2010 4:09:53 PM

"Ipconfig /all" on the Windows 7 machine provides the following

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Main-Desktop
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 00-26-18-D7-51-BE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::4166:6e3a:759d:78e0%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.104(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, February 01, 2010 2:59:37 PM
   Lease Expires . . . . . . . . . . : Wednesday, February 10, 2010 3:29:39 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 234890776
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-DB-F6-F7-00-26-18-D7-51-BE
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{66539C79-621A-433A-B0A4-5725C2EFC02C}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:8bc:696:3f57:ff97(Preferred)
   Link-local IPv6 Address . . . . . : fe80::8bc:696:3f57:ff97%13(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

[IrritatedBoy]

the ipconfig information was obtained after I manually changed the ip address to 192.168.0.105 and then turned DHCP back on. It assigned the same address.

Now I can no longer ping the machine!

If I manually set the address back to 192.168.0.103 I can ping again, but cannot ping by name!

[Computer_Commando]

Are you using a router or attempting to configure one of the computers as a router.  If the latter, get a router.
If router then:
Are you using default settings on router?
Enable DHCP on router and computers.
Call up router in your browser:  192.168.0.1
Find DHCP client table.

[IrritatedBoy]

Thanks for responding!

Using D-link router.
Default settings.
DHCP enabled on router and computers

Clients show up in table.

Network works fine with the exception of the new computer. Can ping by IP, but not by name.

[Computer_Commando]

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ping.mspx?mfr=true

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_tcpip_pro_pingconnect.mspx?mfr=true

Can ping computer by IP address but not by computer name

[IrritatedBoy]

After reading the referred information I forced the router to assign the Names and specific IP adresses to each devices MAC address.

I can now ping everything by name on the network from the server. However I still cannot ping the server by name from other computers.

All I have accomplished so far is the ability to ping FROM the server by name.

I checked to see if sharing was turned on etc. Yep.

net view results are like the ping results. I can see other computers from the Server, but not the server from the other computers.

However the computers do not show up in Workgroup view on the Server.

[IrritatedBoy]

Forogt to mention that I put the names and IP addresses that the Router assigns in the Hosts file on each computer (including the server of course).

[IrritatedBoy]

SOME PROGRESS.

I forced a new IP address on the computer named server in the router--one that hadn't been used yet. Now I can successfully ping the server, but net view does not find \\server. I get error 53.

How can I be sure that the file and print sharing service is running?

thanks

[IrritatedBoy]

To be more clear.

the net view \\server command in the cmd box works on the computer named "server" but does not work anywhere else.

I can see the computer named "server" in windows on all the computers now, but clicking on it gives the famous "network path was not found" error.

[dahlarbear]

From one of the "good" Windows XP machines try to display the network shares of the "problem" Windows XP machine using its numeric IPv4 address:

Use Start -> Run -> \\192.168.0.105

[IrritatedBoy]

Hi,

Thanks for helping out.

I tried your suggestion. "Network path not found" It finds everything else though.

[Computer_Commando]

After reading the referred information I forced the router to assign the Names and specific IP adresses to each devices MAC address.
I can now ping everything by name on the network from the server. However I still cannot ping the server by name from other computers.
All I have accomplished so far is the ability to ping FROM the server by name.
I checked to see if sharing was turned on etc. Yep.
Net view results are like the ping results. I can see other computers from the Server, but not the server from the other computers.
However the computers do not show up in Workgroup view on the Server.

What distinguishes Server from the other computers?  They're all on the same router.  Server is not acting as a server, unless, your physical connection of the router, Server & computers is not a "normal" configuration, i.e., all computer's LAN ports, including Server are connected to router's LAN ports.

[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.