Unable to map drive windows xp

A subscription to help make the most of your time. For up to 6 people. Premium apps. Try 1 month free. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions.

Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. After mapping a shared drive on an XP machine with firewall turned off from my Windows 10 machine, I notice the following issues:.

Is there any thing that could be done to address this issue. Is there a way to map the drive with the XP firewall turned on. The firewall is turned on, on the Windows 10 machine. I have turned on network discovery and file and printer sharing on my Windows 10 machine. Attachments: Up to 10 attachments including images can be used with a maximum of 3. ArunSrinivasa Hi,.

Can you please verify which method you used to map drive on win10? By GPO or right click the sharing folder? Help please!!! I may be wrong, but at one thine MS was telling people not to map the actual drive.

Instead, you make a folder on the drive to share. The XP machine then can map the folder as a virtual drive. Also, many new programs do not need a network resource mapped to a drive.

Are you using programs that require a network share to present itself as a virtual local drive? The point I am trying to make is that there maybe an acceptable workaround. Or, in your case, maybe the workaround will not do the job. Drive mapping problems are a common complaint in windows networking.

Hey Geek, thanks for responding. Indeed, this appears to be a significant issue. Yes, I am aware that mapping the root of drives is not always recommended from a security perspective, but I am on a fairly secure internal network - I am the only one in the house. This is really a pain. I don't have any apps that need to run across my network from XP calling to Win7 - I just want my XP netbook to be able to fully access both C: and D: drives without having to go to the trouble to map specific folders into a Public Win7 share.

Is this so much to ask? Also, theoretically, this type of workaround would mean that every time I created a new folder under Win7 that I want my XP boxes to use, I have to remember to drag that new folder into the Public share? I am discovering that under Win7, the roots of drives are protected.

If people need that, awesome. I don't. It should be a clearly explained option and I should also be able to fully disable that type of security if I choose to. This is a major hassle. Like I said, I understand I can drag folders into the public Win7 share [which does seem to work though I need to test more] but this is so annoying and I guess not so much the point.

Homegroup apparently will only work between Win7 machines.