What protocol are you trying to connect with? Sometimes you'll get that when the AOL service isn't working properly or you don't have an active internet connection.
Have you tried connecting with the local versions of Pidgin and GAIM? Are you able to get online when you have those issues? It could also be some type of firewall/port blocking issue.
ok I found out the problem. It seems that the computer I was on refused to pass internet to any portable apps running on my flash drive because when I went home the next day it worked fine on my computer, it worked fine for me on my school computers. Not sure how to fix this problem exactly so if anyone has information on that please post it, as I bring my flash with me everywhere,and not having internet for those is a pain in the butt
I did experience that on a relatively new Vista install, where I was forced to be "Guest" -- in other words, very restricted. If the computer you were on was having that problem, you'd need to get the owner to grant more privileges to the account you were using.
Ok I'm at my school and am having a problem using Pidgin from my flash drive, it's not the internet since I'm currently on Firefox on my flash drive. The error is:
Could not connect to authentication server:
Windows socket error #10060
I've tried downloading Winsock.dll and Winsck.dll and putting them in the folder with Pidgin(I can not put them in the System32 folder since I do not have admin)is there a solution to this or is it that the system32 winsck.dll/winsock.dll needs updating?
Either the server it is trying to reach is not available, or it is blocked by your firewall, or the Pidgin executable is blocked from using the internet.
I don't suppose you have other IM accounts on other networks you can try. If you get the same error with all of them, that would pretty well confirm either that pidgin is blocked, or your school has blocked access to IM servers (which wouldn't be surprising).
It is most likely a firewall issue at school. You can try to set the port to 80, which should allow the traffic to go through. I had an issue before where I couldn't connect to aim with the standard port, but changed it to 80 and it went through fine.
If the people who run the firewall have a clue, and if they really want to block IM, they will have been a bit more thorough than that. But who knows. Maybe they just wanted to take a stab at it so they can tell the boss that it's been done.
ok had an error trying MSN so it's something with the school network. Tried changing the port to 80 and it just keeps on trying to connect, class about to end will try again 2morrow
What protocol are you trying to connect with? Sometimes you'll get that when the AOL service isn't working properly or you don't have an active internet connection.
I'm also having a connection error. The error message is:
"Could not connect to authentication server:
Error resolving login.oscar.aol.com: 11004"
AIM Options:
Server:"login.oscar.aol.com"
Port:"5190"
These are the default settings, and I have tried to use Pidgin and GAIM
Have you tried connecting with the local versions of Pidgin and GAIM? Are you able to get online when you have those issues? It could also be some type of firewall/port blocking issue.
I'll add to what the others have said: is there a firewall that might be blocking outgoing connections? 10065 might be "no route to host".
Can you open a cmd.exe window and
and get anything back?
If it is not AIM but something else, let us know what.
MC
ok I found out the problem. It seems that the computer I was on refused to pass internet to any portable apps running on my flash drive because when I went home the next day it worked fine on my computer, it worked fine for me on my school computers. Not sure how to fix this problem exactly so if anyone has information on that please post it, as I bring my flash with me everywhere,and not having internet for those is a pain in the butt
I did experience that on a relatively new Vista install, where I was forced to be "Guest" -- in other words, very restricted. If the computer you were on was having that problem, you'd need to get the owner to grant more privileges to the account you were using.
MC
Ok I'm at my school and am having a problem using Pidgin from my flash drive, it's not the internet since I'm currently on Firefox on my flash drive. The error is:
Could not connect to authentication server:
Windows socket error #10060
I've tried downloading Winsock.dll and Winsck.dll and putting them in the folder with Pidgin(I can not put them in the System32 folder since I do not have admin)is there a solution to this or is it that the system32 winsck.dll/winsock.dll needs updating?
Either the server it is trying to reach is not available, or it is blocked by your firewall, or the Pidgin executable is blocked from using the internet.
I don't suppose you have other IM accounts on other networks you can try. If you get the same error with all of them, that would pretty well confirm either that pidgin is blocked, or your school has blocked access to IM servers (which wouldn't be surprising).
MC
Ok I'll try to log into a yahoo account 2morrow, I tried Miranda to see if it was Pidgin and Miranda couldn't log in either.
It is most likely a firewall issue at school. You can try to set the port to 80, which should allow the traffic to go through. I had an issue before where I couldn't connect to aim with the standard port, but changed it to 80 and it went through fine.
He could try 8080 as well. But 80 is a better bet.
The developer formerly known as ZGitRDun8705
If the people who run the firewall have a clue, and if they really want to block IM, they will have been a bit more thorough than that. But who knows. Maybe they just wanted to take a stab at it so they can tell the boss that it's been done.
MC
I concur, but that's the way it was at my school. They just blocked non standard ports, so basically anything outside of 80 was blocked.
ok had an error trying MSN so it's something with the school network. Tried changing the port to 80 and it just keeps on trying to connect, class about to end will try again 2morrow