A web page that opens on port 80 tells you the panel's web server is reachable, and nothing more. Remote access is a separate feature: firmware version 2.4 or later, switched on in the project's panel network settings, and a factory-default reset after a firmware update. No port swap or extra address adds it; the fix runs version check, reset, settings, download.
A panel's web page opens in the browser, yet there is no remote access anywhere on it. That page tells you one thing: the web server answers on port 80, and nothing more about the panel's features. Remote access is a separate panel service, and it is gated three ways. It exists only in panel firmware version 2.4 and later. It has to be switched on in the project's panel network settings. And after a firmware update the panel has to go back to factory defaults before the feature comes up. There is no address to type and no port to swap that will summon it. The fix runs version check, reset, settings, download, in that order.
Why the web page is not the remote-access door
The web server and remote access are two different services. The web server answers a browser on port 80 and serves the panel's page. Remote access is delivered through that same page: once the feature is enabled and the project is downloaded, a remote access link appears there, and the link hands you a client program to install. You point the browser at the panel address alone. There is no second address and no second port to type.
Swapping ports between the services cannot create the feature. On a panel below version 2.4 the service does not exist at all, and on a panel at 2.4 or later it stays off until the project switches it on. The gating is not unique to panels: some Ethernet devices enable their web server only from a minimum configuration-tool release, as in a web server switched on through advanced settings in a newer configuration tool.
Symptoms and what each points to
- The page opens and no remote access link appears. The panel side lacks the feature: firmware below 2.4, or a project downloaded with the feature still switched off.
- Panel and project both read 2.24. The feature does not exist at that version. No port, address or browser setting adds it; the update sequence below is the path.
- Firmware went to 2.4 or later, project downloaded, link still absent. The factory-default reset after the update was skipped, or the switches were never set.
- The link shows and the client downloads, then it misbehaves. Check that the client file kept its original name; renaming it breaks the link between the panel and the client.
- The remote screen appears but operators cannot touch anything. Viewing and control are separate permissions in the project; the remote control permission was not enabled.
Check the version before anything else
Read two versions, not one: the panel firmware and the programming software. The setup documentation requires version 2.4 or later of both for remote access. Read the panel's version from its system menu, and read the project's version in the software before planning any transfer; the field methods are in read an HMI panel firmware version for field maintenance and in check the HMI firmware revision before a project transfer.
Below 2.4 there is no setting to find. The number to act on is the version, so book the maintenance window and update. At 2.4 or later the cause is configuration, and the next section covers it.
The fix, in order
- Load panel firmware 2.4 or later, and build the project in programming software of the same minimum version.
- Reset the panel to factory defaults. Use the reset tool installed with the programming software, or the panel's system menu; on a touch panel the path is an on-screen utility that opens when you press the top-left corner for several seconds, then select the factory-default memory operation. The reset clears the panel's project and network settings, so run it inside the maintenance window with the project file and the panel IP address written down.
- In the project's panel network settings, enable the web server and enable remote access. Both switches are needed.
- Re-enter the panel IP address in the Ethernet port settings. The old project's address does not carry over into the updated project.
- Enable the remote control permission in the project if operators will do more than watch.
- Download the project to the panel over USB, the transfer path the commissioning instructions use.
- Browse to the panel address. The page that answered before now carries a remote access link.
- Follow the link, download the client package and run it without renaming anything. Later sessions start from the installed client's own shortcut; the browser was only the delivery path.
Example: port 80 opens and the panel reads 2.24
Scenario: a packaging line panel serves its status page on port 80. You browse to 192.168.1.50, the illustrative address for this example, and the page loads, but no remote access link appears. The system menu reads panel firmware 2.24, and the project was built in software for 2.24. You have booked a 30-minute maintenance window for the job.
Compare the versions. 2.24 is less than 2.4: written to the same length, 2.24 against 2.40, and 2.24 < 2.40. The digits after the point run in release order, so 2.4 is the later release. Because remote access first exists at 2.4, this panel has nothing to enable, and no browser string or port swap changes that.
Decision: schedule the update. In one 30-minute window, load firmware 2.4 or later, reset the panel to factory defaults, enable the web server and remote access in the panel network settings, re-enter 192.168.1.50 in the Ethernet port settings, and download the project over USB. As an illustrative split of the 30 minutes, allow 10 minutes for the firmware transfer, 5 minutes for the reset and network re-entry, and 10 minutes for the project download, which leaves 5 minutes to open the page and confirm the link. The page now shows the remote access link, the client installs under its own file name, and the remote session runs from the installed client. If any step overruns its share, stop and reschedule rather than leaving a plant panel half-configured, because the reset has already wiped the old project and address.
If the link shows but the session still fails
The panel side is complete once the link shows and the client installs. What remains is the workstation and the network path, so test in this order.
From the plant network the session works but from outside it does not: that is the router path, not the panel. Work through HMI remote access port forwarding fails: test each step.
The client connects and then drops while the page and FTP still answer: compare your case with remote HMI project connection fails while web and FTP work.
Nothing answers after the update and reset: the IP address is the first suspect, because the reset and the new project both start from defaults. HMI panel will not communicate after a firmware update walks through that recovery.
The page answered last week and now stops while FTP still responds: that split points at the web server itself, covered in HMI panel web server stops responding but FTP still works.
The decision for each case
Recommendation: Read the panel firmware version and the project's software version before touching any port setting. At 2.24 or any version below 2.4, book a 30-minute maintenance window and run the documented update: firmware 2.4 or later, a factory-default reset, both switches in the panel network settings, the IP address re-entered, and the project downloaded over USB. At 2.4 or later, the fix is configuration: enable the web server and remote access, set the remote control permission if operators will control, download the project again, and use the link on the panel's page. Leave the working port assignment alone throughout; it is the door the feature uses.
Questions
Can the account name and password be left blank in the project?
The setup notes allow it for a single-user setup: with both fields blank, the client opens a session without a sign-in. Treat that as a site access policy question, not a default. If anyone outside the controls group can reach the panel, put an account name and password in the project's permission fields and download the project again before the link goes live.
The client downloads but will not run on the PC. Is the panel at fault?
No. The link, the download and the untouched file name tell you the panel side is complete. The client is a program built for the browsers and operating systems its setup documentation names, so check the version 2.4 help for that list and run it on a workstation that matches. Repeating the reset or swapping ports will not change what the PC runs.
Is the factory-default reset needed if the panel always had version 2.4?
The documented requirement ties the reset to the firmware update: after updating the panel, reset it to factory defaults so the new feature comes up. A panel that shipped at 2.4 or later, where remote access was only ever left switched off in the project, needs the project switches and a fresh download, with no reset in between. Reading the version first is what tells you which case you are in.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.