XPSP2 will limit your max. connections/sec


Recommended Posts

Writing MS as M$ makes you super cool!

Some people really got problems. Does your dad work at M$ or what. I thought this board had enough class to keep children like you away. If you can?t help the problem stop posting but don`t tell people how they have to write M$.....

BTW for the normal guys: I tried the tcpip.sys from XPSP1 but it didn`t work. I guess they changed another file too.

Think i will email the guy again to get things clear.

Any chance on using tcpip.sys from a previous version to get around this?

Just tried the tcpip.sys from xpsp1a but all it did was rendering the system unbootable.

Booted in safe-mode and restored the tcpip.sys from XPSP2.

Would have been too easy.

So if MS doesn`t fix it i think were really stuck here cause rewriting the tcpip.sys or the ntoskrnl.exe (i think this file is involved too) would be hard without the XP-Sourcecode.

What comes next if they realize that this will not protect nor help spreading blaster or sasser.

AAAH I could imagine they just make WinXP a non-online OS and remove everything from TCPIP to IExplore :wacko:

You all complain you want better security now you get it you compalin again :rolleyes:

Perhaps M$ should just turn off all internet connectivity.... that would be the ultimate security fix!!

No???? why not??? perhaps it would be a bit too restrictive?????

Thats the point, M$ just have no idea........ implementing security changes that can fundamentally effect your internet related activities is not the way to go.

They need to educate people, I have never had a virus in 15 years of computing. With a decent firewall, Virus checker and common sense when browsing and opening email NO ONE should ever get one. :rolleyes:

So I disagree with you, this is not a good attempt and a "security" fix, rather an half a$$ed attempt to stop the proliferation of viruses by restricting connectivity.....rather than educating people. :whistle:

Rimmel?

Perhaps M$ should just turn off all internet connectivity.... that would be the ultimate security fix!!

No???? why not??? perhaps it would be a bit too restrictive?????

Thats the point, M$ just have no idea........ implementing security changes that can fundamentally effect your internet related activities is not the way to go.

They need to educate people, I have never had a virus in 15 years of computing. With a decent firewall, Virus checker and common sense when browsing and opening email NO ONE should ever get one. :rolleyes:

So I disagree with you, this is not a good attempt and a "security" fix, rather an half a$$ed attempt to stop the proliferation of viruses by restricting connectivity.....rather than educating people. :whistle:

Rimmel?

Education is the way.

Say, during the windows xp install - instead of bragging on how windows is so good, they should let the users be aware on firewalls and stuff...

and do a paragraph on network settings, explaining what a firewall is...

or do a window popup that explains how the security of windows can be improved...

I do think that if they had continued developing IE,

if everyone has an antivirus and firewall,

things would be so much different.

Look, guys... this is a GOOD thing. I don't think this is really getting through to you. What this security measure does is put a cap on the number of attempts that can be made to random addresses from your computer by 'corking' the outgoing attempts after a certain number of failures. Why? well it makes sense that if something like sasser is trying to spread by trying to connect to random addresses, there will be a lot of failed attempts because many of the addys it tries to get to won't actually exist.

This is good. And a 'workaround' to dissable this.... is bad. That would mean that if you become infected by some new virus that attempts to do what this security measure tries to slow down, your computer would help the threat spread faster and do more damage than the computer belonging to someone who didn't bother to dissable this security measure. That would just be plain stupid.

And for the record, this has no effect on p2p programs, since p2p clients don't try to connect to random addresses.

Correct me if I'm wrong, guys.

Complete and utter tosh..........

If I wanted to restrict the connection out of my PC's then I would simply do that in my firewall (it has DDOS protection etc). I DO NOT need M$ doing it for me!!!!!

If people were educated properly then they would never get the sasser virus in the first place...... hence this stupid "Security fix" would not be needed.

Consider yourself corrected.

Rimmel?

Notice that it's mainly the people that are literate about computers complaining.

If all people were smart enough to secure their PC's themselves we wouldn't need the 'enhancements' going into Service Pack 2, now would we? However, the "mainstream" user doesn't know that much about computers and probably doesn't want to. Most of them just want a box to turn on, get on the internet, and check their e-mail. They look at their PC the same way they look at their toaster or blender. They expect it to do a few things and care less how it works, so long as it works.

So far as I'm concerned, limiting the amount of "random" outbound TCP connections, within reason, is a good thing as it *will* slow down the spread of worms and virii.

You all complain you want better security now you get it you compalin again :rolleyes:

people want better security that they can change themselves aswell not just something microsoft programs into its operating system so that people cannot turn it off or on, so that certain programs will run at certain times. I think its a good idea just needs to be implemented right

So far as I'm concerned, limiting the amount of "random" outbound TCP connections, within reason, is a good thing as it *will* slow down the spread of worms and virii.

And now the 1000000$ question:

What if i write a worm that doesn?t connects to RANDOM clients but connects to linear IP-ranges ??

Worms spread around like always AND the user has slow connections. So THAT?S a great feature:no:o:

Look, guys... this is a GOOD thing. I don't think this is really getting through to you. What this security measure does is put a cap on the number of attempts that can be made to random addresses from your computer by 'corking' the outgoing attempts after a certain number of failures. Why? well it makes sense that if something like sasser is trying to spread by trying to connect to random addresses, there will be a lot of failed attempts because many of the addys it tries to get to won't actually exist.

This is good. And a 'workaround' to dissable this.... is bad. That would mean that if you become infected by some new virus that attempts to do what this security measure tries to slow down, your computer would help the threat spread faster and do more damage than the computer belonging to someone who didn't bother to dissable this security measure. That would just be plain stupid.

And for the record, this has no effect on p2p programs, since p2p clients don't try to connect to random addresses.

Correct me if I'm wrong, guys.

OOOOHHH, it only corks or limits multi able "failed" attempts. I thought like you couldn't have many things accessing the Net at one time. That's the way it sounded. I don't personally know, because I haven't installed any betas of SP2. thanks for that info.. I sure hope your right.

Some people really got problems. Does your dad work at M$ or what. I thought this board had enough class to keep children like you away. If you can?t help the problem stop posting but don`t tell people how they have to write M$.....

BTW for the normal guys: I tried the tcpip.sys from XPSP1 but it didn`t work. I guess they changed another file too.

Think i will email the guy again to get things clear.

TYPING M$ MAKES ME A COOL KID!!! W00T!3131241

Say, during the windows xp install - instead of bragging on how windows is so good, they should let the users be aware on firewalls and stuff...

and do a paragraph on network settings, explaining what a firewall is...

or do a window popup that explains how the security of windows can be improved...

[RANT]I know. And for AOL they put all the reasons you should use AOL. Why do I need to be convinced IN the installation? I'm already installing it. Why do I need to know WHY I should install?

:rolleyes: Oh well, but I don't see a reason to have why it's good. That's like all those darn AOL ads IN AOL telling you you can get so many hours free. I'm already a member. What's the point in all the ads? [/RANT]

In that case, your options are to do a system restore. uninstall SP2, or reinstall XP and slipstream SP1 :yes:

i think i will wait for a fix for thats, as its not effecting me thats lot really , but i just dont like playing in my internet connection without my premision

Hi there!

There is a fix I created the day before yesterday.

It can be found under

http://mitglied.lycos.de/lvllord

It works with SP2 and SP2-2 and should also work with SP1 (but I don't know, because I have no testing-system).

So, have fun with the download again :-)

LvlLord

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Turbo Pascal was my first real programming experience more than 30 years ago at university. I mostly taught myself from the included examples and help documentation, because the university only taught the basic syntax and philosophy of Pascal, without going deeply into Turbo Pascal’s advanced features. I still remember when I discovered that I could embed assembly language directly into Pascal code, call BIOS functions, manipulate screen memory, use mouse interrupts, and control peripherals from my programs. That opened huge doors for me. Programming back then felt really fun, direct, and close to the machine. What I loved about Pascal was its readability and the almost instant compile time. Turbo Pascal was an amazing environment, but unfortunately Turbo Pascal for Windows 3 did not feel like it fully carried that legacy forward. Later, Delphi got things back on the right track after the messy transition to TP for Windows. Sadly, Delphi suffered from years of uncertainty as it moved from Borland to CodeGear and then to Embarcadero. That instability made many developers lose confidence in it, even though Delphi itself remained a powerful and productive tool. I still work with Delphi from time to time, but I definitely miss the old days of Turbo Pascal.
    • I hope this encodes in to AV1 or AV2 as currently tiktok uses h265 and h264.
    • Qualcomm reportedly in talks to build custom video chips for TikTok parent ByteDance by Karthik Mudaliar Qualcomm is reportedly in advanced discussions to provide custom chip-design services to Chinese tech giant ByteDance, the same company behind TikTok. According to a report from Reuters, Qualcomm could be involved in designing custom silicon tailored for ByteDance's massive data-center workloads. If it goes through, the deal would make ByteDance one of Qualcomm's early anchor customers for its fastly growing custom chip-design division, For years, Qualcomm was the king of making smartphone processors and modems. The company has also been moving into the PC ecosystem and other formats such as on-device AI for Android XR headsets. However, this particular deal is about Qualcomm's custom Application-Specific Integrated Circuits (ASICs). For a platform like TikTok, ByteDance needs hardware that can help it ingest, process, and serve billions of short-form videos daily. Generalised hardware is no longer the most cost-effective and efficient route, which is why ByteDance is trying to develop custom Video Processing Units (VPUs). VPUs designed specifically for ByteDance’s algorithmic needs could drastically reduce data-center power consumption and improve encoding speeds at an unprecedented scale. The underlying tech behind these processors is actually from Qualcomm's recent acquisition of AlphaWave Semi, a high-speed connectivity specialist company. By combining AlphaWave’s high-bandwidth IP with Qualcomm’s architectural expertise, the company could begin mass production by the end of 2026, if the talks go through. All this also comes at a time when U.S.-China tech relations have dwindled. Escalating trade frictions between Washington and Beijing have severely impacted the export of high-end AI chips from U.S. firms like Nvidia, AMD, and Lam Research. Yet, the Qualcomm-ByteDance discussions show that U.S. tech companies are still actively seeking growth avenues and are open to doing business with China, where regulators still permit. Reuters notes that the outcome of this deal could be uncertain, and ByteDance might also seek partners other than Qualcomm. via Reuters | Image via DepositPhotos.com
  • Recent Achievements

    • First Post
      Almohandis earned a badge
      First Post
    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      456
    2. 2
      +Edouard
      164
    3. 3
      PsYcHoKiLLa
      117
    4. 4
      Michael Scrip
      83
    5. 5
      Xenon
      69
  • Tell a friend

    Love Neowin? Tell a friend!