Connecting Wyse Terminal Emulation over a VPN

Hi,

I have an industrial PC that can be connected to via a Wyse Terminal emulation application. This works fine in the local LAN.

The LAN is linked to another site via a LAN to LAN IPSEC VPN. (Each end is controlled by a ZyXel USG 100.)

From the remote site I can ping the Industrial PC, but the Wyse Terminal emulation software cannot connect. I suspect that the Wyse software is using some form of non-routable protocol, but this is beyond me. I believe that the connection is ove UDP, but I know nothing about this.

Any ideas?

Thanks,

Richard
LVL 1
rpmAsked:
Who is Participating?
 
rpmAuthor Commented:
Problem remains unsolved!
0
 
Robert SaylorSenior DeveloperCommented:
Can you connect through Windows Remote Desktop? Have you tried VNC? I suspect some ports are being blocked.
0
 
rpmAuthor Commented:
I connect many different systems through the VPN including remote desktop with no problem. No ports are blocked through the tunnel.
Only the Wyse Terminal Emulator is a problem.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Robert SaylorSenior DeveloperCommented:
On my iPad and iPhone I use PocketCloud that uses WYSE. Both connect to my VPN with no issues. We are using a Cisco VPN. I am not sure what app you are using for WYSE but in my app it asks me for the RDP port. I am using the default 3389. You mentioned that is open but might want to double check.

To verify if its not the app/WYSE try connecting to a machine in your local network that does not require VPN using WYSE. That might help determine if it's a VPN issue or a WYSE issue.
0
 
Robert SaylorSenior DeveloperCommented:
If the application may or may not work through VPN over WAN you might need to deploy a local PC in the same network then use remote desktop from the remote site to connect to to the PC that should be able to connect to the WYSE. I believe this is the issue and is how most deal with applications that can not be shared over a WAN.
0
 
rpmAuthor Commented:
Problem remains unsolved!
0
 
ESQ-TechCommented:
Experiencing the same thing....  I am suspecting that the terminal needs to authenticate on the "home" network in order to get an IP for that network in order to 'work'.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.