"John John" <audetweld@nbnet.nb.ca> wrote in message
news:%23aWqSTKWIHA.1208@TK2MSFTNGP05.phx.gbl...
> 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
Linear Mode
