I recently moved from Windows XP Home to XP Professional, transferred my data and reinstalled my programs. Everything was peachy until I reinstalled an SSH tunnelling application I had used with XP Home. This program basically forms a tunnel between my computer and a remote server and handles requests passed via specific ports (usually 25, 80, 110 and 119). But ever since trying it on XP Pro the program I use (F-Secure) has been unable to initialize these ports (25, 80, 110 and 119). (I manage to create a tunnel to 110 and 119 but that's still of limited use.) The program's listening manager returns the standard WSAEADDRINUSE 10048 error: "Only one usage of each socket address (protocol/IP address/port) is normally permitted".
No, I know none of *my* programs usurp these ports and since I have no viruses, I can only assume programs and/or processes inbuilt in Win XP PRO are responsible. I know XP Professional uses additional network components but since this is not my area of expertise, I don't know which they are, let alone which may be responsible for hogging these ports. So, how can I identify applications or processes usurping these ports and, more importantly, shut them down permanently? Any ideas?