Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Network nightmare path not found 1

Status
Not open for further replies.

starhawkkk

IS-IT--Management
Feb 5, 2003
9
US
Here it is I have two computers runing xp pro the host can see the client in network neiborhood and when I try to access it I get access denied check with the administrator of that computer to see if you have permission network path not found and I cant ping the client? now when I go to the client computer it dose not see the host computer at all no ping or anything both nic cards say they are working properly and I manually set the IP addresses the same I also tried using dhcp no joy any Ideas I am fresh out thank you for any input
 
Make Sure that the ip of all machines which you have manually, belongs to same range and give the same subnet mask. and if it is not subnetted no need of giving gateway.
 
the IP addresses are the same I have checkedmany times any other ideas appreacated
 
Have you disabled xp's firewall? Have you disabled Simple File Sharing?
 
the fire wall on the client computer is not enabled not sure about the simple file sharing how do I check that
 
You can check it by right clicking on any folder, select Sharing & Security. If you don't have a security tab, you're using Simple File Sharing.
 
A lot going on here. I think we need to clarify a few points. One thing at a time.

Biggest thing that troubles me is your statement that you 'manually set the IP addresses the same'. Do you mean that both computers now have the same IP address? That will not work. Both should be on the same network. The first three numbers of the IP should be the same, but the last has to be different. For example, you could use 192.168.1.100 for one and 192.168.1.101 for the other. The last number is not really important, just so they are not the same.

You stated that there is 'no ping'. What do you mean? When you use ping, it always gives either a good reply or an error. There are several different errors, and each means something a little different.

Start with 'ping 127.0.0.1' from each computer. 127.0.0.1 is an internal loopback interface, it should work even if you have other network problems unless you have general problems with TCP/IP.

Next ping the address of the computer you are working on, then try the address of the other computer. When reporting results, remember that the specific error is important.

For file sharing to work properly,
A) the workgroup name on both computers must be the same.
B) the user names and passwords must be the same on both computers.
C) each computer must have at least one shared resource.
D) the user must have the proper permissions to access the resource.

I would work on getting a good ping response first, then look to the file sharing issues.
 
the addresses are 192.168.0.1 for the host the client is 192.168.0.10 the error is no reply timed out when I ping 127.0.0.1 I get 4 sent 4 received lost 0 both computers
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\STARHAWK>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\DOCUME~1\STARHAWK>
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\STARHAWK>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\DOCUME~1\STARHAWK>ping 192.168.0.10

Pinging 192.168.0.10 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\DOCUME~1\STARHAWK>
as for the user and password is that the accounts under user or something else
the files are shared and so are the hard drives
as for permisions where is that at
 
Ok, now we're getting somewhere. Since you can't ping, you won't be able to do anything else at all until that is fixed. So, let's fix the ping problem.

How are the two computers connected? Do they go through a hub/switch, or are they connected directly?

If through a hub/switch, then you should be using a straight through cable on each; if they are connected directly, then you need a crossover cable between them.

Do you have a link light on the two nics?
 
only the fire wall to the internet other then that none the link lights are on at the nicks I am using a hub the cabling is right and there are lights on the hub here is the kicker if I run millenia on both computers and run the net work wizard the network works fine that is what I had until I got xp installed on both computers now no ping or net work I wonder if xp could be putting in the wrong drivers for one or both
 
This device is working properly.

If you are having problems with this device, click Troubleshoot to start the troubleshooter.No conflicts. yes they are shown with no conflicts
 
How are you getting your IP address? At each machine, open a command prompt and type ipconfig /all. Post back the results.
 
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\STARHAWK>ipconfig /all

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-07-95-4F-A5-DB
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.1

PPP adapter My ISP:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 67.217.247.23
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 67.217.247.23
DNS Servers . . . . . . . . . . . : 198.6.100.125
198.6.1.125

C:\DOCUME~1\STARHAWK>
here it is
 
the last post was the host computer

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\STARHA~1>ipconfig /all

Windows IP Configuration

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

Ethernet adapter seth1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-30-BD-08-C4-EB
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1

C:\DOCUME~1\STARHA~1>
 
This one here shows your default gateway is set on the PPP adapter:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-07-95-4F-A5-DB
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.1

PPP adapter My ISP:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 67.217.247.23
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 67.217.247.23
DNS Servers . . . . . . . . . . . : 198.6.100.125
198.6.1.125

Technically, if you are pinging another PC on the same subnet, then it shouldn't have to use the gateway address. But, your PC may be trying to use the PPP adapter instead of your Ethernet adapter. Try disabling the dial-up adapter (then do ipconfig/release and ipconfig/renew)and see if you can then talk to your local network. You should see the gateway, etc addresses filled in on the Realtek NIC then.

I'm thinking your XP PC is confusing itself.
 
I guess there's no way to edit posts after hitting submit.

I noticed your nics aren't using DHCP, so don't bother with the ipconfig/release ipconfig/renew.

Good luck.
 
NetBios can get a little funky. I have seen 'Network Path Not Found' errors when I know full well that the machine receiving those errors is alive and well on the Lan. I've been able to fix those problems by installing NetBEUI, even though I didn't really need it for anything else.

This is a slightly different issue than I think you're having, but the fix might work. - - - -

Bryan
 
Netbeui did not work eather are there any other solutions that we missed thank you all for trying
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top