I'm generally a low-maintenance Verizon home phone and dsl client but this is a major PITA. Wondering if it's my OS or browsers or the crappy new netmail site is just not working today.
Get the "Session Timeout" on everything associated with mail. Can access my home phone and dsl account profiles but zip on netmail on the "new" or even "classic" views. Get the pop-up to log back in and I do so, but NADA. Cleared cookies and history frlom both Firefox and IE8 and restarted. Disabled Norton 360. Nothing works.
I don't access netmail often, but I am on a biz trip this week. It's not the server. I can send/receive on this account on both an iPhone and the work Blackberry and just did test msgs on both a few minutes ago. But I need the netbook to send a couple of large word and excel files.
So for my 1st post I am thinking about raising the **bleep** flag on Verizon since 2 calls and a chat runaround got me nowhere today. They are basically indifferent or uninformed.
So are there any issues with Win7 (mine is still the starter version on the netbook) or is the site just down today? Or am I an idiot missing something that's very obvious ? Which is entirely possible.
Hello Trout. Sorry for the delayed reply to this thread. Are you still experiencing this problem? - Travis
I am also having the same issue with "Session Timeout" messages when I try to access my Verizon emails. This only occurs when I try to access them from work not from home. Is there a setting I need to change under Internet Options in the Browser or is it that my employer is blocking this site???
I'm seeing this as well - I suspect it has something to do with using a VPN back to the company intranet, and a proxy server they have set up between their outgoing connections and the internet.
I have been having the same problem. Never happened until a few months ago, and now happens all the time - once it times out once, that's it for the rest of the day, every subsequent login is immediately logged out again.
Can anyone explain to me the purpose of having "the community" ask each other how to solve this problem, when clearly it is a Verizon website issue?