RE: FWS_PNP_IPHELPER_QUITE_PERIOD
- From: v-shjia@xxxxxxxxxxxxxxxxxxxx ("Sherry Jia")
- Date: Fri, 17 Apr 2009 03:24:38 GMT
Hi Ondrej,
Thank you for posting in Partner Online Technical Community. This is
Sherry and I will be assisting you in this post.
Based on my understanding, after a VPN client connects to ISA Server, ISA
Server updates the routing table in the ISA Server driver by using the IP
address of the VPN client. Such updates consume CPU resources. To process
multiple updates in batches, those updates are delayed for 5 seconds.
During this 5-second delay, ISA Server treats all packets that are sent
from the VPN client IP address as spoofed packets. Then the issue
To work around this behavior, use a registry entry to reduce delay. To do
this, follow these steps:
1. Start Notepad.
2. Copy and then paste the following text into Notepad. Windows Registry
Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RAT\Stingray\Debug\FWSRV]
"FWS_PNP_IPHELPER_QUITE_PERIOD"=dword:000005dc
3. Save the text file as KB929343.reg.
4. Locate and then right-click the KB929343.reg file that you saved.
5. Click Merge.
6. Click OK.
Note: The value of the FWS_PNP_IPHELPER_QUITE_PERIOD registry entry
represents the delay in milliseconds of the routing table updates. By
default, this value is 5000 (5 seconds). These workaround steps set the
value to 1500 (1.5 seconds). Do not set too small a value because routing
table updates consume CPU resources. 1.5 seconds should be sufficient for
most scenarios.
Warning: Serious problems might occur if you modify the registry
incorrectly by using Registry Editor or by using another method. These
problems might require that you reinstall the operating system. Microsoft
cannot guarantee that these problems can be solved. Modify the registry at
your own risk.
If you have any question or problem, please do not hesitate to contact us
at your first convenience. We are glad to be of assistance.
Sincerely,
Sherry Jia
Microsoft Partner Online Support
Get Secure! - www.microsoft.com/security
=====================================================
This Partner Online Technical Community is for break-fix and simple how-to
post-sales tech issues. For pre-sales questions, Certified/Gold Certified
Partners can refer to specific pre-sales Partner OTCs.
For any feedback regarding overall Partner Online Technical Community
experience, please kindly post to
1. from the web interface: Partner Feedback
2. from your newsreader: microsoft.private.directaccess.partnerfeedback
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================
.
- Follow-Ups:
- Re: FWS_PNP_IPHELPER_QUITE_PERIOD
- From: Ondrej Sevecek
- Re: FWS_PNP_IPHELPER_QUITE_PERIOD
- From: Phillip Windell
- Re: FWS_PNP_IPHELPER_QUITE_PERIOD
- References:
- FWS_PNP_IPHELPER_QUITE_PERIOD
- From: Ondrej Sevecek
- FWS_PNP_IPHELPER_QUITE_PERIOD
- Prev by Date: Re: monitor bandwidth
- Next by Date: Can't connect to ISA2004 with RDC
- Previous by thread: FWS_PNP_IPHELPER_QUITE_PERIOD
- Next by thread: Re: FWS_PNP_IPHELPER_QUITE_PERIOD
- Index(es):
Relevant Pages
|