1

Topic: Problem Flinging to NeoTV from Desktop

I am not really a technology person but after having my NeoTV for a few weeks I decided to try and download the Flingo desktop application. It took me a while but I was able to download the application and the other items required. However when I try to open the Flingo desktop it tells me there is an error and to check the

2

Re: Problem Flinging to NeoTV from Desktop

Sorry my message got cut off. The continuation is:

...flingo.exe file. When I do that it says:
Traceback (most recent call last):
  File "flingo.py", line 357, in <module>
  File "twisted\internet\posixbase.pyc", line 419, in listenTCP
  File "twisted\internet\tcp.pyc", line 857, in startListening
twisted.internet.error.CannotListenError: Couldn't listen on any:8080: [Errno 10048] Only one usage of each socket address (protocol/network address/port) is normally permitted.

Can you please tell me what this means. I am able to fling from online but would like to be able to fling the videos I have on my computer.

Also, when I click on the button in the service tray I am able to fling videos but once on my NeoTV they are unable to load.

Please help,
    Amanda

(I don't know if it matters but my computer operates Windows 7)

3

Re: Problem Flinging to NeoTV from Desktop

Hi,
The real culprit is "twisted.internet.error.CannotListenError: Couldn't listen on any:8080: [Errno 10048] Only one usage of each socket address (protocol/network address/port) is normally permitted."
It looks like another service, probably a webserver, is using port 8080 and it not letting fling use that port.

Are you running a webserver on port 8080 on this machine ? In your browser try localhost:8080 or open command prompt and try running 'netstat -an'. If the web request succeeds or if you see 8080 in the output of netstat then stop the webserver or whoever is using that port and retry fling. It should work.

Thanks!
Tapan.

4

Re: Problem Flinging to NeoTV from Desktop

Thank you for responding. Sorry I wasn't able to try your fix before now.
When I checked my browser like you suggested (by typing 'localhost:8080') I got a long list of different things. I couldn't tell which could be the cause of the problem. The list is:

$AVG/         [Directory]    
$Recycle.Bin/         [Directory]    
6ED8D700D9DF25DEEE31BB2B7BA44F/         [Directory]    
BigFishGamesCache/         [Directory]    
Boot/         [Directory]    
Config.Msi/         [Directory]    
Dell/         [Directory]    
Documents and Settings/         [Directory]    
FIND_EULA_PATH/         [Directory]    
ID Vault/         [Directory]    
Intel/         [Directory]    
MSOCache/         [Directory]    
PerfLogs/         [Directory]    
Program Files/         [Directory]    
Program Files (x86)/         [Directory]    
ProgramData/         [Directory]    
System Recovery/         [Directory]    
System Volume Information/         [Directory]    
Temp/         [Directory]    
Users/         [Directory]    
Windows/         [Directory]    
codec-info/         [Directory]    
divx/         [Directory]    
logs/         [Directory]    
BOOTSECT.BAK     8K     [text/html]    
bootmgr     374K     [text/html]    
cirrus_install_log.txt     34K     [text/plain]    
dell.sdr     4K     [text/html]    
hiberfil.sys     4G     [text/html]    
log.txt     80B     [text/plain]    
lxde.log     256B     [text/html]    
pagefile.sys     5G     [text/html]    
stp.log     1005B     [text/html]    
user.js     449B     [application/x-javascript]    

Are all of these causing the problem? And once I know which is, how to I switch it off of 8080? Thanks!

5

Re: Problem Flinging to NeoTV from Desktop

If it helps when I searched in Command Prompt this is what I found that contained '8080':

Proto       Local Address        Foreign Address        State
TCP          0.0.0.0:8080         0.0.0.0.0                    Listening
TCP          10.0.0.2:58821     10.0.0.15:8080          Established

6

Re: Problem Flinging to NeoTV from Desktop

It looks like a webserver is running under your C:/ directory. Once that process is killed that port will be freed.
Try this, it might help.
http://answers.microsoft.com/en-us/wind … 253265f99e

Thanks!