Socket Error # 10061 Connection refused

rovingcowboy · Post by **rovingcowboy** » Sun Jan 06, 2008 7:54 pm

its got to be avast.?

but what is your systom info.? its not in your signiture..

if your on xp maybe there is a mess up there.? try getting the xp sp 3 beta 1 from majorgeeks.com and see if that will fix anything. it does make the system a little faster..

avz10 · Post by **avz10** » Mon Jan 07, 2008 4:08 pm

Well, I dont know anymore.

I have blocked my Widows Firewall, uninstalled Avast-no success. I then uninstalled MM3 and reinstalled it- same problem.

My internet connection is working well in the other programs that I use.

I have windows XP. I tried to install the new service pack, but it only came to 200MB and stopped. I am really frustrated. Should I try an older version of MM? This was not a problem with MM2.

Hope I get some responses. Thanks

rovingcowboy · Post by **rovingcowboy** » Tue Jan 08, 2008 2:32 am

the service pack should be a resume download one try again and see if it finishes the last 130 or so mb's?

i forgot to say its a big one to use a fast broadband.
sorry.

avz10 · Post by **avz10** » Tue Jan 08, 2008 2:16 pm

Thanks for your help, but it does not seem to work. Perhaps I should revert to an older version??

Today, I have installed the Windows update, restarted the computer, etc, etc. Same comment.

any ideas??

rovingcowboy · Post by **rovingcowboy** » Tue Jan 08, 2008 3:35 pm

go in to the beta room in the forum and to the first anouncement message by rusty. go to the last post in that thread and get the newest version of mm 3.

http://www.mediamonkey.com/forum/viewto ... 576#121576

see if he got your error fixed.?

avz10 · Post by **avz10** » Wed Jan 09, 2008 3:11 pm

Our dialogue continues!

I again uninstalled all MMs on my PC. As my problem started when I used 1129, I now downloaded the debug version, this time on my C drive. Same problem. I then scanned my PC for all bugs, defragmented it..., same problem.

Any other suggestions??

Thanks for your help so far.

rovingcowboy · Post by **rovingcowboy** » Wed Jan 09, 2008 4:46 pm

i don't know anymore since your other programs are dialing out
and you get online for this.
only thing to do is try and get a bug report made and sent in to rusty or jiri. since it has to be the dialing command in media monkey that is messing up.

kamuzu · Post by **kamuzu** » Sun Apr 06, 2008 11:58 am

go into TOOLS->OPTIONS->GENERAL->NETWORK and remove the V from Proxy.
it helped me.

geemarcus · Post by **geemarcus** » Tue May 06, 2008 4:38 pm

Hi,

It's a slim hope but I'm wondering if anyone can help me with connecting from work. I had been using an earlier beta (3.0.2..., a recent one), and I just installed the current (3.0.3.1166). Before updating I was able to use the "auto tag from Amazon" function, which is awesome by the way, although I was unable to connect to the CD database when ripping a new CD. With the latest beta I get a timeout error when trying to auto tag from the web (Couldn't show results: Socket Error # 10060 Connection timed out.). It was working this morning so I'm pretty confident the new build started the problem. A reboot didn't help.

Firefox requires I set the connection to autodetect proxy settings and iTunes just works (it says it uses IE configuration). IE configuration has an auto config URL but I can't find anyplace in media monkey to use that.

If I can't fix this I'll probably go back to 3.0.2 - do I need to uninstall in order to roll back?

thecongressman · Post by **thecongressman** » Wed May 07, 2008 10:40 am

I get the socket error all the time--and I know exactly why. I live in the middle east, and my internet sometimes can be sketchy at best. I'll have days when it bounces up and down. If I try to auto-tag when it goes down, I get the socket error. It used to be (before beta 1164) that when I got that socket error, I could no longer use Amazon auto tag for that specific country after my internet was live. For example, I would get the socket error looking for a Darkness album using the US search. Once the internet was back up, I still would get the socket error if I searched US amazon. But if I switched to the Canadian one, it was no problem. The only way to rectify that was to restart MM. Beta 1164 seems to have fixed that problem.

Guest from Dar · Post by **Guest from Dar** » Mon Mar 23, 2009 8:20 am

Malware had changed my connection settings in MM from 'no proxy' to 'localhost:7171', check that and should work afterwards

maki84 · Post by **maki84** » Mon Aug 10, 2009 1:53 pm

thecongressman wrote:For example, I would get the socket error looking for a Darkness album using the US search. Once the internet was back up, I still would get the socket error if I searched US amazon. But if I switched to the Canadian one, it was no problem.

Tanks.
I switched to Canadian and it works...

aureeka · Post by **aureeka** » Thu Feb 21, 2013 1:59 am

I have also this problem in version 4
No matter what type of Amazon i'm using (UK, U.S. France, etc) it still shows the same error
I'm using Windows 7, and firewall allow MM to connect to web
I have Avast Antivirus and it's allowed in there also.
I tried installing, reinstalling, no effect whatsoever...
Any idea ?
Thanx

nordwaky · Post by **nordwaky** » Sun Jun 21, 2015 2:36 am

I live in CA, USA. I have MM 4.1.5.1719 lifetime gold
I get Socket Error # 10061 Connection refused each time I try CTRL+L
I search and search though cannot find solution. Anyone?
I've tried changing Amazon US, CA, etc but no such luck
I have added MediaMonkey to my "allow firewalls" list

Anyone?

Guest · Post by **Guest** » Sun Jun 21, 2015 4:32 am

There have been problems in the past related to MM caching web(store) icons which could cause this. Latest version 4.1.7.1740 now has them bundled with the installer, so try updating the program.