Quote:
|
Originally Posted by iadom
A heads up for anyone using ZoneAlarm that has been updated to version 5.1.
I had not visited grc.com for a long while now, but last night I had nothing better to do , I am well aware of the antipathy towards Mr Gibson and his self promotion, however I was glad that on this instance I ran the Shields Up / Common ports scan. It reported that port 1025 was open. This is the first time any ports had shown open in over 4 years.
A quick look at ZoneAlarm forums and checking the program itself revealed that several people had encountered this problem after the latest update. I am not sure how ( it wasn't me guv) but Generic Host for Win 32 Services had been granted server permissions to the internet as well as the trusted zone, and was keeping port 1025 open.
If like me you use ZoneAlarm without a router and you have not done a check on open ports since the latest ZoneAlarm update it is worthwhile doing so.
In the program control panel in ZoneAlarm, make sure that Generic host for Win 32 Services only has server permissions to the trusted zone and is blocked to the internet.
|
Do you you Windows File Sharing enabled (for some reason, XP does this by default, which IMO is stupid for a home PC)? Just did a
google search and it seems that Windows uses this port either for Windows File Sharing, or for a system called Dcom (communication system for program components). If you run a program called "Dcomcnfg", you can disable dcom, which may release the port.
You should be aware that by stopping dcom or blocking the port, you may stop various programs (including Windows Update and Automatic Updates) working. However, merely blocking it's server rights (as I notice you have done) is OK.