Member Avatar for rudi.anto

Dear All,

Guys, nice to join this forum,

I've a problem that making confuse, my office have 125 client pc with os xp and one server with windows 200 server, each pc installed syamantec antivirus.

I want to access a folder in one client pc (PC A) from other client (PC B) but had got this error message, but if i try to access it from other client (PC C) is not problem

"\\NT001 is no accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission.

Insufficient system resourcers exist to complete the requested service"

i tried to uninstall symantec antivirus from PC B this problem is solve but when i installed it again i've got the message again.

who knows about this problem please help me??:happy:

Thanx N BRgrds

Rudianto

  • 2 Contributors
  • 3 Replies
  • 215 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by rudi.anto

Dani AI

Generated

The fact that uninstalling Symantec on the problem PC restores access while the same share is reachable from another client points to an endpoint/AV control on PC B blocking SMB-style file sharing. 's suggestion to check the Windows anonymous-restriction flag was useful and confirmed that flag was already set to allow access, so the next investigation should focus on Symantec and the client-side network stack.

Troubleshooting checklist (in order):

  • Verify basic connectivity by IP (ping <PC-A-IP>) and attempt the share by IP instead of name; success by IP isolates name resolution from SMB blocking.
  • Compare the working client and failing client for Symantec build/patch level, LiveUpdate date, local firewall settings, and Windows Service Pack/patch level — differences usually expose the culprit.
  • Inspect logs: Windows Event Viewer (System/Application) and Symantec logs for entries that coincide with the failed access attempt (look for blocked/queried network activity).
  • Short test: briefly disable only Symantec's network/firewall protection (or boot Safe Mode with Networking) and retest access. Do not leave protection disabled; treat this as a diagnostic step only.
  • Basic local checks: confirm the Workstation service is running and use netstat -an to see whether outbound SMB ports are being blocked.

Remediation guidance:

  • If the Symantec network module is identified as the blocker, create targeted allow rules for SMB (TCP 139/445), add the peer(s) or local subnet to the product's trusted list, or exclude SMB traffic from deep inspection. Update the Symantec client to the latest build/definitions or apply vendor hotfixes that address SMB/DFS interference.

For escalation, capture Symantec product/version, exact Windows build/Service Pack, timestamps, and the relevant Event Viewer and Symantec log entries before contacting vendor support. The combination of the registry check that suggested and the uninstall/reinstall symptom narrows the problem to endpoint controls rather than server-side sharing configuration.

Recommended Answers

All 3 Replies

Member Avatar for zeroth

Here's something to try on the machine putting out the error. Regedit HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa

There's an entry here named restrictanonymous - each time I've had a problem with an XP machine losing connection with the network, I've found this key set as value 1. It should be set at 0 (zero). When I've set it back, it instantly restores communication.

Worth trying. I have come to believe this key is set to 1 by software like Norton's when it wants to restrict access...

Member Avatar for rudi.anto

Appreciate for your respond, i will try it.

Tnx N BRgrs

Rudianto

Member Avatar for rudi.anto

I was try it but i saw that restrictanonymous has been 0 on my computer.

wuih...........................

Thx Fo your respond but any suggestion please?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.