Open GoogleCodeExporter opened 9 years ago
Please Ignore; issue resolved (caused by firewall not opening port even after
adding exception)
Original comment by danileig...@gmail.com
on 29 Mar 2012 at 6:27
How did you resolve this? I got the same issue, Winamp is added to Windows
firewall, but the port is still closed to incoming connections. When I disable
it entirely, it works, but this is not the way to operate of course.
Original comment by maxim.ko...@gmail.com
on 9 Apr 2012 at 5:03
open for winamp.exe the port 50000 both tcp and udp way (local range is enough)
on the Windows firewall. Works perfectly :)
Original comment by nahis...@gmail.com
on 18 Apr 2012 at 1:36
I have an EVO Touch 4G (galaxy s2, sprint). It was working fine with
Gingerbread. Phone got updated to Honeycomb and the client now always times
out.
Original comment by WilliamS...@gmail.com
on 16 Aug 2012 at 8:50
Ooops. Meant to say my phone updated to ICS, not honeycomb.
Original comment by WilliamS...@gmail.com
on 16 Aug 2012 at 9:38
I've found the solution!
It took me a while, but I've managed to fix the 'timeout' error.
Before trying the below mentioned solution, note that it may weaken your
computer's defenses. Proceed with caution. I bear no responsibilities to any
harm that may result from this.
Now, the following instructions have been written for Win7, but I think it
should work for other versions too.
First, open the Windows Firewall window, and click on 'Advanced Settings'.
In the 'Inbound Rules' section, look for 'Winamp'.
If you don't find it, continue. If you do, (two Rules, both named Winamp) skip
ahead to Scenario Two.
SCENARIO ONE - No Existing Rules
1. Click on 'New Rule'.
2. What type of rule would you like to create? - Port.
Next.
3. Does this rule apply to TCP or UDP? - TCP.
Does this rule apply to all local ports or specific ports? - All local ports.
Next.
4. What action should be taken when a connection matches the specified
conditions? - Allow the connection.
Next.
5. When does this rule apply? - Public. [Optional - Check Domain and Private
too, if it applies to your internet setup]
Next.
6. Name - Winamp
Description - [Unnecessary]
Finish.
7. Repeat Steps 1-2.
8. Does this rule apply to TCP or UDP? - UDP.
Does this rule apply to all local ports or specific ports? - All local ports.
Next.
9. Repeat Steps 4-6.
SCENARIO TWO - Pre-Existing Rules
1. Right-click on the first Winamp Rule, and click on Properties.
2. In the General Tab, make sure 'Enabled' is checked.
In the Action section, select 'Allow the connection'.
3. In the Protocols and ports Tab, make sure 'Local port' and 'Remote port' are
set to accept All Ports. Don't change anything else.
4. In the Programs and Services Tab, in the 'Programs' section, select 'All
programs that meet the specified conditions.'
THIS here, people, is the culprit; this is what was causing the problems in
connections.
5. (Optional) - In the Advanced Tab, 'Customize' the 'Interface types' to
accept 'All interface types', and in the 'Edge traversal' section, 'Allow' it.
6. Right-click on the second Winamp Rule, and click on Properties.
7. Repeat Steps 2-5.
There. Done. It should work now.
Have fun, people!
Original comment by nikhil.w...@gmail.com
on 8 Dec 2012 at 8:20
La solución de # 6 nikhil.w ... @ gmail.com es correcta, pero a mi no me
funcionaba si no desconectaba mi antivirus. Desconecten o cedan permiso a la
aplicación desde su antivirus y funcionará de maravilla. Sirve para cualquier
aplicación de Control Remoto de winamp para android.
Adios desde Chile.... !!!
Original comment by mk.silva...@gmail.com
on 8 Feb 2014 at 4:09
Original issue reported on code.google.com by
danileig...@gmail.com
on 29 Mar 2012 at 6:24