canabeez schreef:wel wel, meneer weet-alles-beter weet het ineens niet meer
canabeez schreef:Lang leve de herinstallaties
r2504 schreef:
Ik heb er geen probleem mee om te vertellen dat ik fouten maak, en niet alles weet... anderen hier hebben echter wel vaak ooglappen op, daar zit het verschil.
r2504 schreef:Vrees er voor... zelfs XP erover installeren wil hij niet omdat SP2 erop staat (al kan ik er dat eerst wel afgooien, maar dan doe ik liever een scratch install).
canabeez schreef:Ik ben blij dat je zo wijs bent.. Maar ik zal je 1 ding zeggen,
zo kom je niet over bij mij..
r2504 schreef:
Bedankt voor je prachtige bijdrage op dit forum... trouwens wat jij denkt over mij is het laatste van mijn zorgen.
Als je enig verstand had had je misschien kunnen suggereren om een netsh int ip reset te doen... maar dat werkt dus ook niet. (maar misschien is de andere persoon in deze thread er iets mee.
canabeez schreef:1 woord mijn vriend: HAHA
r2504 schreef:canabeez schreef:1 woord mijn vriend: HAHA
Jezus man, wat ben jij zielig
Das neue Service Pack 2 für das Betriebssystem Windows XP wurde letzte Woche veröffentlicht. Neben diversen gestopften Sicherheitslücken hat Microsoft auch die Verbindung gedrosselt. Filesharing und ähnliche Anwendungen werden dadurch merklich eingeschränkt. Wichtigster Punkt beim System-Update: Sicherheit. Offiziell soll es Viren und Würmern erschwert werden, sich schnell über Rechner zu verteilen. Deshalb wurden die offenen TCP/IP-Verbindungen reduziert. Neben den Viren werden aber auch Filesharing-Programme beeinträchtigt. P2P-Programme wie eMule und Kazaa Lite nutzen mehrere simultane Verbindungen um Downloads von zu laden. Weniger gleichzeitige Verbindungen, bedeutet weniger Download-Speed.
So long, and thanks for all the fish 
So long, and thanks for all the fish TcpNumConnections
Key: Tcpip\Parameters
Value Type: REG_DWORD - Number
Valid Range: 0 - 0xfffffe
Default: 0xfffffe
Description: This parameter limits the maximum number of connections that TCP can have open at the same time.
First, open the Registry Editor and search the following string:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters"
Then add a new DWORD-value in the right window named "TcpNumConnections"
Then click it right->change and put a Hex-Value "fffffe" in it.
That changes the maximum TCP/IP-Connections to 16.777.214 . This is only needed at SP2.
So long, and thanks for all the fish °MaRtO°° schreef:Just take the patch!
http://www.lvllord.de/?lang=en&url=downloads
So long, and thanks for all the fish
So long, and thanks for all the fish 
Kwabber schreef:Kheb ook ne keer SP2 derop gezwierd met als resultaat dat mijn pc bleef hangen bij het bootscherm. Resultaat: opnieuw Windows mogen installen.
Les voor mij: installeer SP2 nooit meer
So long, and thanks for all the fish Hey guys, i just wanted to point something out. SP2's TCPIP.SYS limits the maximum half-open connections made PER SECOND. So yes, you can have 400 connections open in EMule, and yes BT programs let you have 100 or more connections per torrent or 1000 globally by default. That's the number of concurrent (total) connections you can have and that is the number that is controlled by the registry key on the first page of the post. These numbers are not related in any way.
A half-open connection means a connection that is open on your end but doesn't nessessarily have to be connected by another peer, so like opening a listening port that has nothing coming in yet, or requesting a connection to another machine but not established yet. Anyways, you get 10 of these per second under SP2. That's admittedly pretty low for BT or any p2p sharing prog where you can connect to say 200 people within a couple seconds time. But, what happens when you manage to hit this limit for whatever reason is the TCP/IP stack goes into a flood control kind of mode, and queues pending connections and processes them at the rate set by Max Connects per Second (ie. 10, or 50 if you've patched).
Now, if you consider that for a second (or 10 connections), it's pretty rare that any application you're running needs to establish a huge amount of connections for any considerable length of time. Usually it's a burst of connection activity - when you start a torrent or download a whatever you crazy eMule people call it - and once they're established there's a pretty big dropoff. So, basically the only way this setting is even affecting you is it takes a few more seconds than usual to establish connections when there's a lot of TCP/IP activity.
That's it.
In fact, in Azureus there's a feature, "Slowly connect new peers", and it does the exact same thing as this TCP/IP stack change does, altho i'm not sure of the rate. This isn't unique to Azureus, it's a concept that's been around for a long time - look at mIRC flood control, it's the same thing. The point is, because mass-opening connections is an effective way to make an OS scream like a little girl, many programs that have the ability to do so already have built-in traffic control you've just never noticed.
Seriously, the only thing that will be hindered by this change is software that opens a very large amount of new connections in a very short amount of time, for a very long amount of time. i think that made sense. you get what i mean. other than port scanners and malware/worms, i can't think of anything else that would require more than 10 (or 50) connections per second for any reasonably large period of time. (there very well may be legit programs that do, i just can't think of any).
Sorry bout the long post. One of my biggest annoyances is misinformation. Thanks for your time and please try to spread the word.
So long, and thanks for all the fish 
