Unsolved
This post is more than 5 years old
1 Message
0
6223
May 27th, 2015 07:00
Communicating with NAT'ed Thin Client
Communicating with NAT'ed Thin Client
I have a Z50D at users home behind standard Linksys router. The IP for the thin client is 192.168.x.x, however, my public IP is completely different - 69.196.x.x. When the Thin Client makes contact with WDM, it tells WDM its IP is 192.168.x.x. WDM is unable to communicate with that IP as it's obviously private and not reachable. How can I get WDM to recognize the NAT'ed IP?
No Events found!
Steve Lindsey
6 Posts
0
May 27th, 2015 07:00
Sounds like you & I are in the same boat.
I was able to modify the WDM connection IP on the Wyse client to point to my Public IP (which is then nat'd to my internal Private IP)
the Wyse devices complete check in with no issue, however you will not be able to push files to the Wyse, as then WDM server includes its internal IP for the FTP server in a packet back to the Wyse client to connect to the FTP & download the package. Which obviously fails.
I just opened a similar thread, but will keep an eye on this one in case anyone responds with helpful information
if you need any help setting up your stuff to get to the point where i am, LMK