Difference between revisions of "Talk:Network Configuration"

From FileZilla Wiki
Jump to navigationJump to search
(Revert spam)
Line 1: Line 1:
Jeg har tilføjet afsnittet om, hvordan man opretter FileZilla Server under Vista og Windows Firewall. Jeg er ikke sikker, hvis jeg sætter det på den rigtige sted eller formateret korrekt.
+
I added the section on how to set up FileZilla Server under Vista and Windows Firewall. I'm not sure if I put it in the right place or formatted it correctly.
  
Jeg brugte nogle timer forsøger at finde ud af dette, og jeg har fundet på en masse mennesker har det samme problem. Windows Firewall ikke er let for dig at tilføje FileZilla Server, da det er en tjenesteydelse og ikke en ansøgning, er det kun (som standard) giver dig mulighed for at tilføje interface (som ikke hjælpe med at få folk til at forbinde til din server) . Jeg er ikke sikker på, om disse oplysninger gælder for alle andre version af Windows Firewall, som jeg kun har prøvet det i Vista.
+
I spent a few hours trying to figure this out and I've found that a lot of people have this same problem. Windows Firewall does not easily allow you to add FileZilla Server since it is a service and not an application, it only (by default) gives you the option to add the interface (which doesn't help in getting people to connect to your server). I'm not sure if this information applies to any other version of Windows Firewall as I have only tried it in Vista.
  
-Ashsagoon 2007/10/16
+
-Ashsagoon 10/16/2007
  
: Det ville være langt lettere at netop forhindre den ubrugelig Windows firewall. Alle problemer løst. - [[Bruger: CodeSquid | CodeSquid]] 10:52, 16 oktober 2007 (CEST)
+
:It would be FAR easier to just disable the useless Windows firewall. All problems solved. --[[User:CodeSquid|CodeSquid]] 10:52, 16 October 2007 (CEST)
  
:: Jeg er enig, men der er folk derude, der insisterer på at have det. Også er der folk, der ikke ved ret meget om pc'er og ikke lide det når så dumme ikon popper op og advarer dem om, at det er handicappede og deres pc kan være i fare (dette var mit problem, om nedsættelse af en ftp på en uerfaren brugerens pc). Gør ikke ondt at få instruktioner håber jeg:) - [[Bruger: Ashsagoon | Ashsagoon]] 07:10, 17 oktober 2007 (CEST)
+
::I agree, however there are people out there who insist on having it. Also there are people who don't know much about PCs and don't like it when that stupid icon pops up and warns them that it's disabled and their pc could be in danger (this was my problem, setting up an ftp on an inexperienced user's pc). Doesn't hurt to have the instructions I hope :) --[[User:Ashsagoon|Ashsagoon]] 07:10, 17 October 2007 (CEST)
  
  
"Adgangen til og åbenhed på internettet også tiltrukket ondsindede brugere, der er aktivt udnytter konstruktionsfejl, bugs og manglende erfaring andre brugere. Et velkendt software selskab i Redmond sikkert spillet en rolle i denne" <br>
+
"The availability and openess of the internet also attracted malicious users who are actively exploiting design flaws, bugs and the inexperience of other users. A well known software company located in Redmond certainly played a part in this"<br>
- Hvordan typisk. Jeg er træt af folk bebrejde nogen, og alle sikkerhedsproblemer på Microsoft. Den eneste grund til mere fejl bliver opdaget i Windows, fordi det er målrettet mere. [[Bruger: 203.122.246.191 | 203.122.246.191]] 05:06, 15 February 2008 (CET)
+
- How typical. I'm sick of people blaming any and all security issues on Microsoft. The only reason more flaws are discovered in Windows is because it is targeted more.[[User:203.122.246.191|203.122.246.191]] 05:06, 15 February 2008 (CET)
  
"Det ville være langt lettere at netop forhindre den ubrugelig Windows firewall. Alle problemer løst." <br>
+
"It would be FAR easier to just disable the useless Windows firewall. All problems solved."<br>
-Og igen. Windows firewall er ikke ubrugelig. Der er bedre løsninger derude, men stop beskylde alle dine problemer på Microsoft. [[Bruger: 203.122.246.191 | 203.122.246.191]] 05:06 den 15. februar 2008 (CET)
+
-And again. The Windows firewall is not useless. There are better solutions out there, but stop blaming all your problems on Microsoft.[[User:203.122.246.191|203.122.246.191]] 05:06, 15 February 2008 (CET)
  
-Khammond 2008/11/13
+
-khammond 11/13/2008
  
: Opdateret Windows Firewall Afsnittet spørgsmål afdækket i forbindelse med "Appliation Layer Gateway" og "Routing and Remote Access"-tjenester. Vi løb ind i disse problemer førstehånds og forhindrede den "Application Layer Gateway" service løst vores problemer. Desværre er nogle af os nødt til at bruge Windows firewall, når en hardware firewall er unavailble.
+
:Updated the Windows Firewall section to include issues uncovered regarding the "Appliation Layer Gateway" and "Routing and Remote Access" services. We ran into these problems firsthand and disabling the "Application Layer Gateway" service resolved our problems. Unfortunately some of us need to use the Windows firewall when a hardware firewall is unavailble.
  
Brug af andet end port 990 for implicitte SSL vil ikke fungere. Jeg prøvede det. Filezilla server giver dig mulighed for at ændre denne port, men hvis du gør dig FileZilla kunder vil ikke deres forbindelse. Det WIKI behov for at dække dette, og lad brugerne vide, fordi konsekvenserne er, at det er foranderligt, hvilket den ikke er. Endnu vigtigere, Filezilla klienter hard-kodet for implicitte port 990 og så ville det ikke støtte at sætte den til noget andet alligevel. [[Bruger: Mozkill | Mozkill]] 21:41, 11. maj 2009 (UTC)
+
Using anything other than port 990 for implicit SSL will not work. I tried it. Filezilla server allows you to change this port but if you do you filezilla clients will fail their connect.   The WIKI needs to cover this and let users know because the implication is that it is changeable, which it is not. More importantly, Filezilla clients are hard-coded for implicit port 990 and so wouldnt support setting it to anything else anyway.   [[User:Mozkill|Mozkill]] 21:41, 11 May 2009 (UTC)
  
: Det er forkert, klienten understøtter implicitte FTPS på alle porte. - [[Bruger: CodeSquid | CodeSquid]] 14:08, 13. maj 2009 (UTC)
+
:That's incorrect, the client supports implicit FTPS on all ports. --[[User:CodeSquid|CodeSquid]] 14:08, 13 May 2009 (UTC)
  
Jeg var nødt til at tilføje andre exe uden plads i den.
+
I had to add the other exe without the space in it.
  
Om Windows Vista konfiguration rapporterer jeg mit tilfælde kan hjælpe Filezilla brugere. Den eksterne adgang virkede ikke med de oplysninger om denne wiki, den eneste måde at gøre det virkede var at tilføje portnummer i Windows Firewall undtagelser.
+
About the Windows Vista configuration I report my case may help Filezilla Users. The external access did not work with the information on this wiki; the only way to make it worked was to add the port number in the windows firewall exceptions.
  
[[Bruger: Cypherinfo | Cypherinfo]] 13:03, 22 oktober 2009 (UTC)
+
[[User:Cypherinfo|Cypherinfo]] 13:03, 22 October 2009 (UTC)
  
-Zipwiz 2010/04/12
+
-zipwiz 04/12/2010
  
Hvor er automatisk / manuelt indstillelige "KeepAlive ping" forebyggelse timeouts på lang downloads? Jeg kan kun finde en akademisk og dogmatisk afsnit om servere og firewalls bryde IP RFC'er. Thats fuldstændig ubrugelig, da internettet er realworld og ingen akademisk legeplads. Software som FileZilla bør ikke tage sigte på akademisk fuldstændighed, men om håndtering af, hvad der er tilfældet derude - og derude er mere brudt end kompatible systemer. PLEASE, i det mindste tilføje en mulighed for at oprette en keep-alive ping, og hvis du ønsker, tilføj en stor advarsel dialog, at du bruger denne funktion pauser IP love (som ingen bekymrer sig om ved den måde).
+
Where is the automatic / manually settable "keepalive ping" preventing timeouts on long downloads? I can only find an academic and dogmatic paragraph about servers and firewalls breaking IP RFCs. Thats completely useless, since the internet is realworld and no academic playground. Software like FileZilla should not aim at academic completeness but on dealing with what is the case out there -- and out there are more broken than compliant systems. So, PLEASE, at least add an option to set up a keep-alive ping, and if you want, add a big warning dialogue, that using this feature breaks IP laws (which no one cares about by the way).
  
== KAN ikke forbinde Til server ==
+
== Cannot connect to server ==
  
Hvordan Får jeg FZ på oprette forbindelse Til Serveren?
+
How do I get FZ to connect to server?
  
Venligst hjælp MIG
+
Please help me

Revision as of 19:19, 19 May 2010

I added the section on how to set up FileZilla Server under Vista and Windows Firewall. I'm not sure if I put it in the right place or formatted it correctly.

I spent a few hours trying to figure this out and I've found that a lot of people have this same problem. Windows Firewall does not easily allow you to add FileZilla Server since it is a service and not an application, it only (by default) gives you the option to add the interface (which doesn't help in getting people to connect to your server). I'm not sure if this information applies to any other version of Windows Firewall as I have only tried it in Vista.

-Ashsagoon 10/16/2007

It would be FAR easier to just disable the useless Windows firewall. All problems solved. --CodeSquid 10:52, 16 October 2007 (CEST)
I agree, however there are people out there who insist on having it. Also there are people who don't know much about PCs and don't like it when that stupid icon pops up and warns them that it's disabled and their pc could be in danger (this was my problem, setting up an ftp on an inexperienced user's pc). Doesn't hurt to have the instructions I hope :) --Ashsagoon 07:10, 17 October 2007 (CEST)


"The availability and openess of the internet also attracted malicious users who are actively exploiting design flaws, bugs and the inexperience of other users. A well known software company located in Redmond certainly played a part in this"
- How typical. I'm sick of people blaming any and all security issues on Microsoft. The only reason more flaws are discovered in Windows is because it is targeted more.203.122.246.191 05:06, 15 February 2008 (CET)

"It would be FAR easier to just disable the useless Windows firewall. All problems solved."
-And again. The Windows firewall is not useless. There are better solutions out there, but stop blaming all your problems on Microsoft.203.122.246.191 05:06, 15 February 2008 (CET)

-khammond 11/13/2008

Updated the Windows Firewall section to include issues uncovered regarding the "Appliation Layer Gateway" and "Routing and Remote Access" services. We ran into these problems firsthand and disabling the "Application Layer Gateway" service resolved our problems. Unfortunately some of us need to use the Windows firewall when a hardware firewall is unavailble.

Using anything other than port 990 for implicit SSL will not work. I tried it. Filezilla server allows you to change this port but if you do you filezilla clients will fail their connect. The WIKI needs to cover this and let users know because the implication is that it is changeable, which it is not. More importantly, Filezilla clients are hard-coded for implicit port 990 and so wouldnt support setting it to anything else anyway. Mozkill 21:41, 11 May 2009 (UTC)

That's incorrect, the client supports implicit FTPS on all ports. --CodeSquid 14:08, 13 May 2009 (UTC)

I had to add the other exe without the space in it.

About the Windows Vista configuration I report my case may help Filezilla Users. The external access did not work with the information on this wiki; the only way to make it worked was to add the port number in the windows firewall exceptions.

Cypherinfo 13:03, 22 October 2009 (UTC)

-zipwiz 04/12/2010

Where is the automatic / manually settable "keepalive ping" preventing timeouts on long downloads? I can only find an academic and dogmatic paragraph about servers and firewalls breaking IP RFCs. Thats completely useless, since the internet is realworld and no academic playground. Software like FileZilla should not aim at academic completeness but on dealing with what is the case out there -- and out there are more broken than compliant systems. So, PLEASE, at least add an option to set up a keep-alive ping, and if you want, add a big warning dialogue, that using this feature breaks IP laws (which no one cares about by the way).

Cannot connect to server

How do I get FZ to connect to server?

Please help me