jvmorris
I Am The Man Who Was Not There.
Premium,MVM
join:2001-04-03
Reston, VA
1 edit | reply to agilityman00
Re: [southeast] What's involved in switching back?
Yep, that shows 19.2/4.8 or thereabouts. However I was quoting the Verizon speedtest for quantification purposes as a standard benchmark (and Verizon has confirmed it from their end).
Performance is actually horrible. It often takes two minutes (now)to simply check my Verizon e-mail -- and that's assuming that there's no e-mail to download. (Used to be a matter of a few seconds with Verizon DSL.) Youtube videos are so slow that they are (now) completely unwatchable (and that includes in the middle of the night, because I've checked). I just redownloaded the PCCheck software from Verizon; that 10 MB download took ten minutes! And, yes, I've run the FIOS Optimizer repeatedly; doesn't make any difference.
I really think I want my old DSL connection back. I can live without FIOS TV; don't watch TV much anyway. Admittedly, Verizon FIOS gives me a lot more channels than Comcast did, but the internet is my primary concern and FIOS simply isn't hacking it.
Addendum: I'm not really sure that the problem lies at this end at all; it is increasingly looking like some problem at the Verizon CO or further upstream with their own infrastructure. The DSL connection worked fine.
--
Regards,
Joseph V. Morris |
|
PoloDude
Premium,VIP
join:2006-03-29
East Northport, NY | I would suspect that the problem exists with your pc. do you have any custom network settings on it? static ip. alt dns? |
|
jvmorris
I Am The Man Who Was Not There.
Premium,MVM
join:2001-04-03
Reston, VA
| Negatory. I have multiple PCs here, some are wired, some are wireless connections to the router. Situation is the same on all. Personally, I've made no configuration changes at all and have relied exclusively on configuration changes suggested/made by Verizon techs (remote access) after the problem first developed.
Things haven't got better or worse. Makes no difference. Installation was 6 October; problem did not become apparent until 10 Oct. No configuration changes or new software installs in the interim. Okay, there were the MS updates of Tuesday, 14 October, but that was AFTER the problem began.
--
Regards,
Joseph V. Morris |
|
