Win7 stopped seeing network shares on XP computer

ssvarc
ssvarc used Ask the Experts™
on
A client's Win7 laptop (A), connected wirelessly via a router, stopped, around two weeks ago, to see network shares on a XP computer (B). It still accesses the internet, gets emails, etc, so we know that it is on the network correctly. See below (summary) for further proof of its connectivity.

As part of troubleshooting, I hooked up my Win7 laptop (C) wirelessly to the network. My laptop, C, does access the shares on A. B accesses the C laptop as well.

Summary: (All computers have network shares.) B and C can ping each other. B can access shares on C. B can't ping A or access shares on A.
C can ping B. Can't access shares on B but can see the media sharing of B. C cannot ping A but it can access shares on A.

I have checked the settings on B, to make sure file sharing is on, make sure it is on a Work network, the encryption setting, etc.

What are the troubleshooting steps to take?

Thanks!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Author

Commented:
I'm going to be away for the weekend but will check back early next week, so if no response to an answer please realize that is temporary and I will be checking back.

Thanks!
Commented:
What meesage do you get?
can you get to the shares by ip address vs name?
Make sure password protected file sharing is disabled on computer A.  Also -- try to connect laptop A directly via wired connection and see if you get any different results.

Please give us IP information on all three computers.
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
linraf:

Yes, IP address does get to the shares. I'm not 100% sure, but this is a change from previously, where even the IP didn't help. As well, rereading my summary, I see that I confused several things. Will rework it if necessary, but for now will attempt shares via IP and report back.

Author

Commented:
My above summary was innaccurate. Please don't consult when reading this update.

I was able to map one network share from the XP desktop to the Win7 laptop, using the IP address. There is more then one share and when attempting to map another one I got an error message that it is already mapped. There is no map by Computer (which *does* show the successful one based on IP, which still works), and net use by the command prompt doesn't show anything besides for the successful IP map.

I've enclosed both screenshots.

What are my options? What am I looking for here, some obscure setting?

Thanks! The error message The results of a net use command
Commented:
Sound like a permissions issue.
Commented:
Check your permissions and check for any saved usernames and names.

To check for saved passwords:
start
run
type control userpasswords2
press enter
go to the 2 nd and click manage passwords
look for saved and remove

Author

Commented:
linraf:

Permissions: How do I check for and resolve any permissions issues?

Passwords: I do have saved passwords, but their there for the share setup with IP.

Thoughts?
Commented:
So, it sounds like the username/pw that you have saved does not have permissisions to the ups share on the .107 machine.

On the .107 machine find the ups folder that is shared in Windows Explorer.
rt click on it
properties
security tab
check the users permissions
sharing tab
permission button
check the user's permissions

Author

Commented:
linraf:

I'll try to sum up (correctly this time) the setup and then answer the last couple of items.

There is a WinXP desktop (A) and a Win7 laptop (B). A has three folders being shared, they all have a user called Everyone with Full Control in addition to th eregualr user accounts with Full Control. B used to have maps to the shares from A, until about a month ago when they stopped working.

I brought my Win7 laptop (C) and it saw the shares from A. So they are still around and available. It seems the issue is on the B laptop.

I was able to map one of the A shares to B, using IP addresses. However, the second share is erroring out when it gets to the part about credentials with the above referenced error (shown above with screenshots). I've confirmed that the permissions on the share are correct, and that the user and credentials that was sucessfully used for the first map have valid permissions (Full Control) on this share as well. There is an Everyone with Full Control as well. It is still giving this error (shown above with screen shots).

How do I resolve this and map the shares?

Thanks!
Commented:
Just to confirm, you check the permissions on the security tab and on the share tab?
These are 2 different sets of permissions.

Commented:
When you connect using your test laptop, are you using the same credentials as laptop B?

Author

Commented:
linraf:

Only one of those (I'm pretty sure [but we know what assumptions spell]) it was the security tab.

At this point, I'm using LogMeIn to see the client's computers.

To sum up, check both tab's to see if the user account being used on the map is there on share. OK, will do. Anything else to check for at this point?

Thanks!
This is a ballbuster, I'll be interested to know what fixes it.

Commented:
My other suggestion is removing the saved credentials that we talked about before, then rebooting and accessing the non working share first.  


It should prompt for credentials at this point. Try the crecentials of an administrator of machine A for testing purposes, but do not click to remember password.

Author

Commented:
linraf:

Will do, but it will be about twenty four hours before I can get do it and report back.
A stab in the dark here but I would also try uninstalling File and Print Services for Microsoft Networks and reinstalling it.
Qlemo"Batchelor", Developer and EE Topic Advisor
Top Expert 2015

Commented:
I've requested that this question be deleted for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Author

Commented:
I'm accepting Linraf's answer as accurate and helped to resolve the issue.

Author

Commented:
linraf:

Thanks! A couple days after your last post the HD on the client laptop died. New HD, diagnostics tests, install Windows, programs, setup all the esoterica... Then, the same issues with the shares. So, following the posts, the issues was resolved with IP mapped shares, which had permissions added on both the Share and Security tabs for the user account (whereas before, using Everyone for the permissions, worked without issues).

So that explains the delay (I hope...).

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial