Connect relay to server through NAT.
The webNetwork Server is handing back its internal IP Address to the webNetwork Relay when the relay tries to communicate. The relay cannot contact the server on the internal IP address because it is behind the NAT. The Server needs to be configured to pass the DNS name for the RMI Registry.
On the webNetwork Server run the webNetwork Server Management Console (8090 console).
Click on the Settings tab to go to the Settings page.
Enter the DNS name of the webNetwork server with the service port on the Service Port line ( i.e. - wnserver.example-cloud.com:4500 ).
Enter the DNS name of the webNetwork server with the registry port on the Registry Port line ( i.e. - wnserver.example-cloud.com:1099 ).
Click Save at the top of the page.
Click the Shutdown button to shutdown the webNetwork service.
Make sure that on that server that wnserver.example-cloud.com resolves to the physical IP number on that box via dns or host file entry.
Start webNetwork back up.
Next on each of the standalone relay servers do the same thing but use their machine, such as wnrelay1.company.com.
For each of the services, such as Portal Service, Admin Service, DP Service, Data Exchange Server, Report Service, File Service, and pipeline service, put in wnserver.example-cloud.com:1099
Make sure that on that server that wnrelay1.example-cloud.com resolves to the physical IP number on that box via dns or host file entry.
Next make sure that wnserver.example-cloud.com resolves to the proper ip address to get back to the webNetwork server via dns or host file entry.
Click the Shutdown button to shutdown the webNetwork service on the relay.
Start webNetwork back up.
It should now be able to communicate with the webNetwork server over the NAT connection. They key is that DNS names are used so that they exchange dns names and not physical IP numbers.
With webNetwork 6 we have introduced a feature called PUSH which requires that a Relay can talk to a loader and the loaders can talk to the relay. Because of this, the same steps as above need to be completed on each relay also.
Can't find the KB
Unable to find the KB to address your issue ?
Recent Articles
Lenovo Unified Workspace End-of-Life Questions and Answers
Will the shutdown of LUW servers and access to downloads affect my server licensing? No, the shutdown of the customer servers and access to the product and licensing downloads will not affect your server licensing. This license is downloaded and ...
How do I determine my Unified Workspace license expiration date?
The best method for determining the licensing information including the expiration date of your Unified Workspace license: Login to your 8090 management console on each server This may take remoting into each LUW server and relay, opening a browser, ...
Lenovo Unified Workspace 7.0.2.13 Released
Highlights of Unified Workspace 7.0.2.13 Before you install: Please view the installation notes here. 7.0.2.13 requires a 7.0 license file. Below is a list of enhancements and fixes released in Unified Workspace 7.0.2.13 Fixed external storage ...
LanSchool Documentation Guides
LanSchool Classic Teacher Console The LanSchool Teacher Console is the interface teachers will use to manage their classroom and students. It contains all the tools necessary for a teacher to effectively interact with students and create a ...
Lenovo Unified Workspace 7.0.1.41 Released
Highlights of Unified Workspace 7.0.1.41 Before you install: Please view the installation notes here. 7.0.1.41 requires a 7.0 license file. Below is a list of enhancements and fixes for Unified Workspace 7.0.1.41 Updated Log4j Updated Java Updated ...
Related Articles
Configuring Relay Central.
Activate the RELAY CENTRAL SERVICE on the :8090 console on one of the webNetwork servers. This server should be where everyone will agree to copy the files that should be available on the webnetwork relay servers. The ip address requested should be ...
Debug relay startup problems.
1) If you have your loaders clustered, make sure the cluster status is in sync by using the 8090 management console and checking the cluster status. 2) Use the 8090 console on the relay to turn on com.stoneware.client.stonewareclient debug. When the ...
Cannot connect to Terminal Server
I'm using Remote Desktop Connection to connect to my Terminal Server. When opening Remote Desktop Connection, I put in the FQDN (ts.example-cloud.com) in the Computer field, switch to the tab Security in the Remote Desktop Connection (the last tab or ...
Install a new relay / loader
If you already have a working webNetwork system and need to add an additional Relay or Server (loader) then the following information can be used. First, if you did not do your initial install or have never installed webNetwork and do not feel ...
webRDP cannot connect to new Windows 10 workstations / Windows Server 2016 servers
Issue The HTML5 webRDP client will not connect to new Windows 10 workstations, but will connect to Windows 7 or Windows 8 workstations. Possible Errors: Received an error connecting to: <CN_OF_WEBAPP> Solution Clean installations of Windows 10 now ...