Windows 10: since 1607 upgrade, all lan browser & database requests time out

Since the 1607 upgrade, a win10 laptop times out all requests from our LAN to its Apache web server and to its MySQL server.


The apache & mysql servers on the win 10 machine are functioning normally for local browser and database requests.


Other LAN machines can ping the machine, and can browse its files & folders eg with Windows Explorer.


But all webserver and MySQL server connection requests to it from the LAN time out.


Turning off the win10's antivirus software makes no diff.


How do I fix this?

:)

 

since 1607 upgrade, web and database connection requests to win 10 machine time out

Since the 1607 upgrade, a win10 laptop times out all requests from our LAN to its Apache web server and to its MySQL server.

The apache & mysql servers are functioning normally for local browser and database requests from the win 10 machine.

Other LAN machines can ping the machine, and can browse its files & folders eg with Windows Explorer.

But all webserver and MySQL server connection requests from the LAN time out.

Turning off the win10's antivirus software makes no diff.

How do I fix this?

 

since 1607 upgrade, web and database connection requests to win 10 machine time out

OK...

 

Are you running any kind of Firewall? You really are best to run a LAMP server on Linux, not on Windows. You can use a Raspberry Pi 3 with a 64gb Class 10 Micro SD card running Raspbian.

 

Turns out the 1607 "upgrade" turned on the firewall for lan connections.

Microsoft intrusiveness, ugh.

 

Common advice, yes, I'd never run a production server on Windows unless I had to. This is a devel server, our use case involves too many win tools, another instance of develop on Windows, deploy on *Nix.

As it turns out,

 

You can use SQL Workbench to handle the SQL part. You can also install the web version to handle SQL and PHP. All servers run on Linux and using the Raspberry Pi 3 as a LAMP server to test the final product is a lot better than dedicating a machine. It can handle the server with no problem.

As for Development vs. using, it will all depend on how many connections to it. You want to run the server with a CLI not a GUI. That is why Linux distros such as Ubuntu Server and Debin, along with Raspbian Lite are the prime choice. I have never had any issues with Docker with NethServer and same as the Synology NAS I have. It works better than any VM system.

The Window tools will still work for connecting to the LAMP server. The only time that you may want to use Windows is Windows Server running a Sharepoint Server.

 

> You can use SQL Workbench to handle the SQL part.

You mean MySQL Workbench? Not an option: too fat, too cumbersome, too buggy.

> You can also install the web version to handle SQL and PHP.

There's no "web version" of MySQL Workbench, but it can can connect to other LAN machines, if that's what you mean. So can the raw (and much leaner) mysql client, and so can several browser-based (and also leaner) MySQL maintenance tools.

We have *Nix installations of MySQL, but we also need this windows environment.

Meanwhile, the problem turned out to be that Update 1607 unnecessarily, and without consulting us, turned on the lan firewall. Ugh.

 

First off it is Linux, not *nix. Second it was not caused by the Anniversary edition, and yes it is necessary to have it, since it fixes a lot of issues with the previous edition that caused other issues. MySQL Workbench is not buggy, not fat, cumbersome or buggy. PHPmyadmin is used on the server to allow you to access the SQL tables from another machine on the network.

Running a server on a desktop version of windows is going to keep giving you headaches. Around 99% of the servers for Web, SQL, etc. run on Linux. The move for companies is to go to Linux completely, because it is hardened to not allow attacks or zero day flaws.

You will find that you are going to keep having headaches if you want to use Windows desktop for your project. I have been running various LAMP servers with no issues with Linux and there are also websites and SQL servers that are using the Raspberry Pi 3 running Raspbian Lite and do better than a regular computer.

The suggestions I gave are just another option and will be the best option for you if you do not want the headaches that Windows 10 is going to keep giving you on this project.

As for the "Lan" Firewall. The only firewall that would be for the LAN, would be on the Gateway. If the connection came up as Public, Windows is going to automatically enable the Firewall if you just click through everything and not choose to Customize the installation. It is called slow down and taking your time while setting up the OS. I have yet to have any install of Windows 10 just automatically enable something that I disabled.

 

> First off it is Linux, not *nix.

Argumentative are we? It's often referred to in shirthand as "Nix.

> Second it was not caused by the Anniversary edition

It's not the first time Windows update has set Windows firewall on a machine where it was turned off.

> , and yes it is necessary to have it, since it fixes a lot of issues with the previous edition that caused other issues.

Naturally, if software is in use, it needs updates, no disagreement about that.

> MySQL Workbench is not buggy

Sorry, if you think that, you're just mistaken. Do some reading in the MySQL Workbench forum at forums.mysql.com.

> not fat, cumbersome or buggy.

Very fat, very cumbersome, buggy as above. Less than it used to be, granted, but there still are processes that you best take to the mysql commandline client program.

> PHPmyadmin is used on the server to allow you to access the SQL tables from another machine on the network.

?! That's one possibility. Not the only one. Not the best for all circumstances even. In fact I use it about once a month.

> Running a server on a desktop version of windows is going to keep giving you headaches.

If it's a production server, sure. Naturally, I wouldn't consider running a production server from a desktop. This is a development server.. Been doing it for twenty-five years. Perfectly reasonable development environment.

> Around 99% of the servers for Web, SQL, etc. run on Linux.

It's a bit less than that, but that's in the ballpark, jut not relevant to the present circumstance..

> As for the "Lan" Firewall. The only firewall that would be for the LAN, would be on the Gateway.

NAT. In the router.

> If the connection came up as Public, Windows is going to automatically enable the Firewall
> if you just click through everything and not choose to Customize the installation.

Not sure what you're on about here. This isn't a fresh win10 installation, we're talking about upgrade 1607, where there was nothing to click through. It's the third time here that a win10 upgrade has turned on a windows firewall that had been turned off, and it's not the only setting that such upgrades have changed unbidden.

Thank you for your attention.