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.