I have a windows XP mode environment set up on my laptop that I use occasionally for running an old development environment that doesn't run directly in Windows 7. When I first set it up a few years ago, I used the integration features drive mappings to map direct access to one of the local host drives (my data drive where the actual source code is stored). The drive would show up in the virtual machine as \\tsclient\d.Furthermore, I could also see my entire network within the virtual machine.
I last used the environment a few months ago. Today when I fired up windows XP mode it would no longer allow me to access \\tsclient. Last week I upgraded Norton 360 to a new version, so I suspect somehow Norton 360 is now blocking it.
I was able to work around the problem by chaging the virtual machines networking adapter settings from shared networking (NAT) to instead use the physical adapter (which unfortunately makes the \\tsclient mapped drives unavailable) and instead mapping the drive over the network. Unfortunately this appears to make the performance for accessing the local host drive a lot worse than it was before.
Is there something I can set in Norton 360 to make this work the old way again?
Product version info:
Norton 360
20.2.0.19
Windows 7 Professional
7601.17944.amd64fre.win7sp1_gdr.120830-0333
Norton Autofix Results: 0 item(s)