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.
Related
I have a problem with Windows 10 and I am kinda clueless on why and how I should fix it.
I have a work laptop that was upgraded to windows 10 last month. Ever since I got it I have been having problems with my Internet connection. About every one or 2 hours I stop being able to access the internet. I try and run the Windows diagnostic tool but there are of no help. Only restarting the computer helps, which is a major pain.
I have installed Wireshark to monitor my connections but unfortunately I am not really savvy with it. I can however see that there are quite a few broadcasts being made (they make 90% of all connections being made) but I cannot see from where they come.
I have tried disabling all energy saving options, updating the drivers for the network adapter, reinstalling the antivirus and even a hardware test. Nothing helped. My next step would be to reinstall Windows but I only want to do that as a last resort.
Any ideas what I could do next?
So, I actually fixed my problem. I didn´t really figure out exactly why it happened but I found a work around.
In Windows 10, I opened the Event log to see if there was an error being logged. Thankfully I have been documenting when I lost connection so this was easy to find. I saw that everytime I lost connection, Event 4231 was being logged. I googled the Id and found a solution on this website.
I followed the instructions there and had no more problems ever since.
Recently lost my hard drive where I had WAMP installed and Imagick working.
Someone else did that part for me way back.
Reinstalling Win7 and getting everything working again = nightmare.
So I installed the latest version of WAMP - NO Imagick.
3 days of trying all the solutions on this site (and some others - sorry) and got nowhere.
Does anyone know of a "one shot" installation that will work out the box?
Maybe a fork of one of them - I looked but found nothing
Or maybe I should install Ubuntu onto an old PC and use that as a web server on my home LAN?
Seriously - they are depreciating the GD library some time soon and Imagick is apparently the successor but no-one supports Imagick natively.
Jumping through all sorts of hoops is no guarantee that it will work either as I have painfully found out.
Thanks in advance people.
WAMP and XAMPP are not up to speed with the transition from the soon to be removed GD library to the ImageMagic library and it would seem that neither are planning to bring their products up to date any time soon.
That leaves many users with a major problem as most web site developers need to be able to manipulate images at some time or another during their work.
For users who are not at a reasonably high level of expertize as far as messing around in the guts of the (in my case, Windows) operating systems, this is a nightmare and can be downright dangerous.
I did find what seemed to be a viable alternative in WampDeveloper Pro but unless you specifically go looking for it, their website is very hush-hush about the fact that its going to cost you over $125 to get it working.
You only find out about this at the first run after installing.
So my options are the following:
Put one of the Ubuntu distributions on a VM
or
Find an old drive, install it into your PC and make the PC dual boot using a Ubuntu distribution.
The second option will "ease" me into converting from Microsoft based OS reliance to a Linux based OS however if that does not work out, I do have the option to create an Ubuntu VM under the Windows system (I have used VM for a while under Windows) and use that in place of the other Windows based web server alternatives.
Either way I will be able to carry on servicing my clients and making a living without spending money or having a stroke due to pure frustration.
I may regret this decision BUT I may start wondering to myself "Now why did you wait so long?"
I have vagrant installed on my Windows 7 machine, currently it has an installation hooked up with VirtualBox & a CentoOS install.
While it everything does work, and the server is all configured and the PHP is running ok it really does seem to crawl. I currently have a development version of Magento on here and it is much much slower than I would expect. Occassionally some pages (the checkout ones) can take up-to 2 minutes to process and bring the user to the next page, obviously this makes development very frustrating and slow.
Can anyone suggest any ideas on the best way to optimise my vagrant box?
p.s i've not set this up myself so i am not fully aware of all its configs/settings etc...
Magento has a lot of files, and Virtualbox file share mechanism between Linux and Windows is very slow. Workaround is to use samba saerver on guest and mount it on host.
The LAN which has about a half dozen windows xp professional pcs and one windows 7 professional pc.
A jet/access '97 database file is acting as the database.
The method of acccess is via dao (DAO350.dll) and the front end app is written in vb6.
When an instance is created it immediately opens a global database object which it keeps open for the duration of its lifetime.
The windows 7 machine was acting as the fileserver for the last few months without any glitches.
Within the last week what's happened is that instances of the app will work for a while (say 30 mins) on the xp machines and then will fail on database operations, reporting connection errors (eg disk or network error or unable to find such and such a table.
Instances on the windows 7 machine work normally.
Moving the database file to one of the xp machines has the effect that the app works fine on ALL the xp machines but the error occurs on the windows 7 machine instead.
Just before the problem became apparent a newer version of the app was installed.
Uninstalling and installing the previous version did not solve the problem.
No other network changes that I know of were made although I am not entirely sure about this as the hardware guy did apparently visit about the same time the problems arose, perhaps even to do something concerning online backing up of data. (There is data storage on more than one computer) Apparently he did not go near the win 7 machine.
Finally I know not very much about networks so please forgive me if the information I provide here is superfluous or deficient.
I have tried turning off antivirus on the win 7 machine, restarting etc but nothing seems to work.
It is planned to move our database from jet to sql server express in the future.
I need some suggestions as to the possible causes of this so that I can investigate it further. Any suggestions would be gretly appreciated
UPDATE 08/02/2011
The issue has been resolved by the hardware guy who visited the client today. The problem was that on this particular LAN the IP addresses were allocated dynamically except for the Win 7 machine which had a static IP address.
The static address happened to lie within the range from which the dynamic addresses were being selected. This wasn't a problem until last week when a dynamic address was generated that matched the static one and gave rise to the problems I described above.
Thanks to everyone for their input and thanks for not closing the question.
Having smart knowledgeable people to call on is a great help when you're under pressure from an unhappy customer and the gaps in your own knowledge mean that you can't confidently state that your software is definitely not to blame.
I'd try:
Validate that same DAO and ODBC-drivers is used on both xp- and vista machines.
Is LAN single broadcast domain? If not, rewire. (If routers required make
sure WINS is working)
Upgrade to ms-sql. It could be just a day of well worth work, ;-)
regards,
//t
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.