EDIT - never mind

This post has been edited by wildside: Apr 4 2005, 02:08 PM

Let's try to see if there's a pattern that is helpful here...

To those people that have been successful in getting 218.* or 60.* IPs, can you please answer these questions...

1) What's the average number of times you need to disconnect/reconnect from a 219.* IP before you successfully get the desired IP?

2) Method used to reinitialise connection - software reboot (PPPoE software) or hardware reboot (powering off the modem itself)?

3) Are you using the default TMnet DNS set - i.e. 202.188.0.132/133 + 202.188.1.5?

4) Your location.. DSLAM used, if possible?

5) Mode used - G.dmt, G.lite, etc...

As many responses as possible please...

This post has been edited by wildside: Apr 4 2005, 02:38 PM

Honestly, I'm just trying to help as many people as I can...

Getting tired of playing on Stormrage all alone, whilst my WoW-kaki keep getting stuck with the absurdly high latency.

Will be particularly interested if there are any people in the TTDI/Damansara area who are successfully getting 218.* and 60.* IPs, and how they are doing it.

And just in case there are people who don't want to answer the questions because you are concerned that the 219.* people will flood your precious 218.* and 60.* IPs and increase your latency, let me assure you that's not how it works.

Everyone will still be using the common Streamyx bandwidth and infrastructure. It's just a matter on getting on the routing table/schedule that's not borked. Routing table setups cannot be discerned from traceroutes BTW. It's largely transparent, which is why I am asking the questions...

I have just got five people in four different locations resetting their modes to g.dmt, using the default TMNet DNS values and using Windows XP built in PPPoE functionality to 'soft' disconnect/reconnect - i.e. modem stays powered all through.

one person in SS2 - no luck, still stuck on 219.* after 12 tries.
one person in Bandar Utama - no luck, still stuck on 219.* after 8 tries.
two people in TTDI - stuck on 219.* after 9 tries and 11 tries respectively.
one person in Bukit Damansara - stuck on 219.* after 11 tries.

I think we can conclude that the swath of DSLAMS extending from Bangsar all the way down the Sprint to Bandar Utama is 'pre-programmed' towards the 219.* block... at least using the default Streamyx settings.

Looks like bad news for people living in those areas.. unless I hear differently from people here.



This post has been edited by wildside: Apr 4 2005, 04:01 PM

Hmmm, interesting seeing people living in approximately the same area, with some having no problems connecting to alternate IPs and some almost seeing it impossible doing so.

I think it may be more than a geographic thing, and maybe something to do with modem and connection settings as well...

Will try some experiments tonight...

And to make matters worse, I happen to be stuck at the Authenticating stage connecting to the WoW server now.

This will be a very... 'interesting' evening

Well, after extensive testing and experimentation to find a reliable way to get 218.* and 60.* in the TTDI/Damansara area, I have one thing to say...

I give up! I think I've tried every software and hardware setting I know and I can get it out of the 219.* range for my friends' PCs.

Sorry guys...

Any ideas would be welcome...

So apparently, they stuck a fair block of 218.* IPs behind the proxy now as well.

I'd say it's time to bypass the 'choet-chais' and track down the email addresses of Baharum Salleh and Abdul Wahid Omar, and send them long comprehensive emails with traceroutes, comparisons between 218/219/60 IPs and reminders of their corporate responsibility (as described on the front page of the TM website).

May also want to point out that the lower-liners are being most unhelpful while you are at it.

Ummm yes... please elaborate on how you would set this up...

You'll make quite a few WoW-deprived people happy tonight.

Not asking how you ping a port, but rather how you set it up so that WoW connects to and utilises that port exclusively both at the logon and server phase.

Strange, because I'm pretty sure mine has been going to 3728 all this while.

Time to poke about in the logon setup scripts, it seems..

EDIT - never mind... My fault entirely. Just got a friend to check. It is 3724.

Don't know where I got the idea that 3728 was used instead of the obvious 3724.

Thanks

This post has been edited by wildside: Apr 5 2005, 11:25 AM

Apparently, baharum@tm.net.my still works. So maybe it's time to send your grievances to the head-honcho of TMnet itself, if you think upper management is still unaware of the issues because the lower liners are hiding it from them.

I've done my part, including a part telling him that his staff have been behaving unprofessionally by not attempting to resolve the matter to the satisfaction of the subscribers. Also threw in something about Lim Keng Yaik's recent speech and about Telekom's corporate responsibility as described on the website.

Xeo, eikan.. there's no solution as such.

tarpaucase has given up on playing WoW at home, so he's going to be playing at the office instead

That's good.. but I would encourage people to send emails that are calm, collected and logical, rather than resorting to emotional rhetoric, blanket accusations, etc.

HERE.. Page 41 or you can search for the name.

I'd believe it if he actually gave you a specific date on which the problem would be fixed... INSTEAD OF giving you the usual 'I don't know' answer.

I'd believe it if he gave you a plausible reason why it's taking so long to fix... INSTEAD OF giving you the usual 'Technical problem our personnel looking into it' answer

I'd believe it if he gave you his name... INSTEAD OF trying to avoid answering.

I'd believe it if he calls you at some point to update you on the status... INSTEAD OF you never hearing from him again.

Heh, which is why I always get a name and a direct number, so I can keep going after the same guy.

My current 'victim' is a guy named Shahril. I think it's getting through to him that I'm not going away. I always start my conversation with 'Hi, remember me?'

I'll go call him for the 5th time later today.

Well, I did promise not to divulge his handphone number. I think it's fair not to spread someone's personal number all over the internet.

That said, you should know that this guy is not your typical TMnet goon. He actually works in Telekom's infrastructure division responsible for the TTDI/Damansara area. Got passed on to him on one of my 'routine' calls to 1-300-88-9515.

I think everyone should attempt to get someone similiar in your area. There's always these few people responsible for an area to deal with technical issues.

In any case, just called him a while ago... Maybe today's a particular bad day for him. Turned off his handphone and all :/

Ah see... this is where we don't agree... If they were a focused organisation, they should have had plenty of time to have analysed the problem, set a deadline to fix it and commit to it. Not having a deadline is just asking for procrastination to creep in.


Following on my first answer above, I place a very high emphasis on the need for the backroom technical staff to be constantly in contact with the front-line staff to keep them abreast of developments. It's called professionalism and customer focus. Otherwise, why have a support staff manning 1-300-88-9515 anyway?


Again, it's customer focus to show that they are approachable and taking a personal interest in your problem. Not willing to do so even when asked tells me they have something to hide.