NAS FTP Service vs. WIN FTP Service

  • This topic is empty.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #8525
    MFriedlein
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    Hi,

    first – sorry for my bad english – i’m from germany…

    Until now I use an old 2003 Server to deploy the ini files via FTP and this works fine. Because the server will be retired, I try to use the FTP service wich is provided by an NAS device.

    In future I don’t want to activate the IIS on a Win Server for this anymore – also for safety reasons. We use only the INI deployment via FTP. We don`t use WDM, CCM …

    My first test unfortunately not working. When starting the Client I get the messeage: “File Server not found” and “Can not access system profile”.

    I’ve tested the access as anonymous and as user with password – and as admin. I’ve change the file server path in many ways… so far nothing has worked.

    From the Explorer I have access to ftp://ip-Adresse/wyse/wnos/wnos.ini

    Can it be that it is generally not working with an NAS Service – or because the NAS is not in the domain?

    Thanks in advance
    Markus

    #25491
    MFriedlein
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    Hi,

    to shorten my question a bit:

    it is generally possible to use the FTP Service of an NAS device instead of taking a Windows IIS FTP service?

    Thanks Markus

    #25494
    ConfGen
    Keymaster
    • Total Post: 10692
    • Jedi Master
    • ★★★★★★★

    I do not see any reason why this should not work.
    ThinOS is not dependent on IIS ftp.
    You could also try to use http instead of ftp.
    Just make sure that you add http:// as a prefix to the fileserver. If nothing is mentioned, ThinOS will always use ftp.

    CG

    #25501
    MFriedlein
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    ** english text below **

    Hallo ConfGen,

    irgendetwas muss dann aber das Profil blockieren, da ich immer die Fehlermeldung “Can not Access User Profile” bekomme. Den Zugriff über Http habe ich auch schon probiert – dort ist das selbe.

    Das NAS kann ich vom Wyse Client aus anpingen und bekomme auch eine “Antwort”.

    Meine Testumgebung ist eine Fritzbox mit Zyxel NAS. Ich will jetzt noch das ganze mit statischen IPAdressen und ohne DHCP/Router ausprobieren – um diese als Fehlerquelle auszuschließen.

    Aber vielleicht fällt Dir ja vorher noch was ein…

    Gruß Markus

    ** english text **

    Hi,

    then something must block the profile – it always show the error message “Can not access system profile”. I have already tried http for access – same there.

    When I ping the NAS from the client I get an answer.

    I will now test the situation with static IP addresses and without DHCP and router – (only the NAS and one client).

    But maybe someone has another idea?

    Markus

    #25502
    ConfGen
    Keymaster
    • Total Post: 10692
    • Jedi Master
    • ★★★★★★★

    First test would be to connect from a PC via ftp to your ftp server.
    If you can connect and the desired directory is opening, then the first step should be fine.
    Make sure that the directory you are opening by default contains the wnos folder.
    Do not enter /wnos on the client. This is added automatically.
    eg. Fileserver value = FTP-Server-IP
    FTP Server structure= ftproot/wnos

    CG

    #25503
    MFriedlein
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    Short summary:

    I didn’t get the access over FTP * but via HTTP.

    I only had to find out the correct port and specify it –

    then it worked 🙂

    I hope it makes no difference between http and ftp

    Thanks a lot

    * Whatever the reason is…. I try it with the Explorer and any browser and I was able to Access and open the files…

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.