Firefox just started to do this if on one user account someone has firefox running another user account on the same computer can not connect to the internet through firefox while firefox is running in the first user account
Windows XP/Windows 7 2 user accounts on the computer. If each acct is logged into the computer and tries to have firefox running only one can connect to the internet at a time. Have Verizon FIOS for ISP and this just started to occur. Firefox version 8 but also happening in firefox 6.0.2. How can we run firefox in two computer accts at the same time? Thank you
All Replies (3)
I am having exactly the same problem. This worked on all versions of Firefox up until mid last week. It started failing on Wednesday, coincident with the installation of Firefox 8.0 (see attached gif showing the automatic update on that date).
To fix the problem, you have to shut down Firefox 8.0 on one account, switch to the other account and then you can run it there.
If Firefox 8.0 is running on on account, the other account will run Firefox, but when you enter an URL it waits for quite a while then reports "The connection was reset. The connection was reset while the page was loading".
We also use Thunderbird 8.0 and it does not exhibit this problem, and works at the same time as Firefox 8.0. I suspect they might share some components.
I'd be happy to supply more details if needed.
Thanks,
Ed
I'm glad to know that I'm not the only one having this problem. Unfortunately having to only have firefox running in one acct at one time is a big problem on our computer because there are multiple concurrent users. I've tried to uninstall it and remove all settings and then reinstall to see if that would take care of the problem but it didn't.
Any ideas how to get firefox to load pages in 2 accts at the same time?
In the meantime I've installed google chrome and might switch to using that if I can't resolve this problem.
Thanks
Same problem... after upgrading to Firefox 8, I can only have Firefox open on one user account at a time.
Temporary solution: I simply went back to Firefox 7 for the time-being and problem solved. Hopefully they will come up with a fix soon.