WYSE ThinOS Connectivity

Site A has a Citrix array behind a SonicWall router
Site B had the IIS FTP server which fed the INI file to the S10 units

Units outside Site A CANNOT connect to the FTP server or the array consistently. So we moved the WNOS files to Site A to be served locally on a FileZilla FTP server. We are watching connections to the server, however the units are still not consistently getting connected to the FTP or the array.

NOTE: S10 units INSIDE the Site A firewall are working perfectly, every time. There is no rule we see on the firewall that would block FTP or cause intermittent connectivity with VPN traffic (we are allowing "All" to/from the VPN). The only two things that changed in our environment recently are: A few weeks ago we configured LDAP/SSO on our firewalls, so HTTP traffic is being authenticated across the same tunnel. Also, we put a pre-release firmware on the router at Site A to address some other issues. These two changes are the only ones that fit the timeline.

Any thoughts?
Freda Driscoll-SbarDirector of System OperationsAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Freda Driscoll-SbarConnect With a Mentor Director of System OperationsAuthor Commented:
The issue turned out to be a conflict with Sonicwall's SSO option. Once we excluded the WYSE device IP's using a Object Group, packets no longer got dropped and the WYSE devices were able to connect to the FTP server consistently.
0
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
Ftp log shows successful login intermittently and cannot find cle10_... File. Other times, more frequently, Wyse Devices not even attempt to login and Device hangs on 'connecting to file server'
0
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
I'm thinking there may be site /subnet specific dhcp server options needed for Wyse.  Is this the case?
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
I am confirming that our dhcp server at the problematic site is configured as noted here: http://www.freewysemonkeys.com/downloads/DHCP%20%20FTP%20blazer.pdf
0
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
We are seeing this on our FTP server when the WYSE device is brought back to the local subnet of the FTP:

(000277)4/15/2014 9:00:52 AM - (not logged in) (192.168.1.87)> USER anonymous
(000277)4/15/2014 9:00:52 AM - (not logged in) (192.168.1.87)> 331 Password required for anonymous
(000277)4/15/2014 9:00:52 AM - (not logged in) (192.168.1.87)> PASS ***************
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> 230 Logged on
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> TYPE I
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> 200 Type set to I
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> SIZE /wyse/wnos/C10_bios.bin
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> 550 File not found
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> CWD /wyse/wnos/C10_bios.bin
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> 550 CWD failed. "/wyse/wnos/C10_bios.bin": directory not found.
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> PASV
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> 227 Entering Passive Mode (192,168,1,31,235,41)
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> RETR /wyse/wnos/C10_bios.bin
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> 550 File not found
(000277)4/15/2014 9:00:52 AM - anonymous (192.168.1.87)> disconnected.

Open in new window


Interesting enough, the WYSE device successfully boots and connects to our Citrix WI.

However, when this device was at a remote site yesterday it hung on 'connecting to file server...' and gave netboot error.
0
 
Mohammed HamadaSenior IT ConsultantCommented:
I think this might be FTP "Data" range ports on the firewall that's being blocked occasionally.

Maybe for better observation you can use the Wireshark Application in order to capture the errors?
0
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
I ruled out it being a Sonicwall FTP issue since we can successfully connect to FTP using Windows XP CMD from a client at the same site repeatedly without an issue.

A.) Site A same subnet as FTP: no issues with WYSE auth and connecting to FTP server

B.) Site B & C are remote to FTP over Sonicwall VPN tunnel: WYSE devices show connecting to file server...then revert to default ICA settings screen. We see no attempt to login in FTP server (FileZilla) log.

The Sonicwall LAN-to-VPN and VPN-to-LAN access-rules on either side have allow any-any rules; there are no deny rules.

We do not have WYSE tech support options and they have not been helpful in the past.

Please help us resolve this issue.
0
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
Any have an idea why our WYSE devices are not initiating the FTP connection behind our sonicwall's and over our VPN tunnels?

FTP works from from Windows clients...
0
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
Here is a packet capture on the remote sonicwall for the wyse device and it shows dropped ftp control packets:

Ethernet Header
 Ether Type: IP(0x800), Src=[00:80:64:68:12:93], Dst=[00:17:c5:62:4b:ce]
IP Packet Header
 IP Type: TCP(0x6), Src=[192.168.14.32], Dst=[192.168.1.31]
TCP Packet Header
 TCP Flags = [SYN,], Src=[2050], Dst=[21], Checksum=0xb6c1
Application Header
 FTP Control
Value:[0]
DROPPED, Drop Code: 39, Module Id: 26, (Ref.Id: _4703_uyHtJcpfngKrRmv) 0:0)

Open in new window


This is a LAN-to-VPN zone path and the egress rule is any/any allow....

I'm stumped!
0
 
Freda Driscoll-SbarDirector of System OperationsAuthor Commented:
Researched issue and trouble-shoot various options on Sonicwall. The Sonicwall logs also showed SSO failure for the WYSE IP address.
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.