riojew04532
@cia.com
| reply to rickstep
Re: [Internet] Bell Business Internet Optimax Nightmare
I'll address Rick's question nonetheless. Static IP's do not depend in any way in any of the DSL equipment including DSLAM's, B-RAS/ERX or routers. Static ip's for GAS based services rely on the PPPoE login information. If you've got a static IP, when your PPPoE login is sent, the system sees it is a static IP account and always assigns the same IP to the PPPoE request. When a client isn't getting a static IP, it means that either the static IP wasn't provisioned or that the database has some sort of error and the IP isn't there. |
|
Glen1
These Are The Good Ol' Days.
Premium,MVM
join:2002-05-24
GTA Canada | reply to rickstep
Rick please take the time to post a new thread...you have questions outside of this one.
--
My Canada includes Quebec. |
|
rickstep
join:2002-11-25
Hamilton, ON
| reply to Glen1
Hi Glen1 and the group,
Why are so there so many technical issues with the Internet and the central office side?
In the 1960s and earlier, manufactured products had failures above 10%. Today automobile, microprocessor and electronic manufacturers produce parts with failures of 0.0001% to 0.000025% (1 failure in 1 million to 1 failure in 4 million).
There seem to be few technical issues with the manufacturers' equipment inside the Bell CO.
This leaves poor training, staff that simply don't care or outright incompetence.
My take on this issue is this. Since the circuit was working when the change was made, ALL wire and other devices between the office and the business are existing and the problem is in the office.
Bell may use equipment from several manufacturers, and of that equipment some may be older and not support a static IP. Since changes were made in the office, the assumption has to be that the service is available with at least SOME of the equipment in the office.
If equipment was changed in the office and if PROPER testing was done, the circuit MUST work.
There are way too many excuses here.
The Internet (including all the hardware and engineers, technologists & technicians) needs to be as reliable as POTS (Plain Old Telephone Service) which is no more that 1 hour of down time for a switch for 40 in service years, without the constant excuses.
The fact that it took two months it took to get DKS up and running after the 911 fiasco was absolutely outrageous.
Almost all issues discussed in this forum require very simple fixes. While many questions here come from individuals without any technical knowledge, it seems more and more that Bell staff should post questions here about CO problems so that Bell customers can get the service they are ENTITLED to.
Rick |
|
Glen1
These Are The Good Ol' Days.
Premium,MVM
join:2002-05-24
GTA Canada
 ·Bell Sympatico
| reply to Guspaz
That is exactly why when someone comes in here asking about Cable vs DSL we advise them to get the competitor's service before you disconnect the existing service. Take the time and extra cost to compare the two side by side. In this case if the company had kept the existing service running while the new service was being turned up it would have been business as usual until the new service was working properly. One computer could be placed on the new service and used to test the connection...when everything is up and working, cut over the Lan. Good advice Guspaz.
--
My Canada includes Quebec. |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
·Colbanet
| reply to rickstep
said by rickstep  :Guspaz, There is no guarantee, or anything even close to suggest that a parallel service will fix the problem. Rick. Of course there are no guarantees. It's common sense; if you have a critical system (or even just an important one), you don't shut it down until the new one is up and running successfully. That requires overlapping service. It doesn't always help, but many times it can save you if your new service has problems and the old one is still working. |
|
rickstep
join:2002-11-25
Hamilton, ON | reply to Guspaz
Guspaz,
There is no guarantee, or anything even close to suggest that a parallel service will fix the problem.
Rick. |
|
