I have a small office network running XP Pro. One pc on the network is intermittently available. I periodically get the following error message: "\\PC1 not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The network path was not found." This pc is set up the same as all others on the network. This on again off again behaviour occurs from only one other pc on the network. rebooting the client machine usually works, but is a real pain. typing "\\pc1" in the path window at the top of explorer will sometimes refresh the connection, but not always. On the right side of explorer the pc name for PC1 will show up as "unknown". XP is patched to the latest service packs from MS. Any suggestions will be appreciated. Thanks

[Reply or follow-up to this message]

Have you checked the connections? Maybe the cables are damaged, but you may not be 
able to see this on the outside. Perhaps the network adapter is not working as it 
should. I'd try replacing the cable (maybe swap it with another one) and if that 
doesn't work, try swapping network cards.

[Reply or follow-up to this message]

Check the firewall in the local area connection of the PC you are trying to access. If it is activated it may be preventing you from getting past the firewall and into the files and drives on that machine.........


On Tuesday, November 18, 2003 at 3:59 am, Lee Coda wrote:
>I have a small office network running XP Pro. One pc on the network is intermittently
>available. I periodically get the following error message: "\\PC1 not accessible.
> You might not have permission to use this network resource. Contact the administrator
>of this server to find out if you have access permissions. The network path was
>not found." This pc is set up the same as all others on the network. This on again
>off again behaviour occurs from only one other pc on the network. rebooting the
>client machine usually works, but is a real pain. typing "\\pc1" in the path window
>at the top of explorer will sometimes refresh the connection, but not always. On
>the right side of explorer the pc name for PC1 will show up as "unknown". XP is
>patched to the latest service packs from MS. Any suggestions will be appreciated.
> Thanks
>

[Reply or follow-up to this message]

     This is a very odd problem that I have experianced in the past.  This may or 
may not be the answer for you but something you may want to check.  Took me days 
to find the problem since it did not always occur and was so random.  Here is what 
I found the problem to be.
     Seems that what was happening in Windows XP was that it would randomly select 
which connection it wanted to use every time it booted.  Sometimes it would select 
the LAN card and other times it would select the 1394 network connection.  Of course 
there was no cable connected to the 1394 connection.  Even though PC would show up 
on the network it was not accessable.  I believe the problem to be on the connecting 
XP machine randomly deciding to use the 1394 connection instead of the lan/network 
connection when both were available to it.            
     Solution was to disable the 1394 network connection on the machine that would 
not show up or be accessable.  Once I disable that it never happened again.  All 
computers on the network where 100% connected and accessable after that.  It happened 
once again after that because for some unknown reason the 1394 connection and been 
enabled again.  Once disable problem went away.  Simple fix, days to find the problem.

[Reply or follow-up to this message]

This sounds very much like the problem I am having with one laptop connected to the 
office LAN. 
This computer is mobile and sometimes connects using a dial up service.  It began 
having problems detecting the NIC and started trying to use dialup. However, I'm 
not sure which device I need to disable. 

As I am a network neophyte, and it only appears that this computer only has one high 
speed network connection, do you have any suggestions what I might do to solve this 
one? It has been suggested to me that I replace the NIC, but the laptop doesn't appear 
to have any problems connecting to the internet. It is only now having problems recognizing 
the work group which it was connected to before. 

I have run the Networking Wizard a number of times, I've tried rebooting the computer 
hoping that would fix it. I know that the firewall on that computer as well as on 
the computers it is to network with has been disabled. I tried updating XP so that 
it has all the latest updates and patches. 

So far, nothing has resolved this and I'm considering reinstalling XP and starting 
from scratch. Any suggestions?
Thanks!
Murleen

        

>     Solution was to disable the 1394 network connection on the machine that would 

>not show up or be accessable.  Once I disable that it never happened again.  All 

>computers on the network where 100% connected and accessable after that.  It happened 

>once again after that because for some unknown reason the 1394 connection and been 

>enabled again.  Once disable problem went away.  Simple fix, days to find the problem.

[Reply or follow-up to this message]

Check Services under Administrative Tools off All Programs off the Start Menu. Check that the "Server" services is Started. I found mine was paused. Once I "Restarted" it, I was able to connect. Click here to see how to add the Administrative Tools menu to your Start Menu (it's not obvious): http://www.microsoft.com/windowsxp/expertzone/tips/november/coleman1.asp

[Reply or follow-up to this message]

Here's another thing you might want to try. I found this page after entering a Google search on the error message text, because I have been struggling with the same problem. I tried all of the tips here, but none worked so finally out of trial and error I shut off Norton Internet Security (professional) and all works fine. I configured the firewall to allow the address range of 192.168.1.1 through 192.168.1.149, but apparently NISP does a lot of other things to thwart your network. I need to study up on NISP and find out how to make it live with my network, but for now I am relying on the router firewall to protect my computer from the Internet.


On Tuesday, November 18, 2003 at 3:59 am, Lee Coda wrote:
>I have a small office network running XP Pro. One pc on the network is intermittently
>available. I periodically get the following error message: "\\PC1 not accessible.
> You might not have permission to use this network resource. Contact the administrator
>of this server to find out if you have access permissions. The network path was
>not found." This pc is set up the same as all others on the network. This on again
>off again behaviour occurs from only one other pc on the network. rebooting the
>client machine usually works, but is a real pain. typing "\\pc1" in the path window
>at the top of explorer will sometimes refresh the connection, but not always. On
>the right side of explorer the pc name for PC1 will show up as "unknown". XP is
>patched to the latest service packs from MS. Any suggestions will be appreciated.
> Thanks
>

[Reply or follow-up to this message]

I am also experiencing this same problem. I've tried most of what everyone has posted here, including restarting the server (which was already enabled) and other things. The problem seems to be quite random, while sometimes I can access the workgroup, other times I cant, one thing remains constant though, I just cannot access other compters within the same network. Following from your suggestion, when you said disable the 1394 internet connection, were you referring to the internet connection sharing? Btw, I am running windows xp professional.


On Thursday, February 12, 2004 at 5:50 am, Chuck Flanagan wrote:
>
> This is a very odd problem that I have experianced in the past. This may or
>may not be the answer for you but something you may want to check. Took me days
>to find the problem since it did not always occur and was so random. Here is what
>I found the problem to be.
> Seems that what was happening in Windows XP was that it would randomly select
>which connection it wanted to use every time it booted. Sometimes it would select
>the LAN card and other times it would select the 1394 network connection. Of course
>there was no cable connected to the 1394 connection. Even though PC would show up
>on the network it was not accessable. I believe the problem to be on the connecting
>XP machine randomly deciding to use the 1394 connection instead of the lan/network
>connection when both were available to it.
> Solution was to disable the 1394 network connection on the machine that would
>not show up or be accessable. Once I disable that it never happened again. All
>computers on the network where 100% connected and accessable after that. It happened
>once again after that because for some unknown reason the 1394 connection and been
>enabled again. Once disable problem went away. Simple fix, days to find the problem.

[Reply or follow-up to this message]

I have same problem but this may help.   I typed  \\192.168.0.2\sharedfolder (from 
Start, Run) and succeeded in connecting  to the sharedfolder on the other PC. I then 
suspected name resolution problem.  I proceeded by appending file C:\windows\system32\etc\hosts, 
using notepad, as follows.  

127.0.0.1       localhost
192.168.0.2   gateway

(gateway is the name of the machine I want to access and 192.168.0.2 is its IP address.). 
Remember to save the file after modification & that should do it.  

Tunji







On Sunday, July 4, 2004 at 3:10 am, tzejay wrote:

>I am also experiencing this same problem.  I've tried most of what everyone has 
posted 

>here, including restarting the server (which was already enabled) and other things. 

> The problem seems to be quite random, while sometimes I can access the workgroup, 

>other times I cant,  one thing remains constant though, I just cannot access other 

>compters within the same network.  Following from your suggestion, when you said 

>disable the 1394 internet connection, were you referring to the internet connection 

>sharing? Btw, I am running windows xp professional. 

>

>

> 

[Reply or follow-up to this message]

I dont have another network connection, i3894 or whatever. So I could not disable that. Restarting the Server service didn't do the trick either. It looks like I'll need to reformat because I have no other solution besides rebooting when I lose access to the network drives. Unless anyone out there has a solution, its gonna be an ol reformat :( AxS


On Sunday, July 4, 2004 at 9:43 am, Tunji wrote:
>I have same problem but this may help. I typed \\192.168.0.2\sharedfolder (from
>Start, Run) and succeeded in connecting to the sharedfolder on the other PC. I then
>suspected name resolution problem. I proceeded by appending file C:\windows\system32\etc\hosts,
>using notepad, as follows.
>
>127.0.0.1 localhost
>192.168.0.2 gateway
>
>(gateway is the name of the machine I want to access and 192.168.0.2 is its IP address.).
>Remember to save the file after modification & that should do it.
>
>Tunji
>
>
>

[Reply or follow-up to this message]

Please, all you need to do is double-click on My Computer on the machine that you cannot access, right-click on the Shared Documents Folder, click "Sharing & Security", untick the "Share this folder on the network" box, go out, and then go back in, re-tick it, give the name again i.e. SharedDocs, and this resets the sharing privilege. Have fun sharing - Philip


On Wednesday, October 20, 2004 at 4:50 am, AxS wrote:
>I dont have another network connection, i3894 or whatever. So I could not disable
>that. Restarting the Server service didn't do the trick either. It looks like I'll
>need to reformat because I have no other solution besides rebooting when I lose access
>to the network drives.
>
>Unless anyone out there has a solution, its gonna be an ol reformat :(
>
>AxS
>
>
>

[Reply or follow-up to this message]

*** IMPORTANT *** IMPORTANT *** Also, if the above does not work, simply amend the following regkey from hexadecimal "1" to "0": HKLM\SYSTEM\CurrentControlSet\Control\Lsa\restrictanonymous. Have fun networking. Philip


On Monday, December 13, 2004 at 11:53 am, Philip Barnstead wrote:
>Please, all you need to do is double-click on My Computer on the machine that you
>cannot access, right-click on the Shared Documents Folder, click "Sharing & Security",
>untick the "Share this folder on the network" box, go out, and then go back in, re-tick
>it, give the name again i.e. SharedDocs, and this resets the sharing privilege.
>Have fun sharing - Philip
>
>
>

[Reply or follow-up to this message]

Well - In total frustration, I have tried each tip I could find on the WEB - All 
to no avail! Ironically, before I had put the XP-SP2 on my machines, I had absolutely 
"0" problems! I use a LinkSys Wireless Router... The suggestions from LinkSys are 
to lower the RTS/FRAG/BEACON settings of the router - I did that, and still no-go. 

What I finally did was go to "My Network Places/Add a network place" and put in "\\IPADDRESS\SHAREDDRIVE" 
and BINGO IT WORKED! 

IPADDRESS = IP of the Computer you're connecting to (find this by going to "Start\Run\CMD" 
and type in "ipconfig" on the computer you're trying to connect to.

SHAREDDRIVE = The sharing name of the folder you're trying to access.

You can access printers in the same fashion:
"\\IPADDRESS\SHAREDPRINTERNAME"

This most definetely was a convuluted way to get my computers to talk to each other, 
but it works! Now if Uncle Mickey would address the real issue everyone will be happy!






On Friday, January 7, 2005 at 7:06 am, Philip Barnstead wrote:

>*** IMPORTANT *** IMPORTANT *** Also, if the above does not work, simply amend the 

>following regkey from hexadecimal "1" to "0":

>HKLM\SYSTEM\CurrentControlSet\Control\Lsa\restrictanonymous.

>Have fun networking.

>Philip

>

>

> 

[Reply or follow-up to this message]

I also tried all of the tips on this page. The one that worked was adding the machine to the Hosts file, although I found it in "C:\WINDOWS\SYSTEM32\DRIVERS\ETC". I could access the remote machine using the IP address without a problem. Now I can access it by name. I, of course, also had to configure my router so that the IP address of all my machines are static. This problem also started for me when I installed SP-2. I also have Norton Internet Security enabled. I am on a wireless network (although the machine I'm trying to get to is wired, i doubt that matters). I learned a bit going through all this. Thanks guys.


On Sunday, January 23, 2005 at 4:46 pm, Thom MacDonald wrote:
>Well - In total frustration, I have tried each tip I could find on the WEB - All
>to no avail! Ironically, before I had put the XP-SP2 on my machines, I had absolutely
>"0" problems! I use a LinkSys Wireless Router... The suggestions from LinkSys are
>to lower the RTS/FRAG/BEACON settings of the router - I did that, and still no-go.
>
>What I finally did was go to "My Network Places/Add a network place" and put in "\\IPADDRESS\SHAREDDRIVE"
>and BINGO IT WORKED!
>
>IPADDRESS = IP of the Computer you're connecting to (find this by going to "Start\Run\CMD"
>and type in "ipconfig" on the computer you're trying to connect to.
>
>SHAREDDRIVE = The sharing name of the folder you're trying to access.
>
>You can access printers in the same fashion:
>"\\IPADDRESS\SHAREDPRINTERNAME"
>
>This most definetely was a convuluted way to get my computers to talk to each other,
>but it works! Now if Uncle Mickey would address the real issue everyone will be happy!
>
>

[Reply or follow-up to this message]

This worked for me after rebooting the edited PC. My problem was two XP computers a laptop and a desktop. The desktop could get files from the laptop but the laptop was denied access to the desktop. Thanks, :-)


On Friday, January 7, 2005 at 7:06 am, Philip Barnstead wrote:
>*** IMPORTANT *** IMPORTANT *** Also, if the above does not work, simply amend the
>following regkey from hexadecimal "1" to "0":
>HKLM\SYSTEM\CurrentControlSet\Control\Lsa\restrictanonymous.
>Have fun networking.
>Philip
>
>
>

[Reply or follow-up to this message]

The solution for me was to edit the hosts file. The computer which was not accesible is configured with a static IP due to the fact it is set up for remote access. This same machine had no problem seeing and logging into the laptop which could not access the desktop without editing the hosts file. My suspicion is that static IPs somehow mess with name resolution on a Windows network. Can any expert confirm this and explain why? Is there perhaps a setting in the TCP/IP or client for Windows networking which causes this to begin with. It would be great if we could put a finger on why this happens because I find this quirk in Windows networking to be one of the most frustrating things ever!


On Sunday, May 8, 2005 at 5:25 am, Johnintaegu wrote:
>This worked for me after rebooting the edited PC. My problem was two XP computers
>a laptop and a desktop. The desktop could get files from the laptop but the laptop
>was denied access to the desktop. Thanks, :-)
>
>
>

[Reply or follow-up to this message]

Thom and Phillip, Thank you very much for your informative steps!!! TWO YEARS I have been trying to setup a wireless fileshare for my Dad, and with his new Linksys router we were able to do it after 4 hours today. If only I had found this website first we could have had it done quicker. Just some background for others. We have a desktop and a laptop...the desktop was accessing the laptop but not the other way around. Having used the steps described by Thom below (and editing the registry as described further up), we were able to get the laptop accessing the desktop PC. Thank you very much again!!!!! Chris and a happy father, Ian.


On Sunday, January 23, 2005 at 4:46 pm, Thom MacDonald wrote:
>Well - In total frustration, I have tried each tip I could find on the WEB - All
>to no avail! Ironically, before I had put the XP-SP2 on my machines, I had absolutely
>"0" problems! I use a LinkSys Wireless Router... The suggestions from LinkSys are
>to lower the RTS/FRAG/BEACON settings of the router - I did that, and still no-go.
>
>What I finally did was go to "My Network Places/Add a network place" and put in "\\IPADDRESS\SHAREDDRIVE"
>and BINGO IT WORKED!
>
>IPADDRESS = IP of the Computer you're connecting to (find this by going to "Start\Run\CMD"
>and type in "ipconfig" on the computer you're trying to connect to.
>
>SHAREDDRIVE = The sharing name of the folder you're trying to access.
>
>You can access printers in the same fashion:
>"\\IPADDRESS\SHAREDPRINTERNAME"
>
>This most definetely was a convuluted way to get my computers to talk to each other,
>but it works! Now if Uncle Mickey would address the real issue everyone will be happy!
>
>

[Reply or follow-up to this message]

I have gotten as far to being able to see the other computer in the network neighborhood thing. I've tried everything on this thread, and i think that the \\IPADDRESS\SHAREDDRIVE will work but im not sure what to put for the SHAREDDRIVE do i put the complete address of the folder like \C:\ProgramFiles\Documents or just \Documents ? please help me, im also trying to get a laptop to connect to a Desktop but the Desktop cannot connect to the Laptop yet either.

[Reply or follow-up to this message]

I've tried all of these suggestions, and still no dice. I had turned off some services in services.msc, I've re-enabled computer browsing and server, is there anything else? I have a Linksys WRT54G wireless router, desktop PC connected via cable, wirless laptop, both run XP Pro SP2. I'm able to see and access folders and files on the laptop FROM the PC, but not vice-versa. Thanks Microsoft.

[Reply or follow-up to this message]

additionally, on the laptop, using start-run-//ipaddress (ipaddress is the address of my desktop), I get this message: "Windows cannot find '//ipaddress'. Make sure you typed the name correctly, and then try again. This works fine on the desktop, and I can access the shares on the laptop no problem

[Reply or follow-up to this message]

Eureka, everything works now. My roommate had installed some VPN software to connect to his work computer. I uninstalled his VPN connection, AND I started using the Zone Alarm Pro trial, and my network was visible and sharable by all. I think that no matter what my settings were, with Zone Alarm on or off, it was enabling the OS firewall. There was a setting in Zone Alarm Pro that enabled me to turn off the OS Firewall, and now the network is functional. So really it is a combination of all I guess, but thanks to those who've posted on this thread, I've found some great ideas.

[Reply or follow-up to this message]

I have an XP machine and a couple of Win2k machines. One of the Win2k machines' shared disks was inaccessible via the network. Similarly it could not see the other machines' shared disks. I had forgotten the solution then I remembered it when I saw the postings here. Recent version of Norton Antivirus has an "Internet Worm Protection" option. When it is on, the machine is essentially held incommunicado. I have it turned off - Permanently supposedly only it came on again somehow and I had to re-derive the solution... (The "problem machine" is running a current version of NAV and the other Win2k machine is running an older version so IT never has a problem...) Hope this helps someone...

[Reply or follow-up to this message]

did you find a resolution to this issue; i have tried everything I can think of


On Tuesday, November 18, 2003 at 3:59 am, Lee Coda wrote:
>I have a small office network running XP Pro. One pc on the network is intermittently
>available. I periodically get the following error message: "\\PC1 not accessible.
> You might not have permission to use this network resource. Contact the administrator
>of this server to find out if you have access permissions. The network path was
>not found." This pc is set up the same as all others on the network. This on again
>off again behaviour occurs from only one other pc on the network. rebooting the
>client machine usually works, but is a real pain. typing "\\pc1" in the path window
>at the top of explorer will sometimes refresh the connection, but not always. On
>the right side of explorer the pc name for PC1 will show up as "unknown". XP is
>patched to the latest service packs from MS. Any suggestions will be appreciated.
> Thanks
>

[Reply or follow-up to this message]

After all day trying to figure this out, I tried the following and it works!: Install IPX I got this in the following forum http://www.ocforums.com/showthread.php?t=322245


On Sunday, June 4, 2006 at 5:47 pm, Casey Canby wrote:
>did you find a resolution to this issue; i have tried everything I can think of
>
>
>

[Reply or follow-up to this message]

This was exactly the solution to my errors, now I can access all my Shared Doc Folders from any computer on my Network, Thanks for the help


On Monday, December 13, 2004 at 11:53 am, Philip Barnstead wrote:
>Please, all you need to do is double-click on My Computer on the machine that you
>cannot access, right-click on the Shared Documents Folder, click "Sharing & Security",
>untick the "Share this folder on the network" box, go out, and then go back in, re-tick
>it, give the name again i.e. SharedDocs, and this resets the sharing privilege.
>Have fun sharing - Philip
>
>
>

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum