Editing Talk:Network Configuration
From FileZilla Wiki
Jump to navigationJump to searchWarning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 61: | Line 61: | ||
I just finished troubleshooting a problem I had with my FileZilla server setup and I want to share so that the wiki can be improved. My setup was a GNU/Linux computer hosting VirtualBox with a completely updated (5/4/2013) Windows XP Pro SP3 computer as a guest. VirtualBox was setup to provide NAT between the Linux host and a private IP space for the XP guest. Additionally, I configured the VirtualBox NAT to forward port 1343 and 5000 on the loopback interface (127.0.0.1) of the host to port 21 and 5000 respectively on the guest side. FileZilla server 0.9.41 was installed on the XP guest, and instructed to provide 127.0.0.1:5000 as the external address for passive connections. As such, I was able to establish a FTP command connection from Linux (directed to 127.0.0.1 port 1343). However, when my FTP client on Linux issued the PASV command (while attempting to get a directory contents list from the server), it would get a 227 response from FileZilla server with the internal IP of the XP guest, and stall. Strangely however, the FileZilla server interface would report that the server sent the correct external address in the 227 response (127.0.0.1 as specified in this case, though I tried others). Using Wireshark concurrently on both sides of the VirtualBox NAT, I could see that indeed, the internal address of the XP guest was sent and received in the 227 response, despite what the FileZilla server interface reported. According to this wiki page, my Windows Firewall had the proper exceptions setup, but I disabled the firewall nonetheless, and voila, the specified address was sent. Then, after seeing Windows Application Layer Gateway (ALG) alluded to in this wiki, I disabled ALG, re-enabled Windows Firewall, and the 227 response remained as desired (a restart may be required). Thus, my conclusion is that Windows Application Layer Gateway (ALG) modifies the 227 response, interfering with the establishment of the secondary FTP connection. I write all this here, because (IMO) this issue with Windows Firewall and ALG is somewhat cryptically and incompletely addressed on this wiki page. If someone with edit permissions can adequately address this on the wiki page, I imagine it would help many people. Cheers. | I just finished troubleshooting a problem I had with my FileZilla server setup and I want to share so that the wiki can be improved. My setup was a GNU/Linux computer hosting VirtualBox with a completely updated (5/4/2013) Windows XP Pro SP3 computer as a guest. VirtualBox was setup to provide NAT between the Linux host and a private IP space for the XP guest. Additionally, I configured the VirtualBox NAT to forward port 1343 and 5000 on the loopback interface (127.0.0.1) of the host to port 21 and 5000 respectively on the guest side. FileZilla server 0.9.41 was installed on the XP guest, and instructed to provide 127.0.0.1:5000 as the external address for passive connections. As such, I was able to establish a FTP command connection from Linux (directed to 127.0.0.1 port 1343). However, when my FTP client on Linux issued the PASV command (while attempting to get a directory contents list from the server), it would get a 227 response from FileZilla server with the internal IP of the XP guest, and stall. Strangely however, the FileZilla server interface would report that the server sent the correct external address in the 227 response (127.0.0.1 as specified in this case, though I tried others). Using Wireshark concurrently on both sides of the VirtualBox NAT, I could see that indeed, the internal address of the XP guest was sent and received in the 227 response, despite what the FileZilla server interface reported. According to this wiki page, my Windows Firewall had the proper exceptions setup, but I disabled the firewall nonetheless, and voila, the specified address was sent. Then, after seeing Windows Application Layer Gateway (ALG) alluded to in this wiki, I disabled ALG, re-enabled Windows Firewall, and the 227 response remained as desired (a restart may be required). Thus, my conclusion is that Windows Application Layer Gateway (ALG) modifies the 227 response, interfering with the establishment of the secondary FTP connection. I write all this here, because (IMO) this issue with Windows Firewall and ALG is somewhat cryptically and incompletely addressed on this wiki page. If someone with edit permissions can adequately address this on the wiki page, I imagine it would help many people. Cheers. | ||
− | == | + | == Не удается подключиться к серверу == How do I get ФЗ подключиться к серверу? Помогите, пожалуйста, есть ли способ, чтобы просто синхронизировать сайт на мой ноутбук и веб-сайт в интернете одним нажатием на кнопку upload ? каждый раз я должен искать в каждой карты, если есть что-то в зеленый цвет и чем затем перетащите его. Часто я забыл изменил карту под другую карту, так есть и ошибки на сайте |
− | |||
− | How do I get | ||
− | |||
− | |||
− | |||
− | |||
:( | :( |