Re: 2003 server built in dos prevention??

thanks for the suggestion on the other group... anyone in .networking have
any ideas for my problem below?

"Steven L Umbach" <(E-Mail Removed)> wrote in message
news:u$(E-Mail Removed)...
> Offhand I don't know what is happening and you may also want to post in
> the server.networking newsgroup but I did find the link below which may be
> of help including registry entries that you can modify to change settings.
> Also always look in the application/system logs after a problem occurs for
> any hints and enable auditing of system events in Local Security Policy
> [secpol.msc] that may then enable more system type events to be
> rded. --- Steve
>
> http://www.microsoft.com/technet/pro...g/tcpip03.mspx
>
> "Dave" <(E-Mail Removed)> wrote in message
> news:eEV%(E-Mail Removed)...
>> any comments???? just had it do this again when recovering from a drop
>> of the isdn line.
>>
>> "Dave" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> The situation is this, i have a telnet chat server that can have 100+
>>> active connections during peak times. It is occasionally necessary to
>>> take this down for various reasons. When restarting the server the
>>> clients are automatically trying to reconnect before the port is opened
>>> by the server for up to a minute or so as the server goes through some
>>> initialization stuff.... in w2k pro the os was crippled so if there were
>>> 5 connect attempts outstanding after the port was opened the port would
>>> be disabled... the server os doesn't do this, but it still on occasion
>>> seems to lock out the port. is there some other, maybe anti-dos,
>>> protection that could be triggered by a large number of port connection
>>> attempts in a short period?? if so, can it be disabled or made less
>>> sensitive??
>>>
>>
>>
>
>




Dave