Technical difficulties
As I said before, I have successfully configured my browser (and Semagic, incidentally) to use the webproxy. The problem is that now I am unable to connect the MSN Messenger module in Trillian. I downloaded the actual MSN/Windows Messenger and tried to log in again; it said I was using the wrong password. I went to the Microsoft Passport and MSN homepages and both allowed me to log in with no problems.
Then I guessed that the proxy was the problem, set Messenger's options to "I use a proxy server" and entered the appropriate information (SOCKS version 5, webproxy.queensu.ca, 8080) but it said, "Unable to connect to the SOCKS proxy server." I tried setting it to SOCKS version 4 or HTTP, to no avail. I tried all the same measures with Trillian, first applying the proxy settings to all connections and then only to MSN. The other IM services all work fine no matter which setting I use, but MSN obstinately refuses to connect. Grr.
Any suggestions?
(Yes, I'm going to bed now. I've mucked about with this long enough.)
Then I guessed that the proxy was the problem, set Messenger's options to "I use a proxy server" and entered the appropriate information (SOCKS version 5, webproxy.queensu.ca, 8080) but it said, "Unable to connect to the SOCKS proxy server." I tried setting it to SOCKS version 4 or HTTP, to no avail. I tried all the same measures with Trillian, first applying the proxy settings to all connections and then only to MSN. The other IM services all work fine no matter which setting I use, but MSN obstinately refuses to connect. Grr.
Any suggestions?
(Yes, I'm going to bed now. I've mucked about with this long enough.)
no subject
no subject
Hmm... maybe it's because I always switch to Queen's webproxy after I've already logged onto Trillian? But it'd still disconnect after a while if it's the webproxy's problem... (as well, you can connect to MSN on campus computers, so their proxy can't be the prob, can it?)
no subject
Could you ...
I ended up having a similar problem on trillian, which I thought was an error like yours.
what had happened is that I'd entered the wrong password like ... once, maybe twice ... on trillian. And then went back to using the right password, but MSN had already freaked out on the wrong password from a different program tihng and was blocking anything even with the right password. And then I went to MSN messenger and it said that my password was invalid, but gave me a chance to 'reset' my password I think it was ...
I reset it (just re-entered the right password *L) and it worked perfectly in trillian again.
It just seemed that MSN totally freaked out at the wrong password one time and locked me out. Now, it may have been the proxy making the password seem wrong to them or something, but it did freak out completely.
If that doesn't work ... if you open the window that shows the information going on between trilian and the service, it usually gives an error # - and there are lots of 'how to avoid this error' type things on the trillian messagesystem.
(oh, I did run across one thing about proxies on that too, under I think the error 0.0 ones ... I think it said the http proxy thing does't work on trillian, if that helps ...)