User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20080404 Firefox/188.8.131.52 Build Identifier: version 184.108.40.206 (20080421) My wireless server doesn't think it's their problem and I agree. I am able to browse the Web, I just can't download e-mail from the server. The message I get is "Could not connect to server mail.usiwireless.com; the connection was refused". Anytime my husband has used his profile this happens. It doesn't matter if I log him off or switch users, then log in to my profile, the connection is refused. I have to reboot the computer. If this isn't a Thunderbird problem, then it must be Windows XP problem. Reproducible: Always Steps to Reproduce: 1. Log in to a profile on a computer with more than one profile. 2. Log off (or switch user) then log on to another profile. 3. Open Thunderbird in that profile and click on Get Mail. Error message appears. 4. Get a little mad. 5. Shut down computer and restart. 6. Log in to (my) profile, repeat #3, no problem. Actual Results: Described above. Expected Results: Described above. I have a Dell Dimension 4300, Windows XP with Service Pack 2, and Norton Anti-virus (I've tried disabling that but it didn't make any difference).
Summary: Won't connect to my server after a different WinXP profile has been logged in before I log in to my profile. I must reboot computer, then log in to my profile first. → Won't connect to my mail server after a different WinXP profile has been logged in before I log in to my profile. I must reboot computer, then log in to my profile first.
POP3? IMAP? (probably POP3) Do you mean "connection refused" at following situation? You have only one POP3 account of mail.usiwireless.com, of uid/passwd MS Win's user-id-1 Tb-1 is active, access mail.usiwireless.com with your account's uid/passwd MS Win's user-id-2 Start Tb-2, try to access mail.usiwireless.com with your account's uid/passwd => "the connection was refused"
you don't cite the full error message => incomplete if you still see problem please comment
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.