Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

\\server is not accessible. You might not have permission to this network resource. Contact the administrator of this server to find out if you have access permissions. The specified server cannot per

Posted on 2013-06-04
14
Medium Priority
?
34,578 Views
Last Modified: 2014-09-18
"\\server is not accessible. You might not have permission to this network resource. Contact the administrator of this server to find out if you have access permissions. The specified server cannot perform the requested operation".

Getting his error message from only one particular system in wireless. This system have windows XP SP3. And connecting server is Windows 7. In my network every system able to access with any trouble. I have reinstalled OS also in XP system. All system are in same workgroup. Please suggest solution for this issue.
0
Comment
Question by:Deadman
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 6
14 Comments
 
LVL 20

Expert Comment

by:strivoli
ID: 39221141
Is this the only wireless client?
Is this the only XP SP3 client?
0
 
LVL 7

Author Comment

by:Deadman
ID: 39221162
no, entire network in wireless and have some other systems in XP SP3 client. This system is newly added in our network.
0
 
LVL 20

Expert Comment

by:strivoli
ID: 39221166
Can you ping server from the client?
0
Looking for the Wi-Fi vendor that's right for you?

We know how difficult it can be to evaluate Wi-Fi vendors, so we created this helpful Wi-Fi Buyer's Guide to help you find the Wi-Fi vendor that's right for your business! Download the guide and get started on our checklist today!

 
LVL 7

Author Comment

by:Deadman
ID: 39221170
i'm able to cross ping both systems with IP address, but not able to ping with name of computer.
0
 
LVL 20

Expert Comment

by:strivoli
ID: 39221177
Lets say server's IP is 192.168.1.10. You cannot ping server but you can ping 192.168.1.10, both from the XP client. You cannot run \\server. What happens if you run \\192.168.1.10?
There is some difference (in the TCP/IP settings) between the working clients and the problematic XP client.
0
 
LVL 7

Author Comment

by:Deadman
ID: 39221190
when run with \\192.168.1.10 getting same error. ya i have configured same setting between the working clients and the problematic XP client. still gives trouble
0
 
LVL 20

Expert Comment

by:strivoli
ID: 39221193
BTW, which is server's IP address?
0
 
LVL 7

Author Comment

by:Deadman
ID: 39221209
my server ip address is 192.168.1.52 and XP SP3 Client IP is 192.168.1.97
0
 
LVL 20

Expert Comment

by:strivoli
ID: 39221218
OK. So just to be sure: you tried to run \\192.168.1.52 from the XP client, right?
Does the 7's Windows Application/Security/System Logs show any Warnings/Errors that might help?
0
 
LVL 7

Author Comment

by:Deadman
ID: 39221746
ya i have tried to run \\192.168.1.52 from the XP client getting same error.
In windows 7 System Logs shows in one particular error message.

"The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations."

Event ID is 2017.
0
 
LVL 20

Expert Comment

by:strivoli
ID: 39224658
I don't think the error you reported is related to your issue.
The XP client doesn't show anything useful in it's Logs (again, Application/Security/System)?
0
 
LVL 7

Accepted Solution

by:
Deadman earned 0 total points
ID: 39227985
thanks  strivoli for suggestion of 7's Windows Application/Security/System Logs.

"The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations."

i have resolved above issue making changes in registry.

Set the following registry key to ‘1':

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

and set the following registry key to ‘3':

HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size
0
 
LVL 7

Author Closing Comment

by:Deadman
ID: 39237164
its worked for me
0
 

Expert Comment

by:Lourens van Dyk
ID: 40329807
The registry changes definitely worked for me.

Made the changes and then restarted the Windows 7 connecting server and WinXP client.

Is there maybe a link that explains the registry keys and why they would be affected after some time?

Thank you for the solution  2gainknowledge and strivoli
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How does someone stay on the right and legal side of the hacking world?
What monsters are hiding in your child's room? In this article I will share with you a tech horror story that could happen to anyone, along with some tips on how you can prevent it from happening to you.
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question