IMDTouchKnowledge BaseShop main store

Troubleshooting

Why Sm@rtServer Rejects Sm@rtClient on a WinCC Runtime PC

HMI and touchscreens Published 7 min read

Short answer

Sm@rtServer is a VNC server that listens on TCP 5900, so a refused Sm@rtClient session has one of three causes: no VNC password is set, loopback connections from 127.0.0.1 are filtered, or another VNC server such as TightVNC owns port 5900. Identify the listener with netstat -ano | findstr :5900 first, then set the password in Runtime settings and restart the runtime.

On this page
  1. What Sm@rtServer is on a PC runtime
  2. Check 1: Who owns TCP 5900
  3. Check 2: Set the VNC password
  4. Check 3: Loopback connections from 127.0.0.1
  5. Check 4: Another VNC server on port 5900
  6. What the session controls
  7. The decision for each case
  8. Questions asked

A refused Sm@rtClient session on a PC running WinCC Runtime Advanced has one of three causes, and TCP 5900 tells you which. Sm@rtServer is a VNC server: it speaks the RFB protocol and listens on TCP 5900 by default, and Sm@rtClient is only a VNC viewer. "This server does not have a valid password enabled" means no VNC password exists yet. "loopback connections aren't enabled" means the filter on connections from 127.0.0.1 is doing its job. A bare "Authentication failed" usually means TightVNC, not Sm@rtServer, is the process answering on 5900. Find the listener with netstat -ano | findstr :5900 before touching any password, because settings changed on the wrong server never reach the client. All of this works on a PC runtime, not only on physical panels — the difference is that a connected session controls the whole Windows desktop.

What Sm@rtServer is on a PC runtime #

You enable the server in the HMI project under Runtime settings with the "Start Sm@rtServer" option. On the PC, WinCC Runtime then loads pdata.fwc as the configuration file, and the server that option starts is a standard VNC server: RFB protocol, TCP 5900 by default. Sm@rtClient is a VNC viewer, and any standard VNC client connects to it the same way. On Windows that has three consequences:

  • A VNC server exports the whole desktop, not one application window. On an operator panel the desktop is the HMI, so you never see the difference; on Windows 10 a session takes over the entire PC.
  • The server refuses every incoming connection until a VNC password exists.
  • The server rejects loopback connections — a viewer on the same PC targeting 127.0.0.1 — unless they are explicitly allowed.

A successful telnet handshake to 127.0.0.1 port 5900 proves only that some process holds the socket. It does not tell you which process, and it does not prove the server will accept a viewer.

Check 1: Who owns TCP 5900 #

Before you touch passwords, find out which process owns the port. If another VNC server holds it, every password and loopback change you make in Sm@rtServer has no effect on what the client sees.

  1. On the runtime PC, open a command prompt and run netstat -ano | findstr :5900.
  2. Read the PID on the LISTENING line and resolve it with tasklist /FI "PID eq <pid>".
  3. In Task Manager, Details tab, look for tvnserver.exe or any other VNC server process.

Interpret the result:

  • No listener on 5900: Sm@rtServer did not start. Confirm "Start Sm@rtServer" is checked in Runtime settings, regenerate the project so pdata.fwc carries the setting, and restart the runtime with that file.
  • The listener is tvnserver.exe or another VNC product: go to Check 4.
  • The listener is the WinCC runtime process: go to Check 2.

The local address column also tells you the reach: 0.0.0.0:5900 accepts connections on every adapter, while a listener bound only to 127.0.0.1:5900 accepts local connections only.

Worked example, with example output values:

C:\> netstat -ano | findstr :5900
TCP    0.0.0.0:5900    0.0.0.0:0    LISTENING    4216

C:\> tasklist /FI "PID eq 4216"
tvnserver.exe    4216 Console    1    12,842 K

PID 4216 and the memory figure are illustrative; the columns are what matter. The listener answers on all adapters, and the owner is TightVNC, so the Sm@rtServer password will keep failing no matter how often you retype it. Decision: go to Check 4, stop the service, then re-run the same two commands until the LISTENING line belongs to the WinCC runtime process.

Check 2: Set the VNC password #

The "no valid password" refusal is issued before any authentication happens, and it does not depend on where the client connects from. You can set the password in three places:

  • TIA Portal, HMI device > Runtime settings > Remote access > Sm@rtServer. Use this when the password should travel with the project. The dialog layout varies between TIA Portal versions, and in some V20 installations the password field is not shown there at all — fall back to the applet below.
  • Control Panel > WinCC Runtime Advanced Internet > Remote tab > Change Settings. The Server page takes the access passwords — two of them, one of which covers view-only mirroring. This applet is available whether or not the runtime is running.
  • The Sm@rtServer icon in the Windows system tray while WinCC Runtime is running. Good for quick changes; the same dialog also carries the loopback options.

Make one location the owner of the password, then restart WinCC Runtime so the running server loads the new setting. Reconnect and read the result:

  • A password prompt appears: this branch is resolved.
  • "loopback connections aren't enabled" appears: the password is now accepted, and the loopback filter is the next barrier — Check 3.
  • "Authentication failed" appears: go back to Check 1, because another server is almost certainly answering.

Check 3: Loopback connections from 127.0.0.1 #

The settings dialog carries two options. "Allow loopback connections" admits viewers that connect from 127.0.0.1. "Allow only loopback connections" admits local viewers and blocks every remote one — leave it unchecked on any system that needs remote access.

VNC servers block loopback by default for a practical reason: a viewer sharing the same desktop it is displaying draws its own window inside itself, producing a recursive mirror. A same-PC session is therefore a smoke test that the server answers, never a working operating mode.

There is a known failure pattern: both combinations of the two checkboxes tried, the runtime restarted after each change, and Sm@rtClient still reports "loopback connections aren't enabled". When the setting does not take effect after a runtime restart, stop toggling it and move the test off loopback:

  • Target the PC's own LAN adapter address instead of 127.0.0.1. The connection then arrives with a non-loopback source address, which a filter keyed on 127.0.0.1 does not catch.
  • For a conclusive test, run Sm@rtClient on a second PC and connect to the runtime PC's LAN address. With the password set, this path connects and prompts for it.
  • If the remote attempt times out with no server message at all, add an inbound Windows Firewall rule for TCP 5900.

Check 4: Another VNC server on port 5900 #

Only one process can bind TCP 5900. If TightVNC Server started first, it owns the port; Sm@rtClient negotiates with TightVNC, sends the Sm@rtServer password, and gets a bare "Authentication failed" with nothing in the message pointing at the wrong server. Confirm tvnserver.exe in Task Manager, Details tab, then:

  • Stop the service itself with the "Stop TightVNC Service" item in the TightVNC Start-menu folder, and watch tvnserver.exe disappear from the Details tab. Killing the process is not enough — depending on its recovery configuration, the Windows service restarts it and takes the port back.
  • To keep it from returning after a reboot, set the TightVNC service startup type to Manual or Disabled in services.msc, or move TightVNC to a different port.

What the session controls #

A connected session shows and controls the whole Windows desktop, taskbar included. That is normal VNC framebuffer sharing: it looked scoped on a panel only because the panel desktop is the HMI. A StopRuntime button behaves the same way — on a PC it ends the runtime process, and with no panel shell underneath it, the application closes to the Windows desktop. Neither is a fault.

One safety note, because it belongs here: a session into a runtime PC can start and stop a real machine through Windows, so treat the VNC password and the TCP 5900 firewall rule as machine-safety boundaries, not as IT conveniences.

If the point of the PC runtime is to prove the HMI project before a panel exists, treat it like any bench setup — the same discipline as testing HMI simulation against a live PLC. But commit to this limit now: Sm@rtServer cannot scope a PC session to a single window. If you need exactly the HMI window remotely, the project has to run on a panel; on a PC you accept full-desktop VNC semantics.

The decision for each case #

  • No listener on TCP 5900: "Start Sm@rtServer" never reached the running runtime — confirm the checkbox, regenerate pdata.fwc, restart.
  • "This server does not have a valid password enabled": set the password in one place — Runtime settings in TIA Portal, the WinCC Runtime Advanced Internet applet, or the tray icon — and restart the runtime.
  • "loopback connections aren't enabled": allow loopback for the smoke test, then run the real test from a second PC against the LAN address; open TCP 5900 in the firewall if it times out silently.
  • Bare "Authentication failed": tvnserver.exe owns the port — stop the TightVNC service, disable it at boot, and re-check ownership with netstat -ano.
  • Whole-desktop takeover and StopRuntime closing the application: correct behavior on a PC runtime; plan the operator interface around it or move the project to a panel.

Questions asked

Does Sm@rtServer work on a PC runtime, or only on physical HMI panels?

It works on both. On a panel the exported desktop is the HMI screen, so the session looks scoped to the application. On Windows the runtime is just another program, so the session shows and controls the entire desktop, including Windows itself. That is normal VNC behavior, not a configuration error.

Why does my StopRuntime button close the whole application on the PC?

On a PC, StopRuntime ends the WinCC Runtime process and returns to the Windows desktop; there is no panel shell underneath to fall back to, so nothing of the HMI remains on screen. If the operator must stay inside the application, use screen navigation instead of stopping the runtime.

Is connecting Sm@rtClient to 127.0.0.1 on the same PC a valid test?

Only as a smoke test that something answers on TCP 5900, and only with loopback connections allowed. A viewer on the same desktop draws its own window inside itself, so the picture becomes a recursive mirror. Prove remote access properly from a second PC against the runtime PC's LAN address.

My telnet test to port 5900 succeeds, so why does Sm@rtClient fail?

Telnet proves only that some process holds TCP 5900; it does not identify the process and does not prove it will accept a viewer. Resolve the listening PID with netstat -ano and tasklist before changing any passwords, because a TightVNC server that owns the port will keep rejecting the Sm@rtServer password.

Keep reading

  • How-to

    Testing HMI Simulation Against a Live PLC

    A standalone HMI simulator proves screens and navigation, not communications. Test against a live controller only through a documented online-simulation mode or a physical panel, and verify every read at two data states and every write at the controller before release.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Freezes or Updates Slowly Over Serial

    A panel-wide freeze or slow updates over serial is a link fault — driver, PLC port, wiring, or startup timing — not a screen-object fault. Test the two field-proven fixes first: a 10-second startup delay before the first poll, and a port set to four-wire RS-422 at 19,200 baud. Fix an isolated stale tag separately, by address and data type.

    HMI and touchscreens

  • Explainer

    HMI OPC UA Server vs Client: Which Direction Works

    OPC UA support on an HMI spec sheet almost always means the panel runs a server that serves its tags to external clients. Reading PLC symbols by name needs an OPC UA client driver, a separate capability you verify in the driver list for your exact software release, target and license.

    HMI and touchscreens