So - I have a Win XP laptop that I use on a home wireless and work lan. Of late (the past week or so) for no apparent reasons - I've been having mucho file and printer sharing issues. It's seeing the web fine - but when I try and print to a network printer, or access files I get the "you do not have permission to use the network resource" error
The server is fine (in both situations) and I'm sure it's a laptop issue
Any good ideas please?
Ben Kepes Diversity Limited
E firstname.lastname@example.org P +64 3 3146006 M 021 2384136 skype ben_kepes blog diversity.net.nz
Make sure you have the same username and password in both machines - it makes all much easier. Also, check the Security tab in the properties for those resources (printer, folder) to make sure all users have appropriate access.
If you can double check that the problem is not with the network access or print/file sharing servers (Can check it with other machines on the network). Then your laptop windows need to be refreshed. I hat this part but it happened with me in the past and after surfing the internet & other resources with zero sucess I had to refresh my PC windows. Which worked.
If you're getting a permissions error then I can reasonably safely assume the network is networking otherwise you'd be getting a "not available" error of sorts
Simple file sharing enabled on either of the machines? Guest account disabled? NTFS security permissions ok? Have you tried mapping a shared drive directly via IP at all?
I'm wondering if it's a problem with authentication, I've encoutered it before where even though the client is told to logon to the share as a valid user it actually logs on as guest, who... well has no rights at all.
Also on that mapping a shared drive note, you should be able to map the drive and on the server's computer management - shares page and see who is accessing the share. i.e. joebloggs or guest, regardless of whether or not they're actually able to see the share contents. I've found that handy when the share permissions are fine but the NTFS permissions are borked :)