On 2005-10-04, Max blabbed:
You could search for the executable names on google to find out what owns them specifically then determine if they should be running on your own.
It's better to help yourself than expect help from others.
On 2005-10-04, Max blabbed:
You could search for the executable names on google to find out what owns them specifically then determine if they should be running on your own.
It's better to help yourself than expect help from others.
Could You help me? Is it avrything OK with may open ports? Mayby I can block one... Please explain me it. Thx
alg.exe 1030 LISTEN TCP C:\\WINDOWS\\System32\\alg.exe ccApp.exe 1025 LISTEN TCP C:\\Program Files\\Common Files\\Symantec Shared\\ccApp.exe System 139 LISTEN TCP outpost.exe 803 LISTEN TCP C:\\Program Files\\Agnitum\\Outpost Firewall\\outpost.exe svchost.exe 1900 LISTEN UDP C:\\WINDOWS\\system32\\svchost.exe System 138 LISTEN UDP System 137 LISTEN UDP lsass.exe 4500 LISTEN UDP C:\\WINDOWS\\system32\\lsass.exe svchost.exe 1033 LISTEN UDP C:\\WINDOWS\\system32\\svchost.exe lsass.exe 500 LISTEN UDP C:\\WINDOWS\\system32\\lsass.exe
Could you please post the complete output of netstat -ano ?
Thanx, VB.
Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.