If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
XP folder sharing hell......
I have 3 XP Pro PCs. No server. All in same workgroup.
PC1 can see all shared folders on PC2 but cannot access any of them. I always get "PC1\foldername is 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." PC2 can access folders on PC1. PC3 has the same problems with PC2 as PC1. PC2 can access some of the shared folders on PC1. I have tried installing ALL of the available clients, services and protocols for the ethernet adapter on all PCs. I have tried turning off the Windows (and Eset) firewalls. I have tried just about everything I know to share folders on PC2 to no avail. Anybody have any ideas? |
Ads |
#2
|
|||
|
|||
XP folder sharing hell......
"JimTheAverage" wrote in message ... I have 3 XP Pro PCs. No server. All in same workgroup. PC1 can see all shared folders on PC2 but cannot access any of them. I always get "PC1\foldername is 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." PC2 can access folders on PC1. PC3 has the same problems with PC2 as PC1. PC2 can access some of the shared folders on PC1. I have tried installing ALL of the available clients, services and protocols for the ethernet adapter on all PCs. I have tried turning off the Windows (and Eset) firewalls. I have tried just about everything I know to share folders on PC2 to no avail. Anybody have any ideas? Last time I had similar problems, it was due to services being disabled / not running. Go start run services.msc and check for disabled items. I believe it was 'network DDE' that I started and things started working... Worth a try. -Jeepers |
#3
|
|||
|
|||
XP folder sharing hell......
Check to see if the 'Server' service is running.
JS "JimTheAverage" wrote in message ... I have 3 XP Pro PCs. No server. All in same workgroup. PC1 can see all shared folders on PC2 but cannot access any of them. I always get "PC1\foldername is 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." PC2 can access folders on PC1. PC3 has the same problems with PC2 as PC1. PC2 can access some of the shared folders on PC1. I have tried installing ALL of the available clients, services and protocols for the ethernet adapter on all PCs. I have tried turning off the Windows (and Eset) firewalls. I have tried just about everything I know to share folders on PC2 to no avail. Anybody have any ideas? |
#4
|
|||
|
|||
XP folder sharing hell......
It can be a bit fickle doing sharing between XP Pro PC's.
Two things you need to check: 1) Does each PC have its own computer name? -- going into properties and checking computer name on My computer 2) Does each PC have a different user logging in? Or do you have the same login name for each PC? Remember that when connecting to another PC.. it will usually see the user as computername1\username. So if you have the same username on all three PC's you could be having trouble merely because of that. Try creating three seperate username logins.. and see if that gives you different results. |
#5
|
|||
|
|||
XP folder sharing hell......
"Jeepers Creepers" wrote in message ... "JimTheAverage" wrote in message ... I have 3 XP Pro PCs. No server. All in same workgroup. PC1 can see all shared folders on PC2 but cannot access any of them. I always get "PC1\foldername is 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." PC2 can access folders on PC1. PC3 has the same problems with PC2 as PC1. PC2 can access some of the shared folders on PC1. I have tried installing ALL of the available clients, services and protocols for the ethernet adapter on all PCs. I have tried turning off the Windows (and Eset) firewalls. I have tried just about everything I know to share folders on PC2 to no avail. Anybody have any ideas? Last time I had similar problems, it was due to services being disabled / not running. Go start run services.msc and check for disabled items. I believe it was 'network DDE' that I started and things started working... Worth a try. Thanks for the suggestion. I tried it ...but no luck. jim |
#6
|
|||
|
|||
XP folder sharing hell......
"Cirga" wrote in message ... It can be a bit fickle doing sharing between XP Pro PC's. Two things you need to check: 1) Does each PC have its own computer name? -- going into properties and checking computer name on My computer Yes - different PC names. 2) Does each PC have a different user logging in? Or do you have the same login name for each PC? Remember that when connecting to another PC.. it will usually see the user as computername1\username. So if you have the same username on all three PC's you could be having trouble merely because of that. Try creating three seperate username logins.. and see if that gives you different results. Yes. All 3 are using different user login names. Now I am getting a message that says...."\\pcname\foldername is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out of you have access permission. -- Not enough server storage is available to process this command. Looking up that last part took me to posts that say to increase the IRPStackSize in the registry - but it is already at 50 (the maximum setting for XP - or so I have read). I even removed simple file sharing on the stingy PC and re-shared the folder with everyone having all permission - still no luck. The odd thing is that the stingy PC has shared its printers without a hitch. jim |
#7
|
|||
|
|||
XP folder sharing hell......
"John Holmes" wrote in message . nl... JS "contributed" in 24hoursupport.helpdesk: "JimTheAverage" wrote in message news:74d6fbee-1e17-4ebb-8b1e-2e3c19334f27 @s13g2000prd.googlegroups.com... I have 3 XP Pro PCs. No server. All in same workgroup. PC1 can see all shared folders on PC2 but cannot access any of them. I always get "PC1\foldername is 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." PC2 can access folders on PC1. PC3 has the same problems with PC2 as PC1. PC2 can access some of the shared folders on PC1. I have tried installing ALL of the available clients, services and protocols for the ethernet adapter on all PCs. I have tried turning off the Windows (and Eset) firewalls. I have tried just about everything I know to share folders on PC2 to no avail. Anybody have any ideas? top-poasting corrected Check to see if the 'Server' service is running. JS Yet another clueless fool responds. why? already came up with the correct answer. Shows how much you know....none of the answers thus far have solved the problem. jim |
#8
|
|||
|
|||
XP folder sharing hell......
JimTheAverage wrote:
I have 3 XP Pro PCs. No server. All in same workgroup. PC1 can see all shared folders on PC2 but cannot access any of them. I always get "PC1\foldername is 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." PC2 can access folders on PC1. PC3 has the same problems with PC2 as PC1. PC2 can access some of the shared folders on PC1. I have tried installing ALL of the available clients, services and protocols for the ethernet adapter on all PCs. I have tried turning off the Windows (and Eset) firewalls. I have tried just about everything I know to share folders on PC2 to no avail. Anybody have any ideas? 1- For starters *don't* use 2 firewalls! It will not provide you with additional security and it will or may cause nothing but trouble when you try to setup your network. Decide which firewall you prefer to use and use one firewall only. 2- While you setup and troubleshoot your network completely disable the firewall, at least until you get things sorted out. You can re enable the firewall after you fix your network, keep this extra avenue of trouble out of the picture until you get the network setup properly, you can enable it after you're done. For security reasons, while the firewall is disabled you may want to disconnect the cable to the internet or other outside networks. 3- Make sure that there are no duplicate computer names on the network. Make sure that the machines are all in the same workgroup. 4- For most networks you usually only need one common transport protocol and one network client. Additional transport protocols or clients only bring in extra complications into your network configuration. Additional unneeded transport protocols may result in network collisions and slow down your network. Remove all protocols except for the TCP/IP protocol, in modern networks that is usually the only protocol needed. Remove all network clients except for the Client for Microsoft Networks. 5- Install/enable File and Printer Sharing. 6- Windows XP Pro machines will not allow access to their resources without proper user credentials and authentication. The unsafe method of getting around that is to enable the Guest account. A safer method is to create users with identical names and identical passwords on the machines that you want to share resources. 7- If you have done all of the above and are still getting access denied messages verify the NTFS permissions on the shares. John |
#9
|
|||
|
|||
XP folder sharing hell......
JimTheAverage wrote:
I have 3 XP Pro PCs. No server. All in same workgroup. PC1 can see all shared folders on PC2 but cannot access any of them. I always get "PC1\foldername is 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." PC2 can access folders on PC1. PC3 has the same problems with PC2 as PC1. PC2 can access some of the shared folders on PC1. I have tried installing ALL of the available clients, services and protocols for the ethernet adapter on all PCs. I have tried turning off the Windows (and Eset) firewalls. I have tried just about everything I know to share folders on PC2 to no avail. Anybody have any ideas? On each WinXP PC, create local user account(s), with non-blank password(s), that have the desired access privileges to the desired shares. Log on to the other PCs using those account(s), and you will be able to access the designated shares, provided your network is configured properly. Also, make sure that WinXP's built-in firewall is disabled on the internal LAN connection. Usually, WinXP's Networking Wizard makes it simple and painless -- almost entirely automatic, in fact. There's a lot of useful, easy-to-follow information in WinXP's Help & Support files, and he Home Networking http://www.microsoft.com/windowsxp/h...et/default.asp Networking Information http://www.onecomputerguy.com/networking.htm PracticallyNetworked Home http://www.practicallynetworked.com/index.htm Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm -- Bruce Chambers Help us help you: http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/default.aspx/kb/555375 They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. ~Benjamin Franklin Many people would rather die than think; in fact, most do. ~Bertrand Russell The philosopher has never killed any priests, whereas the priest has killed a great many philosophers. ~ Denis Diderot |
#10
|
|||
|
|||
XP folder sharing hell......
"Jeepers Creepers" wrote in message ... "JimTheAverage" wrote in message ... I have 3 XP Pro PCs. No server. All in same workgroup. PC1 can see all shared folders on PC2 but cannot access any of them. I always get "PC1\foldername is 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." PC2 can access folders on PC1. PC3 has the same problems with PC2 as PC1. PC2 can access some of the shared folders on PC1. I have tried installing ALL of the available clients, services and protocols for the ethernet adapter on all PCs. I have tried turning off the Windows (and Eset) firewalls. I have tried just about everything I know to share folders on PC2 to no avail. Anybody have any ideas? Last time I had similar problems, it was due to services being disabled / not running. Go start run services.msc and check for disabled items. I believe it was 'network DDE' that I started and things started working... Worth a try. -Jeepers Just an update.....I found the culprit. I don't know why or how it created this nightmare yet - but I have fired off a note to the publishers to try and get an answer. The application that completely screwed my networking up was Eset's NOD32 Antivirus and Smart Security Suite. Once removed from all PCs, the network works like a charm. This is not the first bad run-in I've had with Eset's NOD32 and Smart Security. On several occassions I have seen Eset's software break applications by blocking them from running with absolutely NO warning or indication that it had done anything at all. On other occassions I have seen NOD32 toss up red threat screens to customers only to see that there was no "clean" or "quarantine" buttons at all and nothing on the blaring red threat screen said that NOD32 knew what to do or was going to take any action at all. All you could do was close the threat screen and wonder if you were protected. It's sad really. NOD32 used to do one thing - kill viruses - and it did it well. With all of the crap they are cramming into NOD32, they have created a monster of a headache to deal with. And, no documentation of any consequence comes with the product. When an application blocks something or cleans something or quarantines something, wouldn't it be great of it told you what it did? Eset's applications don't. they keep you guessing and wasting valuable time and resources trying to find problems that appear to be network or application related - NOT security related. Now, whenever I see ANY problem on a PC with Eset's products installed, my first course of action will be to uninstall Eset's software before I change a single setting. Thanks for all of the suggestions and watch yourself arounf Eset's NOD32 and "Smart Security". jim |
#11
|
|||
|
|||
XP folder sharing hell......
"John John" wrote in message ... JimTheAverage wrote: I have 3 XP Pro PCs. No server. All in same workgroup. PC1 can see all shared folders on PC2 but cannot access any of them. I always get "PC1\foldername is 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." PC2 can access folders on PC1. PC3 has the same problems with PC2 as PC1. PC2 can access some of the shared folders on PC1. I have tried installing ALL of the available clients, services and protocols for the ethernet adapter on all PCs. I have tried turning off the Windows (and Eset) firewalls. I have tried just about everything I know to share folders on PC2 to no avail. Anybody have any ideas? 1- For starters *don't* use 2 firewalls! It will not provide you with additional security and it will or may cause nothing but trouble when you try to setup your network. Decide which firewall you prefer to use and use one firewall only. 2- While you setup and troubleshoot your network completely disable the firewall, at least until you get things sorted out. You can re enable the firewall after you fix your network, keep this extra avenue of trouble out of the picture until you get the network setup properly, you can enable it after you're done. For security reasons, while the firewall is disabled you may want to disconnect the cable to the internet or other outside networks. 3- Make sure that there are no duplicate computer names on the network. Make sure that the machines are all in the same workgroup. 4- For most networks you usually only need one common transport protocol and one network client. Additional transport protocols or clients only bring in extra complications into your network configuration. Additional unneeded transport protocols may result in network collisions and slow down your network. Remove all protocols except for the TCP/IP protocol, in modern networks that is usually the only protocol needed. Remove all network clients except for the Client for Microsoft Networks. 5- Install/enable File and Printer Sharing. 6- Windows XP Pro machines will not allow access to their resources without proper user credentials and authentication. The unsafe method of getting around that is to enable the Guest account. A safer method is to create users with identical names and identical passwords on the machines that you want to share resources. 7- If you have done all of the above and are still getting access denied messages verify the NTFS permissions on the shares. John Just an update.....I found the culprit. I don't know why or how it created this nightmare yet - but I have fired off a note to the publishers to try and get an answer. The application that completely screwed my networking up was Eset's NOD32 Antivirus and Smart Security Suite. Once removed from all PCs, the network works like a charm. This is not the first bad run-in I've had with Eset's NOD32 and Smart Security. On several occassions I have seen Eset's software break applications by blocking them from running with absolutely NO warning or indication that it had done anything at all. On other occassions I have seen NOD32 toss up red threat screens to customers only to see that there was no "clean" or "quarantine" buttons at all and nothing on the blaring red threat screen said that NOD32 knew what to do or was going to take any action at all. All you could do was close the threat screen and wonder if you were protected. It's sad really. NOD32 used to do one thing - kill viruses - and it did it well. With all of the crap they are cramming into NOD32, they have created a monster of a headache to deal with. And, no documentation of any consequence comes with the product. When an application blocks something or cleans something or quarantines something, wouldn't it be great of it told you what it did? Eset's applications don't. They keep you guessing and wasting valuable time and resources trying to find problems that appear to be network or application related - NOT security related. Now, whenever I see ANY problem on a PC with Eset's products installed, my first course of action will be to uninstall Eset's software before I change a single setting. Thanks for all of the suggestions and watch yourself around Eset's NOD32 and "Smart Security". jim |
#12
|
|||
|
|||
XP folder sharing hell......
"Bruce Chambers" wrote in message ... JimTheAverage wrote: I have 3 XP Pro PCs. No server. All in same workgroup. PC1 can see all shared folders on PC2 but cannot access any of them. I always get "PC1\foldername is 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." PC2 can access folders on PC1. PC3 has the same problems with PC2 as PC1. PC2 can access some of the shared folders on PC1. I have tried installing ALL of the available clients, services and protocols for the ethernet adapter on all PCs. I have tried turning off the Windows (and Eset) firewalls. I have tried just about everything I know to share folders on PC2 to no avail. Anybody have any ideas? On each WinXP PC, create local user account(s), with non-blank password(s), that have the desired access privileges to the desired shares. Log on to the other PCs using those account(s), and you will be able to access the designated shares, provided your network is configured properly. Also, make sure that WinXP's built-in firewall is disabled on the internal LAN connection. Usually, WinXP's Networking Wizard makes it simple and painless -- almost entirely automatic, in fact. There's a lot of useful, easy-to-follow information in WinXP's Help & Support files, and he Home Networking http://www.microsoft.com/windowsxp/h...et/default.asp Networking Information http://www.onecomputerguy.com/networking.htm PracticallyNetworked Home http://www.practicallynetworked.com/index.htm Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm -- Bruce Chambers Help us help you: http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/default.aspx/kb/555375 They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. ~Benjamin Franklin Many people would rather die than think; in fact, most do. ~Bertrand Russell The philosopher has never killed any priests, whereas the priest has killed a great many philosophers. ~ Denis Diderot Just an update.....I found the culprit. I don't know why or how it created this nightmare yet - but I have fired off a note to the publishers to try and get an answer. The application that completely screwed my networking up was Eset's NOD32 Antivirus and Smart Security Suite. Once removed from all PCs, the network works like a charm. This is not the first bad run-in I've had with Eset's NOD32 and Smart Security. On several occassions I have seen Eset's software break applications by blocking them from running with absolutely NO warning or indication that it had done anything at all. On other occassions I have seen NOD32 toss up red threat screens to customers only to see that there was no "clean" or "quarantine" buttons at all and nothing on the blaring red threat screen said that NOD32 knew what to do or was going to take any action at all. All you could do was close the threat screen and wonder if you were protected. It's sad really. NOD32 used to do one thing - kill viruses - and it did it well. With all of the crap they are cramming into NOD32, they have created a monster of a headache to deal with. And, no documentation of any consequence comes with the product. When an application blocks something or cleans something or quarantines something, wouldn't it be great of it told you what it did? Eset's applications don't. They keep you guessing and wasting valuable time and resources trying to find problems that appear to be network or application related - NOT security related. Now, whenever I see ANY problem on a PC with Eset's products installed, my first course of action will be to uninstall Eset's software before I change a single setting. Thanks for all of the suggestions and watch yourself around Eset's NOD32 and "Smart Security". jim |
#13
|
|||
|
|||
XP folder sharing hell......
jim wrote:
Just an update.....I found the culprit. I don't know why or how it created this nightmare yet - but I have fired off a note to the publishers to try and get an answer. The application that completely screwed my networking up was Eset's NOD32 Antivirus and Smart Security Suite. Once removed from all PCs, the network works like a charm. Thanks for letting us know how you fixed it, follow up replies with the solutions that worked help others when they search for help with the same problems. John |
#14
|
|||
|
|||
XP folder sharing hell......
"jim" wrote:
On other occassions I have seen NOD32 toss up red threat screens to customers only to see that there was no "clean" or "quarantine" buttons at all and nothing on the blaring red threat screen said that NOD32 knew what to do or was going to take any action at all. One time I was given a choice to suspend NOD32 for 10 minutes ( along with clean and quarantine); that's handy if you actually wish to download a virus or check one out. I don't get that option anymore. Other than that, I haven't had a problem with NOD32 at all, never tried the security suite. -- Deadlock http://img209.imageshack.us/img209/5...farialibh3.jpg |
#15
|
|||
|
|||
XP folder sharing hell......
"John John" wrote in message ... jim wrote: Just an update.....I found the culprit. I don't know why or how it created this nightmare yet - but I have fired off a note to the publishers to try and get an answer. The application that completely screwed my networking up was Eset's NOD32 Antivirus and Smart Security Suite. Once removed from all PCs, the network works like a charm. Thanks for letting us know how you fixed it, follow up replies with the solutions that worked help others when they search for help with the same problems. To test out my theory fully, I re-installed only the NOD32 antivirus, version 2.7, (not the Smart Security suite) on 2 of the PCs. I then ran the NOD32 updates. Again, I could not get to PC2's shared folders from PC1 - this with absolutely NO change on PC2 other than installing version 2.7 of NOD32 antivirus. And, I could not get to a folder shared from my My Documents folder on PC1 - even though Share Permissions shows that Everyone has permission to Change or Read items in the folder. The folders on PC2 are shared from a 2nd hard drive and are not a part of any system or special use folders (like My Documents). I even disabled simple file sharing and gave Everyone Full Control under both Sharing and Security for several folders on PC2 and I still could not access the folders from PC1. Absolutely incredible! Well, I guess you won't be spreading any viruses on a network that you can't browse, will you? If they work with me to actually fix these issues (whether through training me or fixing what I percieve as a seriously flawed product) I will post the solutions here. I am uninstalling NOD32 completely and putting on a trial version of AVG until I figure this out. Thanks again to all who posted. jim |
Thread Tools | |
Display Modes | |
|
|