Deadman
asked on
\\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
"\\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.
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.
ASKER
no, entire network in wireless and have some other systems in XP SP3 client. This system is newly added in our network.
Can you ping server from the client?
ASKER
i'm able to cross ping both systems with IP address, but not able to ping with name of computer.
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.
There is some difference (in the TCP/IP settings) between the working clients and the problematic XP client.
ASKER
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
BTW, which is server's IP address?
ASKER
my server ip address is 192.168.1.52 and XP SP3 Client IP is 192.168.1.97
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/Syste m Logs show any Warnings/Errors that might help?
Does the 7's Windows Application/Security/Syste
ASKER
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.
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.
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/Syste m)?
The XP client doesn't show anything useful in it's Logs (again, Application/Security/Syste
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
its worked for me
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
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
Is this the only XP SP3 client?