Discussion Locked

Zonealarm on windows 2000 pro client

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a workstation with zonealarm installed. Workstation uses the internet via lan modem. Network is win2000. I am receiving the following internet alerts from zonealarm. Please tell me what each means and if I should answer yes or no to access internet/server. Thank you.

1. Do you want to allow LSA executable and server dll [export version] to access the local area network. LSASS.EXE
2. CBA - PING DISCOVERY, PDS.EXE

7 replies

by joseph moore

1 - Personally, I do not enable many programs to run as Servers in ZA. So, you don't need it to run.
2 - PDS.EXE is a file for Norton Antivirus. So, it "should" be ok to let that one run.

hope this helps

by b_pope

You should say NO to any app wanting to have server rights. The Rule is "only servers need server rights".

Norton doesn't require server rights even when updating virus definitions. Internet Explorer or any other browser doesn't require server rights in ZA.

The only time I've had to allow server rights is to file sharing programs & even those you can block after the program has fully loaded & connected.

by madmark

Looks like someone or something is trying to login to your system from remote. DENY DENY DENY. If something fails or acts unexpectedly, you can always enable it later. Only allow applications that you KNOW are supposed to be serving to act as servers. That would be darn few on a workstation!

From http://searchwin2000.techtarget.com...x285120,00.html

What is Local Security Authority?

The Local Security Authority or LSA is a key component of the logon process in both
Windows NT and Windows 2000. In Windows 2000, the LSA is responsible for validating
users for both local and remote logons. The LSA also maintains the local security
policy.

During the local (interactive) logon to a machine, a person enters their name and
password to the logon dialog. This information is passed to the LSA, which then calls
the appropriate authentication package. The password is sent in a nonreversible secret
key format using a one-way hash function. The LSA then queries the SAM database for
the user's account information. If the key provided matches the one in the SAM, the
SAM returns the users SID and the SIDs of any groups the user belongs to. The LSA
then uses these SIDs to generate the security access token.

This discussion is closed to new replies.