I've created two servers (Windows Server 2019) that are (theoretically) identical.  One for production and one for test.

FM19 is set up for Web Publishing on each.

The firewall settings match.  I've opened all the specified Filemaker ports.  All three servers are on the same network.

I am able to connect a worker server to my Test server.
I am not able to connect that same worker machine to the Production server.

I've tried to connect while no users were signed in after the system had been freshly restarted.

I've created a 2nd worker server in order to test.  That server failed to connect to Production, as well.

In the Filemaker Event log for my Test server I get:

2021-xx-xx 14:33:39.161 -0400    Information    518    XXXX    Administrator connected: "yyyy [130.x.x.x]" (admin console).
2021-xx-xx 14:33:39.334 -0400    Information    1043    XXXX    Web Publishing Engine (worker01.x.x.x) was added.

I removed the worker from the Test system:

2021-xx-xx 14:42:47.597 -0400    Information    1044    XXXX    Web Publishing Engine (worker01.x.x.x) was removed.

in the Filemaker Event log for my Production server all I get is:

2021-xx-xx 11:55:47.815 -0400    Information    518    ZZZZ    Administrator connected: "yyyy [130.x.x.x]" (admin console).

On the Deployment screen, what I get is: An unknown error occurred

 

Any thoughts or suggestions?

my bet would be to re install FMS on the worker.

 

Jerry

 

 

I did that just now.  Same result.  Administrator user is able to connect to the master, but nothing else shows in the log. 

The deployment assistant shows: an unknown error occurred

What ports do you have open? Workers use 16002 to connect to the master.

Test Server: 16000, 16001, 16002, 80, 443, 5003, 2399

Production Server: 16000, 16001, 16002, 80, 443, 5003, 2399

Worker:  16000, 16001, 16002, 80, 443, 5003

 

Using Deployment Assistant Worker connects to Test, but not to Production.