Video Screencast Help
Search Video Help Close Back
to help

Wireless start drop and connect every few second after SEP install

Created: 24 Oct 2007 | Updated: 21 May 2010 | 15 comments
jian an lim's picture
0 0 Votes
Login to vote
I just install the SEP (unmanage mode) to a laptop for testing. However, it start to drop the wireless every few second and reconnect again.
 
I disabled the Network Threat Protection and the wireless started to work again. I checked the Traffic log and found that protocol Ethernet has been blocked
 
24/10/2007 3:07:56 PM Blocked 10 Incoming ETHERNET 0.0.0.0 00-13-CE-AF-F9-7C 0 0.0.0.0 00-16-B6-51-10-2E 0  jianan.lim INVIZAGE Default 1 24/10/2007 3:07:15 PM 24/10/2007 3:07:15 PM Block_all 
 
I have no idea what kind of protocol is this as I cant find what protocol number is a ETHERNET would be.
 
 
 
If any one can tell me how to configure the firewall rules to allow the above connection that will be great.
 
Jian
Discussion Filed Under:

Comments 15 CommentsJump to latest comment

ekwang's picture

Hello Jian,

I'll take a stab at this as I was having a similar problem, albeit with a desktop computer using a Belkin USB Wireless adapter. I initially had SSC 3.1 installed and installed SEP directly over the existing SSC deployment. Upon restarting the desktop, there were numerous wireless problems much like the ones you describe: My wireless connection would keep restarting, and each time it restarted, it would try and obtain an IP address. I uninstalled SEP, rebooted, and then re-installed SEP. After doing that, all other previous problems seemed to go away, such as problems printing to a wirelessly connected network printer and problems with sending outbound Internet email from Outlook 2003. As an additional item, I could not resolve the wireless problem. As a last resort, I also did a power cycle on my wireless router and sure enough, that solved that problem.

So, it is possible that it might not be SEP but that your wireless router needs to be power cycled. At the very least, it removes a variable from the list of possible suspects and helps to narrow down the cause to something related to SEP.

Hope this helps.
Eric

0
Login to vote
  • Actions
Nixus's picture

Hello Jian.

I have the same problem, just wantet to check if you've reached a sollution to the problem yet?

Regards Thomas.

0
Login to vote
  • Actions
jian an lim's picture
I still cannot find out a way even the above method, it is not helpful.
 
I only find it happen with linksys wireless, but not with cisco wireless.
 
 
how about yours?
 
what kind of wireless router you using?
0
Login to vote
  • Actions
Nixus's picture

No, that method does not apply to us.. it's a known bug in SEP.

http://service1.symantec.com/support/ent-security....

Regarding AP/Router, i have one Linksys WRT54G and one Linksys WRT350N v2.

Same problem on both.

I just hope that Symantec adresses this issue fast.

0
Login to vote
  • Actions
jian an lim's picture
I try to switch it to WEP and it is not working as well.
 
probably symantec have to look into thier whole NT protection on all wireless solutions
 
 
Just pray hard for symantec to fix ASAP.
 
 
0
Login to vote
  • Actions
Carsten Hoffmann's picture
Hi
 
 
This does not effect all Wireless connections (mine is working fine with WPA2 at home). Are you using WPA?
Carsten
0
Login to vote
  • Actions
Nixus's picture

Ick, i was just going to try WEP, thanx for the heads-up.

Maybe we should go for no encryption for the time beeing.
with MAC-filtering + local VPN ofcourse.

0
Login to vote
  • Actions
Nixus's picture

Hi Carsten.

Atleast for me, i am using WPA(TKIP) on my WRT54G and WPA2(AES) on my WRT350N.

Do you have any special rules regarding ETHERNET set in your firewall?
(I could not find any way to change the block_all rule and add ETHERNET rules)

My laptop is a Lenovo T60p v2007.

Thomas

0
Login to vote
  • Actions
jian an lim's picture
Hi Nixus,
 
I don't think there is a rule like that. symantec will have to fix this bug
 
anyway, i am trying to read the wpa2 on windows xp sp2 and we need to install a hotfix to make it work!
 
 
I am gonna test it and see how it goes
 
thanks for updating Carsten
0
Login to vote
  • Actions
Nixus's picture

Ok, keep me/us posted.

I hope for positive results.

0
Login to vote
  • Actions
Carsten Hoffmann's picture
Hi All,
 
yes this is something that Symantec has to fix. One thing you should keep in mind if you disable/uninstall Network Threat Protection (Firewall) is that the Windows Firewall is disabled when you install SEP with the Firewall.
 
While the Windows Firewall is far from beeing perfect it is better then no firewall at all. So please turn back on if you have to uninstall the SEP Firewall component for some reason.
 
Carsten
0
Login to vote
  • Actions
Nixus's picture

Hi.

Just wondering if that patch did anything positive in regard of wireless?

Thomas

0
Login to vote
  • Actions
JimW's picture
Two questions.
 
Does this problem still occur if you use an unmanaged client package generated from the SEPM console? Does it occur if you use a managed client in client control mode?
 
Jim

Jim Waggoner Director Product Management, Symantec Endpoint Protection, Enterprise Security Group, Symantec

0
Login to vote
  • Actions
jian an lim's picture
I am installing an unmanaged client directly from the CD1
hope this does help.
0
Login to vote
  • Actions
JimW's picture
Thank you.
 
Yes this issue is being worked on by the engineering team, but in the mean time, the work-around is to install an unmanaged/stand-alone client package that has been exported from the SEPM console or a managed client package set to be in client control mode. Let me know if this helps.
 
Regards,
 
JimW

Jim Waggoner Director Product Management, Symantec Endpoint Protection, Enterprise Security Group, Symantec

0
Login to vote
  • Actions