Trouble mapping network drive in Windows 7 via Parallels. Discussion in 'Windows. Unfortunately there is one problem that I am encountering in regards to mapping a network drive at my office with Parallels/Windows 7. The Mac sees the network drive and can read and write to it without issue. Windows unfortunately can not, and the office.
I have a macbook pro. Recently I installed parallels desktop on it. But the problem i have is when I connect a usb device to my macbook it is not being detected in the windows parallel desktop. Also I have no idea how to get right click options in the parallel windows desktop. Can you please help me. Thank you for your help in advance.
I have to admit that I was stymied for a long time about how to right-click within Parallels, a great virtualization application available for Mac OS X that lets you run Microsoft Windows XP, Windows Vista, Linux and a variety of other operating systems within Mac OS X. Plug in an external two-button mouse, of course, and the right click just works, but within Parallels?
The secret is to hold down the Control-Shift buttons when you click on the mouse within Parallels. I found that out by actually reading their documentation (imagine!) after puzzling through the problem for far too many hours. Your Control key might well be labeled “Ctrl” on your MacBook Pro, as it is with mine, of course.
The USB device question is straightforward too. In the Preferences for Parallels you can specify whether you want USB devices to be auto-connected upon detection or not. Sounds like you have this option turned off. To change it, you need to shut down your virtual machine, if it’s running, and then choose Edit –> Virtual Machine…, within which you’ll find one of the options is:
On mine you can see that I have my Connection Options set to “Connect to Guest OS”: yours is set to “Connect to Mac OS” instead. A good third alternative, by the way, is to simply choose the option “Ask me what to do”, which means that every time it detects a new USB device, you’ll have the option of letting Parallels have it or let Mac OS X have it.
Finally, if you are running Parallels and you find that your USB devices are being captured by Mac OS X but not your virtual guest OS, you can also go to the Devices menu, find the peripheral in question, and choose it to have Parallels wrest control from Mac OS X and hand it to your guest operating system. If the peripheral is checked, Parallels owns it, and if it’s not checked, the Mac operating system owns it:
As you can see, Parallels has stolen control of my Apple iPhone from the Mac operating system and the Mac side can’t see it. Interestingly, when hooked up this way, the phone doesn’t appear to charge from the USB connection, but when I release it from Parallels (by simply selecting it in this Devices menu) it syncs up with iTunes on my Mac and charges from the USB cable too.
That should get you going a bit more efficiently with Parallels. Enjoy!
Let’s Stay In Touch!
Map To Network Drive
I have a server running Windows 2003 R2 SP2. I can ping it from any computer on the network. My problem is that it acts as a file and print server, but none of the other computers on the network can access these files or printers. I've done some searching and these are the things that have been suggested and the results.
Make sure a firewall isn't blocking anything; There isn't one in place aside from Windows and it is turned off.
Check the DNS; I used nslookup with the IP Address and the server name and I got the same results, so that's not the problem. I also make sure to use the IP Address just to avoid DNS problems.
Telnet into the server from a client; I'm not sure if this worked or not. I used telnet servername 445, as the article suggested. The cmd screen cleared and left me with a flashing cursor. After about a minute I got the normal prompt on the next line. I've never used telnet before so I don't know if it worked or not, but I didn't get an explicit error message.
A general fix I've ran into before is to release the IP Address, flush the DNS, and renew the IP Address. Where I work, this seems to fix a lot of issues, but it didn't fix this one.
I've tried mapping the drives through Windows Explorer and the command prompt, but neither works. In command prompt, I get the error: Multiple connections to a server or shared resource are not allowed. In Windows Explorer, I get the error: The network path servernameshare cannot be found. I've also tried to access the server through the run box. When I do I get the error: servernameshare is not accessible. The network path was not found.
It is also worth mentioning, the server is experiencing a near identical problem. I can ping any computer on the network, but cannot access shares made on those computers from the server. I did this for testing purposes when the issue started, so fixing this direction of connection isn't a priority, but I feel this is relevant to the overall issue. When I try to use the run box to connect to the client's share from the server I get the error: clientnameshare is not accessible. The network is not present or not started. The Windows Explorer and command prompt errors are the same as above.
Any and all help is greatly appreciated. Thanks in advance.
EDIT: Sorry for the single slash. I had typed two, but I guess HTML saw it as one. I had to put three for it to show two. It wouldn't let me add a comment so I just included this edit.
EDIT 2: Sorry, it still won't let me add a comment. It is part of a domain, and I'm sure that credentials aren't the issue. I've tried going in with the local and domain administrator accounts.
EDIT 3: Yes, Scott. I was at the aforementioned server when I made the question, but went back to my office afterwards. I'll see if I can find that registration email. Sorry for the trouble.
3 Answers
My boss finally figured it out. Very simple fix. The Workstation service wasn't running. It was set to automatic, but never started. Everything fixed itself when that started.
I had a Win7 Home edition system that would not see or be seen from other Win7 computers on my network. Each and every system connected through router to Internet with no issues. Pinging IP addresses in either direction worked consistently, BUT pinging COMPUTER-NAME in either direction would NOT work.
Checked WORKGROUP name, DNS, router settings, Windows services. Nothing.
Started looking at less likely reasons I could think of: firewall ports, HOSTS files, LMHOSTS, ARP cache, malware, higher-level stack corruption, errant third-party apps, exorcism of evil spirits...
Driving me nuts! I used to troubleshooting for a living, now I can't get a system (with NO apparent problems) to talk to the rest of my simple network, and vice versa!
NO local system communication beyond pinging IP addresses worked. So, I knew it was likely a Windows issue, more precisely, Windows-specific networking.
I finally found the problem. I had disabled HomeGroup services manually (HomeGroup doesn't work with my young kids' old XP machines, and it is nothing an advanced user would really ever need). BUT, in spite of disabling HomeGroup services, WHEN THE COMPUTER'S ADVANCED NETWORK SETTINGS FOR 'PRIVATE NETWORK' WERE LOOKED AT, 'HOMEGROUP' WAS STILL SELECTED. Deselected it, and everything worked immediately. DOH!
My fault for being too techy and disabling the services directly instead of going through the dialog panel. I suspect an 'ON' flag was still set inside the registry, even though the HomeGroup services were disabled, and this led to the older NETBIOS-type of connection from being allowed.
This parallels the old advice that, IF given a choice, ALWAYS change a registry setting via a Windows dialog panel, instead of directly through the registry. As in this instance, there are often unseen levers interacting with other components that only show up as problems later -- problems that you may not associate with a change you made earlier. (We've all been there, right?)
For those having issues with starting up the Workstation Service as Workstation service could not start for me, do the following... (always make sure to backup your registry before making any changes)
Go to >>>
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServiceslanmanworkstation
On the right there should be a 'DependOnService' & 'DependOnGroup', delete these 2 and reboot.
Problem solved :)
URL for Ref = https://social.technet.microsoft.com/Forums/windowsserver/en-US/722499b5-dc8a-472c-a187-b49dc1a14f07/could-not-start-the-workstation-service-on-local-computer-error-1275?forum=winservergen