In the past, our networking products have mostly been mentioned as LAN only devices for practical purposes. However, products like the L300 and RX300 are standard networking devices and could be possibly placed on a WAN deployment, however, success in the deployment will depend on planning and implementing. Calculating resources is paramount. here is an article on scaling your server resources
. Once you read through the article, you will become familiar with the term "user workload", which implies a careful estimation on the session's burden on the server. the same applies to the network, which may be the most important part, since the network infrastructure, logic and IT expertise will determine if a WAN deployment is feasible in your current deployment plan.
There are three basic elements that will be at play here and carry significant implications for a WAN or cross subnet deployment:
• Safe transmission of packets from point to point across the WAN (TCP and UDP alike. This may imply specialized switches to protect and propel the packet without loss)
• Have minimal or no latency (specialized infrastructure may be needed to offer quite fast transmission of data)
• Bandwidth allowance (catering the amount of foreseen active sessions and workload)
If you consider that this is something that you have at your disposal, consider these additional points:
• You may need to configure a port forwarding rule for TCP 27605 in order to establish a session and be familiar with the ports and executables needed for our platform to work.
• Video or heavy graphics over WAN will tax your connection beyond what is practical. For the RX300 we have developed vCAST, which will allow the transmission of YouTube videos directly from the source without having to be processed at the server side. Check this out
if you need vCAST for your deployment.
We encourage you to test. Keep in mind that once you pass the line of a common LAN, most troubleshooting and problem solving relies on your local staff, since configurations on hardware, logic and security are implemented by your IT. Yet, you can still further consult our tech support and we will provide you with any information we may currently have in order to guide you in the right direction to get started.
A final word. Sometimes, if the infrastructure is not in place to make a WAN deployment happen, it may be more practical to have local servers do the "talking" across the WAN and have the terminals to a Local LAN NComputing Server. This will avoid the extra expenses, resources and effort associated with the allowances mentioned above.
Article ID: 105