Troubleshooting
Why KTP900 Basic Sm@rtServer Refuses Remote Client Connections
Short answer
A KTP900 Basic refuses Sm@rtServer clients for two dominant reasons: the panel firmware is still below V17, so the license-free service introduced with WinCC V17 is not actually available on the device, or the client has no routed path to the panel's network. Update the panel to firmware V17, confirm the Sm@rtServer password, then connect from the same subnet or through a VPN — the service is a LAN VNC server and nothing more.
On this page
- Why will Sm@rtClient not connect to my KTP900 Basic?
- Which firmware does the panel need for Sm@rtServer without a license?
- Where is the Sm@rtServer license key supposed to be?
- What address and password does the client need?
- Can I reach the HMI from the internet without a VPN?
- In what order should I test the connection?
- Why does the session connect and then stop responding?
- Questions asked
Your KTP900 Basic refuses remote clients for one of two dominant reasons: the panel is still on firmware older than V17, so the license-free Sm@rtServer introduced with WinCC V17 is not actually available on the device, or the client has no routed path to the panel, because Sm@rtServer is only a VNC server on the panel's own LAN. The fix sequence is short: read the panel's real firmware in TIA Portal, update it to V17 if needed, confirm the Sm@rtServer password, prove the session on the local subnet, then reach the panel through a VPN. Nothing in this fix requires a license key from the box.
Why will Sm@rtClient not connect to my KTP900 Basic? #
The usual cause is the panel, not the app: a KTP900 Basic on firmware older than V17 accepts the Sm@rtServer setting while its runtime refuses clients, because the license-free service from WinCC V17 materializes only when the panel's firmware reaches that generation.
TIA Portal V18 on your desk identifies the engineering environment; it says nothing about the firmware inside the panel, and a download that succeeds against older firmware still leaves the option visibly enabled on the device. That is why this failure looks like a mystery. Four conditions must hold at once, and the client error rarely says which one is missing:
| What you see | Where the fault lives | What settles it |
|---|---|---|
| Option enabled, connection refused outright | Firmware generation or license state | The firmware the device reports, not the project version |
| Client reaches the panel, login rejected | Sm@rtServer password | Re-enter the password in the project and on the panel |
| Works locally, fails from another internet connection | Routing or VPN | A route from the client to the HMI subnet |
| Session opens, then stops responding | Service stability | The known KTP limitation, not licensing or firmware |
An enabled checkbox proves only the second of those. When the server side is a WinCC Runtime PC rather than a Basic panel, the rejection has different causes — read why Sm@rtServer rejects Sm@rtClient on a WinCC runtime PC.
Which firmware does the panel need for Sm@rtServer without a license? #
Update the panel to firmware V17 or later, the level at which Sm@rtServer runs license-free on Basic Panels 2nd Generation; projects in V14 through V16 still require a purchased license, and the panel's firmware — not your TIA Portal version — decides which side of that line the device is on.
As of WinCC (TIA Portal) V17, a Sm@rtServer license is no longer required for Basic Panels 2nd Generation. The licensing change rides on the software generation, but the panel only honors it once its own firmware is at the V17 level, and that panel update is the step people skip.
- In TIA Portal, connect to the panel online and read the firmware version the device itself reports.
- Compare it with the device version configured in the project — a V18 project downloading onto a panel that reports an older level is exactly this failure.
- Update with the firmware image published for your exact panel model, then download the project again.
- Re-read the firmware from the device and confirm V17 or newer before blaming the client.
If a newer image exists for your exact model, taking it is fine; what decides this branch is that the reported level is not older than V17. One documented quirk to ignore along the way: the "Load preview" dialog still displays a licensing note on Basic Panels from V17 onward even though no license is required.
Where is the Sm@rtServer license key supposed to be? #
Nowhere — there is no key in the box, because from WinCC V17 the Basic Panel 2nd Generation carries no Sm@rtServer license requirement at all, and nothing is supplied to type in; a purchased key only exists if you stay on V14 through V16.
The "included license" you may have been told about is the V17 licensing change, not a physical key. A purchased license only enters the picture if you deliberately stay on V14 through V16, and even then the correct move is a transfer to the panel with the Automation License Manager (ALM), never a code typed into a dialog. Decision: if the panel can be brought to the V17 level, buy nothing.
What address and password does the client need? #
Connect with the panel's IP address and the Sm@rtServer password you set in TIA Portal or on the panel itself, from a client on the same subnet — the hostname is not a substitute for the address, and the Sm@rtServer password is separate from every other credential.
Read the IP from the panel's own network settings or from the device configuration in TIA Portal, and set the client to the Sm@rtServer/VNC connection mode. The password is the one configured for the service, in the project's runtime settings or on the device; it is not the panel's operator login or any network credential.
Illustrative example with real addresses: the panel holds 192.168.10.5 with subnet mask 255.255.255.0, so its network is 192.168.10.5 AND 255.255.255.0 = 192.168.10.0/24. A client PC at 192.168.10.42 masks to the same 192.168.10.0/24, so the session can go direct. A phone on cellular, or a VPN client holding 172.16.4.20, shares no network with the panel and connects only if the VPN routes 192.168.10.0/24 toward the HMI side.
For the panel-side settings in detail, see setting up Sm@rtServer remote control of an HMI panel over the LAN.
Can I reach the HMI from the internet without a VPN? #
No — Sm@rtServer is a VNC server on the panel's own network, so a client on a different internet connection needs a VPN back into the HMI network; forwarding TCP 5900 from the router would work but hands HMI control to every scanner on the internet.
There is no relay and no discovery service in Sm@rtServer: once the VPN is up, the client behaves exactly as it did on the LAN — same panel IP, same password. For a site with no fixed public address, remote HMI access with dynamic DNS and a VPN is the established pattern.
Port forwarding is the shortcut you refuse: that mapping puts live control of a running machine one password away from the entire internet — do not do it on a plant network. When several people only need to watch rather than operate, a read-only web client mirror of an HMI screen gives them the view without handing out VNC control. You also cannot sidestep networking with a cable, because the KTP900 Basic has no supported external display output — see why the KTP900 Basic has no external display option.
In what order should I test the connection? #
Test firmware, then the local subnet, then the VPN — in that order — because a remote-path fault hides a panel-side fault, and every step below changes exactly one condition before you move on.
- Read the firmware the connected panel reports and compare it with the project's device version; if the panel is below V17, update it, redownload the project, and read the version back.
- Confirm Sm@rtServer is enabled in the downloaded project and shows as active on the panel, with its password set in both places.
- From a PC on the panel's own subnet, connect using the panel IP and the Sm@rtServer password. Success here proves firmware, license state, service enablement and credentials in one shot.
- Bring the client in over the VPN and repeat step 3 with the same address; success proves the route and nothing else changed.
- If step 3 fails, stop: the fault is panel-side (firmware, service, password) or a local firewall — do not start wide-area troubleshooting.
- If step 3 works and step 4 fails, the fault is VPN routing or access rules; fix it there and leave the HMI alone.
Why does the session connect and then stop responding? #
A session that opens and then stops responding is a different fault from a refused connection: this is the known Sm@rtServer limitation on KTP panels, so stop chasing licenses and firmware and treat it as a service-stability problem.
A refused connection and a dying session have different fixes. If the client connects, the screen appears, and the service then stops responding on KTP hardware, license and firmware work will not help you — read known limitation where Sm@rtServer stops on KTP panels and follow its conditions and recovery steps before repeating any of the work above.
Questions asked
Do I need any licensing action at all once the project is V17 or newer?
No. From WinCC V17 the Basic Panel 2nd Generation needs no purchased Sm@rtServer license: nothing to order, nothing to transfer, nothing to type. The only licensing-adjacent action is bringing the panel firmware to the V17 level; after that, any failure left is a password, a service setting or a network path.
Why does the Load preview dialog still mention a license on a V17 project?
Siemens documents this note on Basic Panels from V17 onward even though no license is required, so treat it as informational. The check that settles it: read the firmware back from the panel and confirm the V17 level. If the panel reports V17 and the project is V17 or newer, ignore the note completely — there is no key behind it.
Is forwarding port 5900 on the router an acceptable shortcut instead of a VPN?
No. Sm@rtServer is VNC-based and listens on TCP 5900, and forwarding that port from the plant router does make the panel reachable from anywhere — which is exactly the problem, since it publishes live control of the HMI to every scanner on the internet with only the service password in the way. Keep 5900 on the LAN and bring remote clients in over a VPN.
Can I connect using the panel's hostname instead of its IP address?
Use the IP address. The client does not discover panels by name across networks, and a hostname that resolves on your engineering PC often fails on the phone app. Read the address from the panel's own settings or the device configuration in TIA Portal, then confirm the client is on the same subnet or has a VPN route to it.
Is there a way to show the KTP900 Basic screen on a larger local display instead?
Not by cable: this Basic panel has no supported external display output, which is precisely why Sm@rtServer exists in its toolset. Run the client on any PC in the panel's subnet and you get a live, touch-capable mirror of the HMI screen — the same session, without any wide-area network in the path.