
| Connection Issue to ASI Partner provide.net I subscribe to SBC DSL thru an ISP called provide.net. I received a Speedstream 5200 Modem/router from a friend which I am using in router mode. It sees the DSL service I have green lights. Because this modem was not on the SBC service before I believe the PPPoE settings are incorrect and my ISP said they do not have those setting because the modems they send come preset. Does anyone have the setting I need to set (setting cats below)
VPI - ACI - Encapsulation Type - Traffic Class - Peak Tx Cell Rate - Sustained Tx Cell Rate - Tx Burst Tolerance -
Thanks
Subject edited by moderator to reflect the proper ISP [text was edited by moderator] |
|
 RadioDoc58ef2c0Premium,ExMod 2000-03 join:2000-05-11 | Re: SBC DSL Connection IssueAre you sure you need all of that?
Anyway, this may get you rolling... Protocol in use...................... RFC1483 (SNAP) Connection Identifier (VPI*VCI)...... 0*35
-- Open your eyes see the lies right in front of you. |
|
 | Thanks,
Not sure if I need it all or not but it is a good start cause I get no connection to my ISP it fails to grab a IP at moment. My current PPPoE is set at 8/81 which I was sure was incorrect.
Thanks again I will change it and see what happens.
BTW I am in Michigan |
|
 | Well I changed my PPPoE setting to 0/35 and now I am at least getting a different connection error and I am now showing a Access Concentrator # whatever that is.
I get the following error message
"The local connection is still busy, please wait a few seconds before attempting to connect"
which is a step in right direction I think!
Any other suggestions? or information you need to help determine problem |
|
 RadioDoc58ef2c0Premium,ExMod 2000-03 join:2000-05-11 | That's a new one on me. The Access Concentrator is the ASI Redback which your modem/router is talking to. If you get that far the physical layer link is up and running.
Is that error coming from the router? All ASI (SBC) provided wholesale DSL connections use the same protocols and settings, so this should be fairly easy to track down now. Do you have your username in as name@provide.net? -- Open your eyes see the lies right in front of you. |
|
|
|
 | No I have my username without the @provide.net cause ISP said I did not need it but I will try it, can't hurt |
|
 RadioDoc58ef2c0Premium,ExMod 2000-03 join:2000-05-11 | If it's provisioned via ASI, you usually need it. |
|
 | Ok changed it and still same error busy lol this is nuts & frustrating so close yet so far
Made more progress so far here then I have on phone with ISP they keep saying we will have to refer to the network guys and call you back, and so far no call |
|
 RadioDoc58ef2c0Premium,ExMod 2000-03 join:2000-05-11 | Damn. I don't see anyone online right now who can check this out from ASI's side either. -- Open your eyes see the lies right in front of you. |
|
 | There were so many options and choices when I setup the PPPoE to 0/35 like
Traffic Class - Constant Bit Rate, Unspecified Bit Rate, Variable Bit Rate PPPoE Config - Client Only, Bridged Only, with 2684B Connection, with PPPoE Bridge
I will tinker with these 1 ata time reboot Modem see if makes any difference |
|
 RadioDoc58ef2c0Premium,ExMod 2000-03 join:2000-05-11 | Traffic class is UBR (unspecified). PPPoE should be bridged
That "busy" error still has me flummoxed. -- Open your eyes see the lies right in front of you. |
|
 | When I select with PPPoE Bridged next choice is
Should the Virtual Circuit also use a 2684 Bridged connection? Yes or No |
|
 | After I changed it to PPPoE Bridged and selected No to 2684 Bridged connection and rebooted I get;
"The local connection failed to negotiate PPPoE options. Please check your username and password"
If I try again is when I get;
"The local connection is still busy, please wait a few seconds before attempting to connect." |
|
 levI think there is a target on my backPremium,Ex-mod 2002-08 join:2001-05-30 Chicago, IL kudos:2 Reviews:
·AT&T Midwest
| Ned,
The weekend is a VERY bad time to try to resolve this kind of issue. You can try to keep beating on it, but you'll probably be amazed with the highly qualified help you'll get on Monday.
I'll move your thread over to the ASI area. ASI is the DSL transport provider you're using, that RadioDoc mentioned.
You might want to see if there's anyone at your ISP, or any other user of your ISP who's up on the settings for DSL. The website at »www.provide.net was no help at all, and doesn't seem to mention anything about DSL. |
|
 DavidNow accepting new patientsPremium,VIP join:2002-05-30 Granite City, IL kudos:70 Reviews:
·AT&T Southwest
·DIRECTV
·AT&T Midwest
·Google Voice
| reply to Nedbeam
Re: Connection Issue to ASI Partner provide.net Actually the person that could check the router would be core network.. It is probably built as an SBCIS customer which would be different.
IM me the info on monday and I can check
Thanks David -- Fast and furious!! 225lbs lost and a future that I never dreamed of... Whodathunkit?? |
|
 AmeritecTechChange we can believe in, 1922Premium join:2002-09-06 Houston, TX kudos:6 | reply to Nedbeam Could you contact Provide directly at (888) 480-4200? |
|
 | Yeah I tried calling provide net the HD personal state they do not have that kinda info and passed the ticket to the network team and that they would call me back but not heard anything back from them yet. |
|
 | reply to David Beach Boy,
What info you want the setting I have currently in my PPPoE configuration? |
|
 wayjacPremium,MVM join:2001-12-22 Indy kudos:1 | Beach Boy needs the 10 digit telephone number, you may want to include the billing name and address. -- God bless our troops |
|
 OHnetguyPremium join:2003-01-16 Toronto, OH
| reply to Nedbeam
Re: SBC DSL Connection Issue I didn't find the following thread very informative. But, it may be better than nothing. It's the only thing that came up in a Google search of that error.
»Efficient 5200 and login failure - Frontier DSL...
Also - to my knowledge, it would be impossible for you to connect if you don't have some @domain or @realm appended to your username upon auth. This is what tells the CLEC to pass your authentication request on to your ISPs RADIUS servers. Without @something on the end, it goes into the great abyss. Considering your ISP told you that you didn't require one at all, you were either dealing with a clueless tech who has nothing to do with the DSL side of things or..well, that must be it. At any rate, it may or may not be @provide.net - It was selectable when your ISP set up their DSL options through ASI - in fact they could even have more than one possibility. They may or may not have chosen @provide.net - but they did in fact choose @something.
Mike [text was edited by author 2003-10-05 10:26:33] |
|