Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Remove picture download limit
- Thread starter kav40
- Start date
Member bkrike suggested the fix. But it has nothing to do with .pic or any other file extensions. The default limit for sessions is the standard, world-wide, for session connections simultaneously to a server.
You can adjust, and hence, abuse the standard. In most cases the server from which you are downloading will not complain. But they can.
Microsoft got this one right. Please be considerate of your sessions if you modify the default limits.
You can adjust, and hence, abuse the standard. In most cases the server from which you are downloading will not complain. But they can.
Microsoft got this one right. Please be considerate of your sessions if you modify the default limits.
bkrike,
This information should be more public, as the suggestion is often made that Microsoft screwed up and this is some secret hack.
The limit was standards based. The workaround is widely published as a MS KB article, or on a thousand or so web sites.
There is a related issue with Service Pack 2 dealing with the ability of the tcp/ip stack to simultaneously oper more than ten connections. This too was not a mistake. It was a deliberate effort under SP2 to limit the ability of a worm to propogate. In this case there is no MS KB or simple registry workaround. You shold know that you can do a workaround if it impacts you:
This also differs from your original issue, in the sense that the SP2 connections are cached and queued, rather than just discarded.
I very much appreciate your post and the sentiments expressed. There are good reasons for the standards requirements for connections to a single site. There are good reasons for the SP2 limitation on rapid tcp/ip connections. How good a net-citizen you decide to be is fundamentally not a choice of Microsoft, but yourself.
Best regards,
Bill Castner
This information should be more public, as the suggestion is often made that Microsoft screwed up and this is some secret hack.
The limit was standards based. The workaround is widely published as a MS KB article, or on a thousand or so web sites.
There is a related issue with Service Pack 2 dealing with the ability of the tcp/ip stack to simultaneously oper more than ten connections. This too was not a mistake. It was a deliberate effort under SP2 to limit the ability of a worm to propogate. In this case there is no MS KB or simple registry workaround. You shold know that you can do a workaround if it impacts you:
This also differs from your original issue, in the sense that the SP2 connections are cached and queued, rather than just discarded.
I very much appreciate your post and the sentiments expressed. There are good reasons for the standards requirements for connections to a single site. There are good reasons for the SP2 limitation on rapid tcp/ip connections. How good a net-citizen you decide to be is fundamentally not a choice of Microsoft, but yourself.
Best regards,
Bill Castner
- Status
Similar threads
- Locked
- Question
- Locked
- Question