Transmission

I have a very strange problem, had a fully functional transmission system before going on vacation, accessible via Transmission remote gui. I have returned from vacation, fired everything up and transmission no longer works. From the GUI i just get 'connection reset by peer' and from web interface this does nothing. I have rebuild the software again, no errors during build and the software fires up fine, but no better off in terms of accessing the transmission daemon. Port 9091 is clear from a firewall perspective, but server does not respond. I am not too sure where to start or what tools to use to assist diagnose this problem further. (I had Transmission 2.33 running on Centos 5.5)

Check the IP addresses or names you are using.

And I mean check them carefully, it could be a DNS problem if you use names, and spyware/virus are well know to use those kind of tricks, exploiting name resolution (in Windows, changing etc/hosts).

That kind of response (connection reset by peer) usually means that you connected to somebody else, which doesn't have anything on port 9091, or has the firewall closed (and if I understand your description, you shouldn't even go through a firewall, not even yours, your server and the computer you are using are on the same LAN, or not?).

I have made some progress. It is now evident that I have something running on my Linux box that's grabbed port 9091, just not sure what this is or why this did not happen before. I have reallocated transmission to port 9191 and all is working fine again, but still a mystery what has taken the original port. Clearly not a transmission problem though.

Its very easy to see what is using the port:

Thanks, I have now confirmed that Twonky Media Server is also listening on port 9091, although the documentation for this software makes no mention of it using this port. I am even more surprised that this has not caused a problem previously.