[MR4] ICMP Response Time
Hi,
I Have upgraded on MR4 clients, before the client have MR3. Currently the icmp response time on local network there is approximatively 16 ms (before with MR3 there is <1ms). Only Prevention intrusion is active (and antivirus / antispyware and truscan).
For example when ping gateway, with mr3 the response time is 1ms. With mr4 the response time is 16ms. When I disable network threat, the response time is 1ms.
But the problem isn't present on all workstation's. On workstation with MR4 and XP SP3 the response time is 1ms.
On workstation with XPSP2 and MR4, the reponse time is 16ms. On another workstation with XPSP2 and MR4, the response time is 1ms.
I have tried to upgrade the network driver but it's same problem.
I have open a call to solve this problem.
Hi
I have the same issue after the upgrade to MR4 on Windows XpSp2.
This is the response times when i Ping the Gateway or any windows machine on the lan:
34ms
1ms
16ms
2ms
16ms
6ms
16ms
2ms
16ms
2ms
16ms
Symantec Techsupport told me that this is normal. I am not really happy with that answer. I have a case open at Symantec Tech Support and want a more technical answer from them.
I was told to move the PING rule at the top of the Fw rules but it did not resolve the problem.
If I configure the PING rule locally on the Client instead, the replies are different:
Reply from 10.xx.x.x: bytes=32 time=41ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=1ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=15ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=16ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=1ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=16ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=1ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=16ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=1ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=16ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=1ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=15ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=15ms TTL=254
Reply from 10.xx.x.x: bytes=32 time=15ms TTL=254
I think the problem is localized on teefer2 driver (IPS). On the MR3 there is no problem the response time is 1ms.
I have called Symantec and it the support can recreate the issue. This is general problem on MR4 or new functionnality.
Because one packet is long and after one packet have correct response time.
the case was escalated on Advanced Team for analysis.
For my company the firewall isn't activated, only IDS is activated. The problem is same on XP SP3.
Hi,
Did you make any progress on resolving this?
I've a server running 2003 SP2 with MR4 installed exhibiting the same behavior.
Neil
Hi,
Case has been escalated on advanced team, a patch will be available soon maybe by liveupdate or in MR4 MP2.
This worked for him.
http://www.sadikhov.com/forum/lofiversion/index.php?t140757.html
Would you like to reply?
Login or Register to post your comment.