[resolved] XP computers won't talk via router

dillburt · 07-19-2005, 07:39 PM

I am using a D-Link DCM-100 cable modem into a Netgear RP614 4-port router. This has been set up and working for 3 years with 2 computers, one running Win98SE and one running Windows XP Pro, sharing all files, folders and printer, as well as internet. The third router port goes to my Cisco ATA-186 analog telephone adapter, for my Vonage VoIP phone service. All of the above have been working fine for 3 years.

Last week I purchased a third computer,a Dell Dimension 9100 running Windows XP Media Center Edition. I connected its ethernet card to the fourth port on the router and on the initial bootup everything came up working. The next day, when I returned to the new computer, there were problems. I don't know what changed (the computer was not touched), but here is what I have:

All IP addresses are DHCP assigned. The router (gateway) is 192.168.0.1. The Cisco ATA is 192.168.0.2, XP Pro computer is 192.168.0.3, new XP media center computer is 192.168.0.4, and Win98SE computer is 192.168.0.5. All of these IP addresses ping successfully from any of the 3 computers EXCEPT 192.168.0.4 (the new XP computer). Pinging this address always times out, even when done from that very computer. All computers are in the same workgroup, and each has a unique name. The workgroup can be viewed from all 3 computers, and in each case all 3 show up by name within the workgroup. Looking at the router configuration (from the router config software), each port is shown correctly with the IP address and the corresponding computer name, and no errors are detected. Each of the 3 computers has the Windows firewall turned OFF. All drives on each computer are set up for sharing. I am using the same user name and password on the 2 XP computers, and this name is set up as an administrator. The Win98SE computer communicates perfectly in both directions with both of the XP computers, with full file sharing. BUT, the two XP computers will not communicate with each other. Any attempt to access files or folders from one XP computer on the other XP computer, or even double-clicking the computer name from within the workgroup, results in this message: "\\name\drive is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to see if you have access permissions. The network path was not found."

Oh yes, I can also ping the NIC on each computer (127.0.0.1) successfully.
I need to get the 2 XP computers talking! Any ideas or suggestions would be most welcome.

nonameyet · 07-22-2005, 04:40 PM

just wondering how You made out, since, NOBODY replied...

I'm in the Same boat with a Brand New Dell 600m running win xp...

I have several other computers on my network, with No Problems.

If, I figure it out, I'll let You know

**johnwill** · 07-22-2005, 05:26 PM

You seem to have two problems. The new computer appears to have some sort of hardware issue. Let's see the output of:

Open a DOS window and type:

IPCONFIG /ALL >C:RESULT.TXT

Open C:\RESULT.TXT with Notepad and copy/paste the entire results here.

The two XP machines that on the network appear to have a permissions issue. Have you made sure there is a user account with the same name/password as is used to logon to the other XP machine?

dillburt · 07-23-2005, 08:36 AM

Since I posted the original message, a friend suggested that I create a host file listing the ip addresses and names of the three computers. Since doing this, I can now access files and printers attached to the OLD Xp pro computer from the NEW xp computer. But I still can't access the NEW one from the OLD one. In spite of this, all through this I have always had full access to both XP computers from the old Win98 computer. The new computer, at 192.168.0.4, still does not ping successfully from anywhere, even from its own keyboard.

Here is the result file you requested: (from the new XP computer)

Windows IP Configuration

Host Name . . . . . . . . . . . . : D9100

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : hsd1.fl.comcast.net.

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : hsd1.fl.comcast.net.

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection

Physical Address. . . . . . . . . : 00-12-3F-6F-4F-80

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.4

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. . . . . . . . . . : Friday, July 22, 2005 6:56:24 PM

Lease Expires . . . . . . . . . . : Monday, January 18, 2038 11:14:07 PM

dillburt · 07-23-2005, 08:40 AM

I failed to answer your other question: I was using fast user switching with no passwords. A few days ago I changed to password logon on both XP computers. It didn't help. The user names have always been identical.

**johnwill** · 07-23-2005, 12:27 PM

Try these fixes on the new XP system.

TCP/IP stack repair options for use with Windows XP with SP2.

For these commands, Start, Run, CMD to open a command prompt.

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset TCP/IP stack to installation defaults. netsh int ip reset [log_file_name]

Note: the log_file_name needs to be specified, e.g. netsh int ip reset reset.log

ebackhus · 07-23-2005, 01:50 PM

[ping] 127.0.0.1

dillburt · 07-23-2005, 01:54 PM

Thanks for your help. I did both of these resets, then restarted the computer. Unfortunately, I'm still unable to ping the system.

I don't understand how I can't even ping it, but can access it by name from my old Win98 system.

**johnwill** · 07-24-2005, 09:36 AM

I don't understand that either, the only thing that comes to mind is a firewall that is specifically blocking ICMP (ping) requests.

dillburt · 07-24-2005, 07:17 PM

Windows firewall is turned off on each computer. I don't know where else to look for any firewall settings. I can manually change the IP address of the new XP system, but that doesn't change my inability to ping successfully. What would allow the Win98 system to reach the XP system by name while the other XP system cannot do so?

dillburt · 07-24-2005, 07:18 PM

I did ping the NIC at 127.0.0.1 (successfully) before I first posted this problem. That has never been a problem.

**johnwill** · 07-25-2005, 05:41 PM

I think I'd have to see this to know what's happening. It's possible to have a network connection and still not be able to ping. For instance, if NETBEUI or IPX is installed on both ends in addition to TCP/IP, you'll be able to connect even if TCP/IP isn't configured correctly.

dillburt · 07-25-2005, 07:05 PM

NetBeui IS installed on all three computers. Earlier, before my first post here, someone advised me to install it on the new XP system to solve my network problem. It solved the problem, but only to the extent of enabling reliable communication between the XP and the Win98 computer.

Now someone is suggesting that I install TCP/IP version 6 as a fix. Any thoughts on this? (Also, how to do it?)

**johnwill** · 07-26-2005, 05:27 PM

Do NOT install IPv6, it will NOT solve any of these issues! There is no reason for 99.99% of the computing public to have IPv6 currently, and it brings nothing to the party.

The fact that NETBEUI is installed all around explains why you can network locally without issue, you're probably not using TCP/IP.

I'm at a loss about the ping failure, since this is almost always a firewall issue.

dillburt · 07-30-2005, 09:13 AM

Thanks for the info on IPv6...I don't want it if I don't need it.

Assuming I have a firewall problem of some sort, which I can't see...does netbeui get around firewalls somehow?

**johnwill** · 07-30-2005, 11:36 AM

Yep, NETBEUI is a non-routable protocol, so it's only on the local LAN. The Firewall is just for TCP/IP, IPX or NETBEUI jump right over.

dillburt · 08-01-2005, 06:20 PM

Well, I have the answer at last. It seems that when I received my new computer from Dell, Norton Internet Security was already installed and activated, including Norton Personal Firewall. I kept verifying that Windows firewall was turned off, unaware that Norton had a separate firewall. Now that I have turned off Norton firewall, I can ping successfully. Whew!

Thanks for all the support along the way.

Now, if I could just figure out how to mark this thread resolved. I don't find that option in Thread Tools.

07-19-2005, 07:39 PM	#1 (permalink)
dillburt Registered User Join Date: Jul 2005 Posts: 16 OS: XP	XP computers won't talk via router I am using a D-Link DCM-100 cable modem into a Netgear RP614 4-port router. This has been set up and working for 3 years with 2 computers, one running Win98SE and one running Windows XP Pro, sharing all files, folders and printer, as well as internet. The third router port goes to my Cisco ATA-186 analog telephone adapter, for my Vonage VoIP phone service. All of the above have been working fine for 3 years. Last week I purchased a third computer,a Dell Dimension 9100 running Windows XP Media Center Edition. I connected its ethernet card to the fourth port on the router and on the initial bootup everything came up working. The next day, when I returned to the new computer, there were problems. I don't know what changed (the computer was not touched), but here is what I have: All IP addresses are DHCP assigned. The router (gateway) is 192.168.0.1. The Cisco ATA is 192.168.0.2, XP Pro computer is 192.168.0.3, new XP media center computer is 192.168.0.4, and Win98SE computer is 192.168.0.5. All of these IP addresses ping successfully from any of the 3 computers EXCEPT 192.168.0.4 (the new XP computer). Pinging this address always times out, even when done from that very computer. All computers are in the same workgroup, and each has a unique name. The workgroup can be viewed from all 3 computers, and in each case all 3 show up by name within the workgroup. Looking at the router configuration (from the router config software), each port is shown correctly with the IP address and the corresponding computer name, and no errors are detected. Each of the 3 computers has the Windows firewall turned OFF. All drives on each computer are set up for sharing. I am using the same user name and password on the 2 XP computers, and this name is set up as an administrator. The Win98SE computer communicates perfectly in both directions with both of the XP computers, with full file sharing. BUT, the two XP computers will not communicate with each other. Any attempt to access files or folders from one XP computer on the other XP computer, or even double-clicking the computer name from within the workgroup, results in this message: "\\name\drive is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to see if you have access permissions. The network path was not found." Oh yes, I can also ping the NIC on each computer (127.0.0.1) successfully. I need to get the 2 XP computers talking! Any ideas or suggestions would be most welcome.

07-22-2005, 04:40 PM	#2 (permalink)
nonameyet Registered User Join Date: Dec 2004 Posts: 8 OS: win 98SE	just wondering how You made out, since, NOBODY replied... I'm in the Same boat with a Brand New Dell 600m running win xp... I have several other computers on my network, with No Problems. If, I figure it out, I'll let You know __________________ Ring, Ring, Phone man...

07-22-2005, 05:26 PM	#3 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,921 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	You seem to have two problems. The new computer appears to have some sort of hardware issue. Let's see the output of: Open a DOS window and type: IPCONFIG /ALL >C:RESULT.TXT Open C:\RESULT.TXT with Notepad and copy/paste the entire results here. The two XP machines that on the network appear to have a permissions issue. Have you made sure there is a user account with the same name/password as is used to logon to the other XP machine? __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

07-23-2005, 08:36 AM	#4 (permalink)
dillburt Registered User Join Date: Jul 2005 Posts: 16 OS: XP	Reply to johnwill Since I posted the original message, a friend suggested that I create a host file listing the ip addresses and names of the three computers. Since doing this, I can now access files and printers attached to the OLD Xp pro computer from the NEW xp computer. But I still can't access the NEW one from the OLD one. In spite of this, all through this I have always had full access to both XP computers from the old Win98 computer. The new computer, at 192.168.0.4, still does not ping successfully from anywhere, even from its own keyboard. Here is the result file you requested: (from the new XP computer) Windows IP Configuration Host Name . . . . . . . . . . . . : D9100 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : hsd1.fl.comcast.net. Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : hsd1.fl.comcast.net. Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection Physical Address. . . . . . . . . : 00-12-3F-6F-4F-80 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.0.4 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. . . . . . . . . . : Friday, July 22, 2005 6:56:24 PM Lease Expires . . . . . . . . . . : Monday, January 18, 2038 11:14:07 PM

07-23-2005, 08:40 AM	#5 (permalink)
dillburt Registered User Join Date: Jul 2005 Posts: 16 OS: XP	Addl reply to johnwill I failed to answer your other question: I was using fast user switching with no passwords. A few days ago I changed to password logon on both XP computers. It didn't help. The user names have always been identical.

07-23-2005, 12:27 PM	#6 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,921 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	Try these fixes on the new XP system. TCP/IP stack repair options for use with Windows XP with SP2. For these commands, Start, Run, CMD to open a command prompt. Reset WINSOCK entries to installation defaults: netsh winsock reset catalog Reset TCP/IP stack to installation defaults. netsh int ip reset [log_file_name] Note: the log_file_name needs to be specified, e.g. netsh int ip reset reset.log __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

07-23-2005, 01:50 PM	#7 (permalink)
ebackhus Manager, Design Join Date: Apr 2005 Location: SATX Posts: 14,335 OS: WinXP Pro SP3/Windows 7 RTM My System Blog Entries: 28	[ping] 127.0.0.1 __________________ ----------------------------- There are no dumb questions, unless a customer is asking them. Help in the fight against cancer and other serious illnesses.

07-23-2005, 01:54 PM	#8 (permalink)
dillburt Registered User Join Date: Jul 2005 Posts: 16 OS: XP	Reply to johnwill Thanks for your help. I did both of these resets, then restarted the computer. Unfortunately, I'm still unable to ping the system. I don't understand how I can't even ping it, but can access it by name from my old Win98 system.

07-24-2005, 09:36 AM	#9 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,921 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	I don't understand that either, the only thing that comes to mind is a firewall that is specifically blocking ICMP (ping) requests. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

07-24-2005, 07:17 PM	#10 (permalink)
dillburt Registered User Join Date: Jul 2005 Posts: 16 OS: XP	Reply to johnwill Windows firewall is turned off on each computer. I don't know where else to look for any firewall settings. I can manually change the IP address of the new XP system, but that doesn't change my inability to ping successfully. What would allow the Win98 system to reach the XP system by name while the other XP system cannot do so?

07-24-2005, 07:18 PM	#11 (permalink)
dillburt Registered User Join Date: Jul 2005 Posts: 16 OS: XP	Reply to ebackhus I did ping the NIC at 127.0.0.1 (successfully) before I first posted this problem. That has never been a problem.

07-25-2005, 05:41 PM	#12 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,921 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	I think I'd have to see this to know what's happening. It's possible to have a network connection and still not be able to ping. For instance, if NETBEUI or IPX is installed on both ends in addition to TCP/IP, you'll be able to connect even if TCP/IP isn't configured correctly. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

07-25-2005, 07:05 PM	#13 (permalink)
dillburt Registered User Join Date: Jul 2005 Posts: 16 OS: XP	Reply to johnwill NetBeui IS installed on all three computers. Earlier, before my first post here, someone advised me to install it on the new XP system to solve my network problem. It solved the problem, but only to the extent of enabling reliable communication between the XP and the Win98 computer. Now someone is suggesting that I install TCP/IP version 6 as a fix. Any thoughts on this? (Also, how to do it?)

07-26-2005, 05:27 PM	#14 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,921 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	Do NOT install IPv6, it will NOT solve any of these issues! There is no reason for 99.99% of the computing public to have IPv6 currently, and it brings nothing to the party. The fact that NETBEUI is installed all around explains why you can network locally without issue, you're probably not using TCP/IP. I'm at a loss about the ping failure, since this is almost always a firewall issue. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

07-30-2005, 09:13 AM	#15 (permalink)
dillburt Registered User Join Date: Jul 2005 Posts: 16 OS: XP	Reply to johnwill Thanks for the info on IPv6...I don't want it if I don't need it. Assuming I have a firewall problem of some sort, which I can't see...does netbeui get around firewalls somehow?

07-30-2005, 11:36 AM	#16 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,921 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	Yep, NETBEUI is a non-routable protocol, so it's only on the local LAN. The Firewall is just for TCP/IP, IPX or NETBEUI jump right over. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

08-01-2005, 06:20 PM	#17 (permalink)
dillburt Registered User Join Date: Jul 2005 Posts: 16 OS: XP	Solved! Well, I have the answer at last. It seems that when I received my new computer from Dell, Norton Internet Security was already installed and activated, including Norton Personal Firewall. I kept verifying that Windows firewall was turned off, unaware that Norton had a separate firewall. Now that I have turned off Norton firewall, I can ping successfully. Whew! Thanks for all the support along the way. Now, if I could just figure out how to mark this thread resolved. I don't find that option in Thread Tools.