- This topic is empty.
20. August 2007 at 11:27 #559
So I’ve been working on my thin clicent project and have 1 centralized server – however, I’ve been unable to get my S10’s to read the FTP server across the WAN. Does the FTP server have to be on the same subnet in order for you to be able to read the config? My server IP is 126.96.36.199 but the device is on a 170.94.104.*** subnet at another physical location. I had our vendor watch the routers upon booting up and they never saw any traffic when it attempted to read from the file server. Manual FTP From a prompt works. Everything else works fine on the device as far as manually setting up an ICA/RDP session. Before moving to the remote site, I put in the network settings for the remotesite and ran it in lockdown so it would save it to flash. Now I get No ICA connection icons and pretty much cant do anything with the device because it wont read the config. I’ll probably have to rig up two routers to get the thing unlocked. Any tips? My quick fix is just to create an FTP server @ each site to correct the inital problem, unless I’m missing a setting. Thanks21. August 2007 at 4:54 #10026
No, I run FTP over the WAN all the time with no issues.
I can only suggest that there is a set up issue on the terminal, if you are using the DHCP option tags in the remote site it should be easy to fix as normally it is a simple path issue.
If you have a static IP or a manual setup of the file server path then yes, you will need to manually unlock the unit and look at the system log on the device to see what the issue is. Given you can manually ftp to the server from the remote subnet on a PC its most likely a simple setup issue.
Post back you 162 tag set up and your ftp folder structure,
-TT21. August 2007 at 13:06 #10029
After troubleshooting at that particular site and setting up a FTP server on that site’s LAN there’s defintely a switch/infrastrucre issue. I’m going to try another site today. A lot of the stuff in that particular building is wired up on CAT5 using only 2 pair (10Mb) yeah – dont laugh, it’s the government. 🙄22. August 2007 at 21:00 #10034
And of course, testing at another unit, everything works fine, as it should. I can read the wnos.ini across the WAN correctly. You never know what you get when inmate labor pulls your cat-5 😯22. August 2007 at 21:46 #10035
Hahah, I love it! I bunch of us techies on this site and we all jumped into hard core problem solving not the obvious questions!
Gald you got it going though and thanks for posting back, sounds like a tough environment to deal with!
-TT23. August 2007 at 13:36 #10036
It’s actually one of the best work environments I’ve ever worked in, but of course, I dont actually work in the unit – we have our own office. Most of the units aren’t too bad, we just have to work with construction / maintenance to get wiring/conduit run. Inmate labor isn’t tha bad, but the guys over at construction have no idea how to run cable/fiber etc. We had one run where they ran some cat-5 400+ feet then wondered why it only worked part of the time.8. November 2007 at 14:19 #10698
Well, another update – it appears to be in the router. The sites we have with CISCO 1841’s work fine, the ones with 2611 models do not. Anyone have expereince with this?9. November 2007 at 6:06 #10704
No specifically on that router however check to see if there are any errors on the interfaces of the router. If you get any over runs or discards that’s a good place to start to look,
-TT16. November 2007 at 19:39 #10800
Well, we tried DHCP on the router today and got it to work, but it still wont read the FTP with a static address.. Everything else on the client works fine after the inital “reading system profile” times out.
While using a static they see no traffic on the router interface or IP cache flow. Any ideas?16. November 2007 at 23:00 #10806
Its been a while since you first posted this issue, so just clarify for me.
You said “it works with DHCP on the router”. Now do you mean with the 161 and 162 tag defined in the DHCP server in the router the Wyse device correctly finds the wnos.ini?
Then you say that with a static IP on the wyse terminal it does not?
If this is the case remember the path is different when you manually enter it on the terminal as it only adds /wnos to the path.
Can you post back the exact details of your setup?
-TT26. November 2007 at 15:38 #10870
Here’s the config. We found out that on the 2611 routers, it will work with DHCP (enabled on the router, but we dont use it). The FTP times out when a static address is used.28. November 2007 at 20:07 #10901
It appears increasing the TCP timeout from 1×30 secs to 2×30 secs resolved the issue. I’m going to assume the older routers (2611’s) weren’t processing as fast as the newer (1841’s) ones.
- You must be logged in to reply to this topic.