edit - just realised you said you could access the ui via the localmachine - strongly points to a firewall blocking comms accross port 80.

A couple of places to start:

1. Are all FME services running on the machine?
2. Can you access and login into FME Server on the machine its installed on via http://localhost:80/fmeserver? if no, what do the logs say?
3. If yes, can you ping the server from the remote machine? If not, suggests that no connection can be made across any ports (not always the case)
4. If FME Server loads on the server but not on the remote machine suggests that there is a firewall blocking some (or all) connections between the environment(s)

Hi, for 3... yes i can ping the server from the remote machine. For 4, I'd have thought this too but i was using that remote connection to do backups and stop automations etc right up to the point where I uninstalled 2020 and installed 2022. From that point on remote access failed. We're still digging (with no obvious results) and it's not critical over the holidays as the server is running and we can access the interface on the host but I'm going to try another reinstall when back in the new year

Thanks for the response

Rob

Hello, we had the same issue, al works well on FME server 2020, but the upgrade to 2022 with same host name on new server (Windows Server 2019) only works in the browser on the server itself.

The firewall rule that was made during the installation give acces to the program ...\\Server\\fme\\fme.exe after changing that to 'all programs that meet the specified conditions' connection from remote browsers works well.

Can't remember I had to change that on the FME 2020 server.

Brillliant, worked a treat, I need to check what the setting is on the server that "worked" out of the box!

thanks

Rob

On the server that worked it was still set the same but I've updated it as above for consistency!