AT&T Midwest → Static IP upgrade nightmare....for me anyways..

I'm currently on the 1500/256 speed package. I wanted to have a static IP for an FTP or a website. When I inquired about statics a few months ago, Team Data said I would get the same IP every time I connected through PPPoE. I called TD to place my order and asked if this doesn't work out I can switch back, he says I could. I then asked if I had to buy the Efficient Networks router, he said I didn't and could keep my current equipment. A few days later I get a confirmation mail saying the statics are in place, to call support for assistance, and instead of one IP they offer everyone 5 IPs now. It was around that time my connection drops. I call router support, once I told them I didn't have their router they refused to help me. This is where the fun begins...

That entire day was spent trying to get someone to unofficially help me, no one would, not that I blame them, and futile attempts to make it work myself. The next day I called to cancel the statics and go back to dynamic. TD says I couldn't, and I would have to cancel my service and order as a new customer or I would need to buy the router. I was furious. I told them what I was told by sales and that this was unacceptable. He contacts a stupidvisor....er....supervisor who then contacts his superior. They finally admitted they could change me back to dynamic but it was problematic for billing, so they tell everyone to cancel their service because they can't downgrade. So, no service for 4 days. I called TD everyday for the status, no one returns my calls. On the second day I get transfered to techsup, a tier 2 troubleshoots and can't get it running so he gives me a trouble ticket. ASI calls to schedule a visit. I asked to talk to a tech before someone comes out. The tech I spoke to was a frekin genius, he knew exactly what it was, ASI pulls through again. Everyone failed to mention I use name@static_ameritech.net for my login. It's strange that my Linksys shows my gateway IP for the WAN IP, but it works, I can't access my usable IPs though. I finally get a call from TD saying I'm back on dynamic, but I'm still on static, and still waiting...

Anyway, the point to my story is...Ask questions first.

said by turn_key:

---

Anyway, the point to my story is...Ask questions first.

---

My gut feeling is that's why there are FAQs on the subject.
James

About the Linksys and not being able to get at all the IPs: »AT&T Midwest/Ameritech FAQ »SBC/Ameritech 5 Static IP-Compatible Routers (update 05-19-06). It can't support that since it can't do multi-NAT.

The static login issue is mentioned in that FAQ entry, and also here: »Top 10 problems and fixes collection thread (which is in the most common problems and fixes thread).

Maybe Ameritech tech support should just use our FAQ instead of just guessing...

Yeah, it's funny how people here are more knowledgeable about THEIR company...

I was just blowing off some steam and that was the condensed version...lol

Thanks for the links, I'll check them out.

said by turn_key:

---

Yeah, it's funny how people here are more knowledgeable about THEIR company...

---

Heh... Well, I would surmise that we have a lot more experience with the service and system than most of them do. We've had to do all sorts of troubleshooting over the years to figure out what the hell was going on when things went into the toilet. Unfortunate, but we certainly learned a lot.

»AT&T Midwest/Ameritech FAQ »SBC/Ameritech 5 Static IP-Compatible Routers (update 05-19-06)

Just as a side note - this FAQ is missing two POPs that require @static_ameritech.net logins:

Both Milwaukee and Cleveland require it as well.

OK...that must be relatively new. I'll add those.

By the way, if you ever find anything that needs fixed in there, you can use the little notepad icon next to the "byline" at the bottom of the item. It generates an IM to me with the link to the item.

I was reading the compatibility list....

I've read that the ZyXEL is the same as the Netgear. I know it says the Netgear won't work, but they are the same internally, has this been confirmed?

[text was edited by author 2002-04-22 00:39:43]

I'm sure both routers are physically capable of doing multi-NAT. They might use similar hardware but the Netgear router may not be programmed to support it. Most routers are just simple hardware and a programmable DSP which is the meat of the operation. The software the router runs is what determines its function - Zyxel just happens to program theirs with better features.

I currently have a Linksys 4port router. It's pretty flaky and they did a crappy job implementing everything about it (it was the only thing available when I purchased it). If I were to buy one today I'd opt for a Zyxel box.

Who knows, I might be trashing the Linksys soon. It just has too many issues.
[text was edited by author 2002-04-22 09:18:09]

Actually, all sites in ameritech should use the "@static_" for static IP's. Sometimes it might not be needed, however in the future if that POP ever upgrades past 1 redback there will be problems.

In the future it might be required in other areas. However its currently only required in Chicago, Cleveland, Detroit, and Milwaukee.

It's not a good idea to login using "@static_" if its not required. There have been issues linked to users logging in this way when it's not needed. My suggestion is don't use it unless you have to.

Please feel free to elaborate as to what "nasties" can be caused by logging on with "@static_". I'm curious.

Something the tech at ASI said was hopefully by the end of the year, if regulations are lifted, Ameritech will stop using PPPoE altogether...something about Ameritech's equipment interfacing with ASI's...Ameritech will rebuild their network. He said the first thing people will notice is the increase in speed, basic package will be 1.5 down. They want to run it like the phone lines, they don't make money from your service but only when you buy the extra 50 products they offer for your service, i.e. Call waiting, call forwarding, caller ID, etc. So look for movie and audio subscription and pay-per-view...oh no...

Not all but some areas have authentication issues. I've seen where a customer will authenticate 4000+ times in a matter of hours.

Believe me it causes issues. Albeit uncommon but it can happen.

Why not avoid the possibility of a problem by not using "@static_" when you don't need to? Makes good sense to me.

Hmmm, the "@static_" shouldn't really affect the login process in terms of radius authentication. Especially in cities with only one redback. But hey, whatever works I guess.