Ankündigung

Einklappen
Keine Ankündigung bisher.

- √ - Urgent: Problem with distant FTP transfert from Gira HomeServer 3, Expert 2.8

Einklappen
X
 
  • Filter
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge

  • kokoriko187
    antwortet
    Guys, my problem is resolved.
    Now the FTP work with my Domaine Name (dyndns).

    I think the domain name (dyndns) took time before being functional.
    I have not done anything more since this morning.

    Thank you all and best regards!

    Einen Kommentar schreiben:


  • kokoriko187
    antwortet
    The DNS Server is OK. It's my router, and the second DNS is my provider.
    I can access to the distant homeserver by internet. That's not the problem.


    The problem is:

    In Expert 2.8:
    Project ==> Network ==> FTP ==> Address of FTP Server:

    If I specify a DOMAINE NAME (DynDNS): xy.dyndns.org - NOT WORK
    xy.dyndns.org = 60.206.10.XX

    and I have an error in DNS ==> Server Err

    Server Err: xy.dyndns.org

    ---------------------------

    Else

    In Expert 2.8:
    Project ==> Network ==> FTP ==> Address of FTP Server:


    If I specify the IP Address: 60.206.10.XX - WORK FINE

    I use the dyndns.org (domaine name) because I don't want to pay for a static IP address.

    Einen Kommentar schreiben:


  • Gaston
    antwortet
    Compare the DNS used by your pc (comand: ipconfig) with the one configured in the Homeserver (Ethernet section of th edebug page).

    Usually it is your router that is best suited to be the DNS server for your internal devices.

    Cheers,
    Gaston

    Einen Kommentar schreiben:


  • kokoriko187
    antwortet
    I don't understand why the NameServer work for FTP Client and browsers (IE9, and Mozilla Firefox)?

    FTP network:

    QNAP TS 559 Pro II (FTP Server)
    IP: 192.168.1.34

    Router
    Local IP: 192.168.1.1
    Public IP: 62.20x.x.x

    NAT port 20-21 to my QNAP (FTP Server)

    DynDNS:
    xxx.dyndns.org to 62.20x.x.x
    Automatic check (if Public IP change)

    --------------------------------------------------------

    HomeServers network (in another city):
    Gira HomeServer 3, Expert 2.8
    IP: 192.168.1.12

    Router
    Local IP: 192.168.1.1
    Public IP: 195.18x.x.x

    Einen Kommentar schreiben:


  • Michel
    antwortet
    Obviously you have an Nameserver problem.

    In this case you should check the Entries for the Nameserver in the Experte or try an other Nameserver, e.g. your router.
    Try to use the same DNS-Entry as in your working machine´s network setup.

    This should do the job.

    Einen Kommentar schreiben:


  • kokoriko187
    antwortet
    Sorry Michel!

    Gaston, please find the DNS debug in attachement.

    IP: OK
    DNS: Error

    Best Regards.
    Angehängte Dateien

    Einen Kommentar schreiben:


  • Michel
    antwortet
    Please do not use the "quote" / "zitieren" - Button all the time, especially not with quotes of the entire last post.
    Fullquotes makes it more difficult to read.

    Thank you!

    Einen Kommentar schreiben:


  • Gaston
    antwortet
    Zitat von kokoriko187 Beitrag anzeigen
    Hello,

    I just found the problem. Thank you guys.

    If I use the Public IP Address (of the provider), no problem. The archive arrive on my FTP Server.
    What does the DNS Debug section read on the homeserver ?

    Einen Kommentar schreiben:


  • kokoriko187
    antwortet
    [WARNUNG]FULLQUOTE DELETED[/WARNUNG]

    Hello,

    I just found the problem. Thank you guys.

    If I use the Public IP Address (of the provider), no problem. The archive arrive on my FTP Server.

    If I use the DNS: xxx.dyndns.org, the FTP server was not found.

    I don't understand the problem, because the dyndns.org work with FTP Clients. Does someone have a solution for that?

    PS: it's not urgent now, I have the alternative solution

    Best regards!

    Einen Kommentar schreiben:


  • Gaston
    antwortet
    Zitat von kokoriko187 Beitrag anzeigen
    The firewall of my router is disabled.
    Firewalling cannot be really disabled with ipv4 NAT routers as some parts are just implicit from the NAT functionality, and in thi sparticular case the part that woul dimpact active FTP connections.

    Which type of router do you have ?

    Cheers,
    Gaston

    Einen Kommentar schreiben:


  • kokoriko187
    antwortet
    [WARNUNG]FULLQUOTE DELETED[/WARNUNG]
    Hello,

    Thank you for you answer.

    I can't see FTP Logs on my FTP Server (it's a QNAP TS-559 Pro II and I don't have the FTP logs).

    Does someone have a FTP Server to test the upload of my archive (to be sure thats not a problem of my FTP/path)?

    The firewall of my router is disabled.

    Thank you so much, and have a nice day!

    Einen Kommentar schreiben:


  • Gaston
    antwortet
    I sth econfiguraton shown the one that has been loaded to the HS ? This appears like a firewall problem usualy seen in active FTP mode, but passice is checked here so no port redirects are necessary.

    Do you have access to the FTP server log on the remote server ?

    If your router is a Fritz!Box you may be able to capture the communication for diagnosing.

    Cheers,
    Gaston

    Einen Kommentar schreiben:


  • Michel
    antwortet
    As it is an outgoing connection FROM the Homeserver, there is no reason to redirect any ports to the HS.

    But you should see any errors then on your FTP-Server.

    Einen Kommentar schreiben:


  • kokoriko187
    antwortet
    Hello,

    Thank you for you answer.

    The path is correct, because the FTP work fine in local (192.168.1.x).

    I can reach my FTP server xxx.dyndns.org using an FTP Client (Filezilla, FTP Expert), without problems.

    I tried upload the file on another FTP server (on my website: itconseil.ch), and the problem is the same.

    Do you think I have to redirect the port 20-21 (used by FTP protocol) on my router, to the HomeServer 3?

    Best regards..

    Einen Kommentar schreiben:


  • Michel
    antwortet
    It seems that a timeout occurs. Transfer ended after ~ 40 seconds.
    Please recheck that the path is definitely correct.

    Maybe the IP-Adress stored at dyndns is not correct. Recheck this too.

    Einen Kommentar schreiben:

Lädt...
X