Hello, I am using N.I.S. Recently I went to GRC's web site (http://grc.com/default.htm) to check for security issues, In the past, the PC always came thru with flying colors however, this time it failed telling me that port 1026 is open. GRC does not offer much information on how to fix the problem. I researched symantec site and learned how to find out what is using/listening on a port. By doing the following: Open the Norton Internet Security (NIS) or Personal Firewall (NPF) Statistics window: Start NIS or NPF. Click Options. Click Internet Security (or Personal Firewall). Some users may skip this step. Click View Statistics. The Statistics window appears. Click View. Point to Columns and click One. This will display the various statistics in a single column. Scroll down the window until you see Network Connections. Look under the "Local" column. This displays your computer name and the port or service. Locate the port in question. When you find the port in question, look to the left to the "Executable" column. This will display the executable program that is listening on (using) that port. You should be able to identify the application by that executable. I found MSTASK.exe is using/listening? Port 1026. MSTASK.exe appears to be the task scheduler - is this correct? Anyway I shut down what was running is task scheduler as well as "windows update." MSTASK.exe is still listed in N.I.S. as using/listening port 1026. How do I go about fixing this problem? Can anyone give some advice? Thanks, J.

Have you denied it access in the applications area.

Wow, some times I wonder Yes, I denied it and then checked N.I.S. which stilled showed it, however, I never rechecked it because I didn't think that the problem was resolved. I deleted the rule for MSTASK.exe in N.I.S. it still shows up but everything looks good when I run grc's security check. What is MSTASK.exe do? Thanks J.

look here http://www.google.ca/search?q=MSTASK.exe+&ie=UTF-8&oe=UTF-8&hl=en&btnG=Google+Search&meta=

J. I've got the same problem. I even tried explicitly creating a rule blocking 1026 (TCP and UDP). But GRC is still showing it open. The (very small) good news is that I've read that mstask should only accept comm from localhost (127.0.0.1). Needless to say though, I'm contacting Symantec ASAP. Any help is greatly appreciated!

Sixty7, Have you received a reply from symantec? Did you end up deleting N.I.S. rule for MStask like I did? J.