To: mr.mark who wrote (20947 ) 6/24/2001 11:53:01 AM From: Rick Faurot Read Replies (2) | Respond to of 110652 mark, Since you use Communicator for email as I do, I am wondering whether you or anyone else has encountered the following: I have been getting a dialogue box popping up during a session. The box says "Password Entry Dialog The mail server responded: mail storage services unavailable, wait a few minutes and try again." At the bottom of this box is a place to enter my email password and two buttons, ok and cancel. Problems here are that entering email password and clicking either ok or cancel does nothing. Using Control/alt/del sometimes makes the box go away, but more often does nothing and then the control/alt/del box hangs on the screen as well. While this password entry box is hung on my screen, I can still see data coming in on the screen that was up, for example quotes or mIRC, but I cannot change screens or use my mouse to make any changes. The only way to get rid of the password entry box is to force shut down my machine. My first take on this was that my isp was having a problem, so I called them. They said they weren't having a problem, that it was a browser problem. So I deleted Communicator 4.76 and downloaded and installed 4.77, which seemed to have worked for a while, but the bug did come back, though not as often. All of this is happening on my Dell 4100 on W2000 and connected via DSL. Yesterday I got the same bug on my Dell 400 which is on W98. On this machine I am still using Communicator 4.76. This machine is connected via 56k to a different isp than my Dell4100. Again, the password entry box and buttons on this Password Entry Dialog box were not functional and the box locked me out of doing anything else with my machine. In all instances where this box has popped up, I was not trying to send or access email, and once I rebooted, I did not have any new mail coming in. So it appears to me that either Communicator is getting some kind of message from the isp that triggers this dialog box to pop up, or else there is something in the Communicator code which is buggy and causing the problem. I believe that is everything I know about the problem. Any ideas, feedback or suggestions would be appreciated. best regards, Rick