Tutorial: Web2go
You can access a network component and / or its web interface via Web2go.
The following protocols are available for this purpose:
| Type | Example of application |
|---|---|
| HTTP Hypertext Transfer Protocol |
Unencrypted transfer protocol for web browsers. Default port 80 |
| HTTPS Hypertext Transfer Protocol Secure |
Encrypted transfer protocol for web browsers. Default port 443 |
| RDP Remote Desktop Protocol |
Display and control of the screen content of a remote Windows computer. To be able to connect to a PC using RDP you might need to enable |
| SSH (Secure Shell) Secure File Transver Protocol |
Encrypted data transfer between client and server. Default port 22 |
| TELNET | Unencrypted data transfer between client and server. Default port 23 |
| VNC | Display and control of the screen content of a remote HMI (Touch panel). Default port 5900 |
Notice
If you want to access a Windows PC via RDP or VNC, you may need to log in to the remote Windows. But with the key combination Ctrl + Alt + Del you block the local computer.
In the RDP / VNC window you can call up an options menu with the key combination Alt + Ctrl + Shift. There you can display an on-screen keyboard that allows you to type keyboard shortcuts that would otherwise produce undesirable results (such as Ctrl + Alt + Del).
Notice
Any number of Web2go connections can be created or configured. However, only one connection can be established per Web2go license.
For X licenses, X connections can be established at the same time, or X users can simultaneously connect to the same Web interface.
Information and details about your current license, see "System> In Use / Licenses".
For more information on the portal licenses, please contact your sales partner.
1. VNC/RDP via Web2go and Direct link
2. Web interface access via Web2go
1. VNC/RDP via Web2go and Direct link
This video shows how-to establish a VNC/RDP connection via Web2Go and Direct link.
2. Web interface access via Web2go
This video shows how-to access the mbNET Web interface via Web2go.
3. HTML display error
We are often asked why there are display errors when accessing a network component and/or its web interface via Web2go using HTTP/HTTPS protocols but not with the VNC protocol. In the following, a panel PC is used to illustrate how the corresponding protocols perform the access on the technical level.
Web2Go access via HTTP / HTTPS protocol
Please note that the Panel PC LAN IP address is within the visibility range of the router but not the PLC plant network IP address, which can be reached only by the Panel PC.
The core problem in such cases is that in the first step of such HTTP/HTTPS protocol accesses the HTML file is transferred unrendered and after its transfer the PLC IP address at the new destination is no longer accessible during the final HTML rendering process and thus this associated reference can no longer be resolved for the browser.
=> Display error
Therefore this is a network and browser rendering problem and not a Web2Go problem!
Web2Go access via VNC protocol
Such display errors do not occur via the VNC protocol, because the screen content is first rendered on the panel PC and then a transfer takes place.
4. Troubleshooting
- How can I login to a locked Windows-PC via VNC / RDP?
- Why does my Web2Go connection to a Windows 10 PC fail?
| Revision: V1.2 |
|---|