Having a weird issue. I'm new to Macs and have a windows VM that I'm running on a new macbook pro via VM Fusion. I setup a file share on the windows side (Win 7) and accessed it from the Mac side using the "Connect to Server" dialog. I did it successfully several times, even adding in a symlink on the mac side and starting a git repository. About halfway through my first pull from my git server the pull froze (i.e. didn't continue pulling). I waited for quite a while like that before killing the terminal window, and after that I was no longer able to connect to the share in any fashion. I've tried removing the share on both sides, rebooting both sides, but ever since then trying to connect back to that VM gives me an error that "There was an error connecting tot he server {ip address}. Check the server name or IP Address, and then try again"
IP is right, I've tried it with the name as well (which is how I did it originally) which was also right; I can ping from the mac side to the windows side both the IP and name. I have tried editing /etc/hosts to point a name at the IP address that way, same result. I've tried turning off the windows firewall and antivirus, no difference.
I guess I'd assume it was me not doing something right on the shares, except that it went from working to not working w/o me changing any settings. It's a new box, so it's possible that there was an OS patch (on either side) that caused the change, but I didn't notice any going in during the time in question.
UPDATE: I pulled another new mac patch down (I guess I didn't have them all) and it worked again. Right up until I froze it again with the git issue (I had tried to resolve the pack size issue that appeared to be the root cause of the git problem, I was wrong).
Is there any process I should look at killing and restarting? This behavior seems like there's a hung process somewhere, though shutting the mac down and booting it up again isn't helping, so I don't know.
Figured it out. Turns out that turning off sharing on the windows sid,e then turning it back on solved it.
Related
I downloaded the latest version of Appium from the GitHub. I have installed it on two Windows PCs,
On first one it works fine.
But on the second one, just by clicking "Start server v1.7.2" a window appear showing "The server is stopped".
What is wrong with the configuration?
I found the solution for above error.
It was due to firewall modified by an antivirus, it disables all open ports on this PC.
There can be around three solutions:
Format the PC will help us to get open ports, but it is not a recommended solution.
Uninstalling Antivirus can open blocked ports, by recovering firewall to its original state.
If the 2nd solution does not help then Uninstalling Antivirus and create a new User Account on PC, helps me to run Server successfully.
I am trying to setup tightvnc on my Raspberry Pi 2 (rp2), so I can remote in from my mac. I have done this before and it went smooth as butter. But this second setup has been a real challenge and i am not sure why. I used these steps: https://www.raspberrypi.org/documentation/remote-access/vnc/. The only thing I did wrong on this - I setup automatic start up before ever connecting to the vnc server or setting up the password, which makes me think might be the root of the problem.
When I try to connect to my rp2 via finder's connect to server feature, I get a message saying that I cannot connect and need to check the settings on the host. I can ssh into rp2, and i can see that indeed tightvnc is not running, but! .X0-lock and X0 in /tmp/ folder do exist. If I delete both of these and restart tightvnc and then connect to the rp2 from my mac I can see grey pixelated screen & mouse cursor. ???
I tried removing tightvnc, tried disabling autostart, but it always persists which is beyond me (i have used linux before for school and work, so I am not a complete noob, but not an expert either). I tried redoing the steps to correct the install, no luck.
Any ideas? Any thing I can take a look at? I might just wipe the whole raspberry instal.
Thanks!
So I setup my homestead on a Win 10 machine and it seems like I find myself with this issue every now and then.
What happens is, homestead works just fine for a few days then all of a sudden, when I start it up, I can no longer access http://local.domain.dev (which is what I mapped to the IP 192.168.10.10) without appending it with port 8000.
I really don't get it. I think it has something to do with Windows updates? Although I can't really tell since Win 10 updates are so, I dunno, sneaky? I never know when there were updates until I see it on the notification bar. Most of the time, it doesn't tell you it's updating during bootup like Win 7 did.
In any case, this is really becoming a pain since having the domain is important to some of the features of the site I'm working on and specifying a port somehow screws it up (whole different story, don't ask).
So, I guess I'm asking if anyone else is experiencing the same issues on their Windows 10 machine and if they have a permanent fix to this?
This issue has popped up every now and then since I've upgraded to Win 10 and the last time had this issue, what I did to fix it was to update Vagrant and VBox.
I have Vagrant 1.7.4 and VBox 5.0.4, I think those are still the latest ones.
I'm having trouble opening VMWare on my Mac pro OS 10.10. I didn't do anything, moving its files or anything. I just turned my Mac off before I went to bed last night, and then this morning, when I tried to open VMWare again on my Mac, it keeps giving me this waring:
File not found.
I'm very confused, I've important files storing on my Windows workspace and need to have it restored.
What I've tried:
I've uninstalled VMWare on my machine, and re-downloaded and reinstalled it back, but, no luck, still the same warning. VMWare doesn't open at all.
I've also restarted my machine, hoping that something magic can happen, but unexpectedly, no luck.
OK, question resolved after I went to the Tech Stop at my University.
We just found that Windows 7 was somehow gone in my VMWare, then we opened Virtual Machine Library of VMWare, then re-installed Win7 into this VMWare, as this picture shows: http://postimg.org/image/blnk4x59z/
Now things are working fine.
Some other people might run into the same issue in the future, I don't know why this happened and nobody really knows what's going on.
I called VMWare tech support, but they don't provide any help since I downloaded it for free from our CS department website. But our department tech assistance has never met this issue. So nobody to turn to.
But anyway, pretty simple to fix:
Just re-install win7 in your VMWare, if you run into the same case as I did, by opening your Virtual Machine Library.
I experienced the same symptom after rebooting my Mac. SSun's answer helped me to solve it, but I think I can offer a bit of further insight.
VMWare Fusion was actually launching successfully, but when attempting to open a machine that was open at last quit, it fails to find the machine's files. I mis-interpreted the message as meaning that VMWare couldn't find an internal file and thought it had failed to launch. I got the same error when attempting to reinstall.
SSun refers to re-installing a guest OS. To be specific, one just needs to delete the reference to the virtual machine in VMWare (after dismissing the popup and you can access to the Window menu and open your virtual machine library); not reinstalling the actual guest OS. One can then recreate the reference by opening the machine via File > Open. Alternatively, resolve the root cause of the machine not being found.
In my case the root cause was that the virtual machine resided on a different hard drive to Mac OS and was referenced via a symlink. This hard drive had failed to mount automatically at boot up.
The same confusing error occurs when reinstalling because at the end of the install, VMWare launches automatically, triggering the symptom again.
I followed the steps from kb.mit.edu below to resolve this issue:
Click OK to close the error message.
Close the Virtual Machine. Click the red dot in upper left hand
corner or execute the keyboard shortcut Command+W
Follow the menu path Window >> Virtual Machine Library to open the
Virtual Machine Library.
Right-click on the thumbnail image for the VM or hold down the Ctr
key while clicking on the thumbnail image for the VM. Result: A
drop-down menu appears.
Select Delete Result: Remove Virtual Machine dialog box appears, with
options to Cancel, Move to Track or Keep File.
Choose Keep File.
However after doing the above, I found out that you need to resart your machine for eveything to work properly, else the problem will still persist.
If you get this error – including after deleting a VM (i.e., you cannot do anything inside the VMWare Fusion app to resolve this) – I found that the following will work, without reinstalling the app, deleting its preferences, or rebooting the host Mac, but at the tiny cost of having to re-add your VMs to the list of the available ones (a simple drag-and-drop operation):
Shut down any running VMs that are functioning, then shut down VMWare Fusion.
Trash the "~/Library/Application Support/VMware Fusion/vmInventory" file
Open the Activity Monitor app, search for "vm", and shut down everything with "vmware", "vmnet", and "vmrest" in its name. (Or do effectively the same thing in the Terminal, with ps aux | grep vm and then kill -9 on each of the appropriate process numbers, if you're command-line-oriented.)
Go find your VMs in Finder.
Restart the VMWare Fusion application.
Drag each of your VM packages to VMWare and drop it on the now-empty left pane of the Virtual Machine Library window to re-add the the VM to the list.
Test-start each of them to make sure you didn't break anything. [This is the paranoia option, here.]
Restart VMWare to make darned sure it writes out new config files. [My trust level in this app is quite low of late.]
I have the strangest problem with ftp. Immediately after a reboot the windows command line ftp program works fine.
Then, I try to use a friendlier ftp client (TotalCommander, which I have used for years) and it can log in, get folder contents, everything works until I try to upload a file. Then it seems that the connection gets suddenly closed -- and ftp ability is thereafter damaged.
Here is the strange part: ftp upload seems to then be permanently broken. And the way it is broken is quite strange. I go back to the command line ftp client, and I can connect, list folders, change folders, download files of any size, upload small files <2Kbytes, BUT upload of a file bigger than 2K causes the connection to be dropped, and the command times out.
Reboot the OS (64 bit Win 7) and everything is fine again.
I have disabled the windows firewall since many discussions centered on this. The behavior is the same whether windows firewall is on or off.
I have tried toggling PASV mode, and again, the behavior is the same whether sending passive or not.
I have tried in both binary and ASCII mode, and the behavior is the same.
This problem began when I reinstalled the Windows 7 Enterprise, Service Pack 1 on a new disk. Installed all 146+ patches and updates.
Network is not a problem: no problems with my laptop connected to the same network. No problems with the remote server when accessed from other machines. It is clearly isolated to this new installation of windows.
Any ideas at all how running one program could cause the command line ftp to become unable to send files if they are >2k?
The problem has magically gone away, and this question has won me the time honored "Tumbleweed" badge.
While it is inconclusive, the problem appeared to be something with the network driver. The application was making a request that somehow put the driver in a mode which would limit sending (only for ftp as far as I know) to less than 2K. I reinstalled the latest network driver and latest chipset drivers, rebooted a number of times, to no effect. However, I installed the HP Printer driver, and poof, the problem went away. This might simply be a coincidence, or there might be some OS utility that got updated as a result. If anyone has clues as to why installing HP printer software would fix a network card, please share.