18 December 2008
10:54 AM | Diposkan oleh
AK47
his ones simple:
this is for broad band connections. I didn’t try it on dial up but might work for dial up.
1.make sure your logged on as actually "Administrator". do not log on with any account that just has administrator privileges.
2. start - run - type gpedit.msc
3. expand the "local computer policy" branch
4. expand the "administrative templates" branch
5. expand the "network branch"
6. Highlight the "QoS Packet Scheduler" in left window
7. in right window double click the "limit reservable bandwidth" setting
8. on setting tab check the "enabled" item
9. where it says "Bandwidth limit %" change it to read 0
reboot if you want to but not necessary on some systems your all done. Effect is immediate on some systems. some need re-boot. I have one machine that needs to reboot first, the others didn't. Don't know why this is.
This is more of a "counter what XP does" thing. In other words, XP seems to want to reserve 20% of the bandwidth for its self. Even with QoS disabled, even when this item is disabled. So why not use it to your advantage. To demonstrate the problem with this on stand alone machines start up a big download from a server with an FTP client. Try to find a server that doesn't max out your bandwidth. In this case you want a slow to medium speed server to demonstrate this. Let it run for a couple of minutes to get stable. The start up another download from the same server with another instance of your FTP client. You will notice that the available bandwidth is now being fought over and one of the clients download will be very slow or both will slow down when they should both be using the available bandwidth. Using this "tweak" both clients will have a fair share of the bandwidth and will not fight over the bandwidth.
this is for broad band connections. I didn’t try it on dial up but might work for dial up.
1.make sure your logged on as actually "Administrator". do not log on with any account that just has administrator privileges.
2. start - run - type gpedit.msc
3. expand the "local computer policy" branch
4. expand the "administrative templates" branch
5. expand the "network branch"
6. Highlight the "QoS Packet Scheduler" in left window
7. in right window double click the "limit reservable bandwidth" setting
8. on setting tab check the "enabled" item
9. where it says "Bandwidth limit %" change it to read 0
reboot if you want to but not necessary on some systems your all done. Effect is immediate on some systems. some need re-boot. I have one machine that needs to reboot first, the others didn't. Don't know why this is.
This is more of a "counter what XP does" thing. In other words, XP seems to want to reserve 20% of the bandwidth for its self. Even with QoS disabled, even when this item is disabled. So why not use it to your advantage. To demonstrate the problem with this on stand alone machines start up a big download from a server with an FTP client. Try to find a server that doesn't max out your bandwidth. In this case you want a slow to medium speed server to demonstrate this. Let it run for a couple of minutes to get stable. The start up another download from the same server with another instance of your FTP client. You will notice that the available bandwidth is now being fought over and one of the clients download will be very slow or both will slow down when they should both be using the available bandwidth. Using this "tweak" both clients will have a fair share of the bandwidth and will not fight over the bandwidth.
Subscribe to:
Post Comments (Atom)
0 komentar:
Post a Comment