Hello Paul,

The two clients on which I tested this version of SEP are currently unmanaged.

I assume the SEP ruleset for NTP to which you are referring is something that would be configured if the clients were managed?  If so, then I believe my previous answer also answers this question.

Thanks,

Kevan

I don't have a problem with this configuration

HP Laptop

Vista x32 Home premium
Intel PRO/Wireless 3945ABG with latest Intel drivers
SEP11 unmanaged client

Router

Thomson Speedtouch 585iv6
Settings
Interface Type: 802.11g
Actual Speed: 54 Mbps
Channel Selection: Manual
 Channel: 9
Security
Broadcast Network Name: Yes
Allow New Devices: New stations are not allowed
Security Mode: WPA-PSK
WPA-PSK Preshared Key: XXXXXXXX
WPA-PSK Encryption: AES
WPA-PSK Version: WPA2

Maybe the problem is with Windows XP or with the drivers. As a workaround create a firewall rule that allows all protocols, both incoming and outgoing traffic with the routers IP or export a policy from a managed client that contains the Allow EAPOL rule and import it to the unmanaged client with smc -importconfig command.

Message Edited by Tony Wilson on 10-19-2007 12:07 AM

I too am having this isssue.  Windows XP SP2, and any WPA network, I can't connect without first disabling the Symantec Endpoint Security Client.  After I connect to the WPA network, I can turn it back on. I hope a solution is found soon....

I discovered something else today, with the configuration i'm using above. I can connect with the AP, internet works ok but i can't have filesharing between the vista laptop and two XPSp2 desktops.

The client is managed, Allow wireless EAPOL is there, IPv6 is disabled. The firewall ignores the Microsoft Windows Networking settings. Even if you check "Share my files and printers with others on the network", nothing happens. The firewall blocks all traffic from and to XXXXXX.lan desktops and 137,138 and 139 ports.

The only solution is to create a firewall rule that allows traffic for all the Subnet or for the specific IP's and ports including a broadcast address (192.168.1.255).

Two XP desktops can connect fine to each other by just checking the "Share my files and printers with others on the network" option in SEP and without the need to create a firewall rule.

Message Edited by Hans on 10-19-2007 07:04 PM

So what is the solution for people using unmanaged clients? How do we allow EAPOL? Maybe someone could post an XML file with the needed policy so every person in need could import it?

Looks like Symantec is working on this issue as there is now official acknowledgement in the knowledgebase

If the link doesn't work, it's document ID 2007101713294448

Tony,

Any chance you could post the two rules you are talking about. I have only found 1 rule and after adding that, wireless still doesn't work.

The really odd thing is that one of the PCs on the network, that is not part of the domain nor does it have Endpoint installed, can't even see the SSID of the access point. And this only became an issue after Endpoint was installed.

Ken

Message Edited by zeek on 10-31-2007 09:08 AM