Yortw: I spoke to Telecom yesterday.
They were happy to give me a credit due to my issues and said it would show on the next bill (no arguments at all), but I don't know how much of a credit it will be yet.
I told them they could close the open case since I had a work around, but I tried to put the hard word on them that it was all their fault for shipping a modem with known incompatibilities and no warning. Not sure if I got that message through or not, they sort of tried to blame MS/Windows, which I didn't accept but it may have been water off a ducks back. I explained about how long the problem had been going on for, how no one had even mentioned checking the DNS let alone the specific modem incompatibility, about the forum post here which quickly resolved it and suggested this was a problem they should already know about.
They DID promise to update all their 'Technical Coaches' and get the information published down to the front line troops so they knew about the issue and that using the Google DNS servers would work as a work around. The guy I spoke to also said he had a modem expert he knew but who was currently away, and he would follow up with him when he got back. I also asked them several times to make sure their help & support pages mention this issue and possible solutions, and I sort of got a 'yeah', but I'm not sure if they really meant it. I guess we'll just have to wait and see what happens.
I'm pretty confident the guy was actually going to talk to the technical coaches, so hopefully their call centre will be more help to other customers in the future.
Now I'm left wondering what to do. Leave my systems pointed at Google ? Buy my own modem ? Wait for a patch ? Try that batch file ? Given my system is working as it is, I'm kinda loathe to do anything that might upset it, even if it is really just patched and not 'fixed'.
Have you tried using Telecoms DNS servers inputted manually instead of Googles?
122.56.237.1
210.55.111.1



