Shareaza

I have noticed that the port keeps changing from the assigned 6436 to a variety of others, and seems to be different each time I check it. When I change it back, Shareaza freezes for a moment, then resumes. What's going on? Why can't I keep it on the port I want?

Have you checked the random port option in the settings?

The random port option checkbox is clear. I have not selected it. This is part of my concern, as I would expect the port to change randomly had this option been selected. FYI I am using Windows 7 Home Premium. I wonder f this may have something to do with it, however I doubt it. I am using the latest Shareaza version as well. Thoughts?

Have you tried uninstalling and installing again?

What version are you using exactly? The latest stable (2.3.5.0) or one of the most recent alpha builds (2.3.5.1 r88xx)?

2.3.5.0

Its ordinary feature when Shareaza tries to select other port in case original is locked by some network application.

I don't know of any other application that would be using that port. I have not tried uninstalling and reinstalling, but will do so now. The port is different almost every time I open the settings, even when I close it and reopen it immediatley after. That seems strange to me

Random guess an anti-virus or firewall software issue making Shareaza lose the port and fail to reacquire it (because the security software still has it).

Why? Some (badly written) security software (SS) does (or did anyway) work by setting itself as a "proxy" between applications and the actual sockets, so the application would get its sockets from the SS and the SS would handle the actual Windows sockets. When something went wrong the application would try to get back its port but it would still be reserved since the SS failed to release it when the application lost it. Or thought it lost it when actually the SS was incompatible. Not saying that is the case here, but curious of how you can exclude it flat out.

Wrong, all security software (including viruses) uses TCP layer drivers and absolutely transparent for client ports. It must be regular application with same port opened which Shareaza tries to use.

Thanks, actually that is only true for software that was designed or re-factored by someone who knows what they are doing within the last decade or so, but I get your point.