[cmk]

Ok chaps here goes.

I'm the one who had the problem. The engineer arrived yesterday with a new CM. One of those little blue efforts. He plugged it all in and tested it but nothing was doing. He plugged in his laptop and said it was working fine but I saw no evidence of this. He told me that NTL were remote updating the CMs and it looks like mine was done early hours Wednesday morning and it had gone haywire. Nice of them to tell me they were doing this in the first place mind.

He was happy the connection was working and it was a local issue. It seemed to be the case but before the update it was fine so as I see it what NTL did knackered things up somehow. I spoke to tech support again who suggested a winsock issue. I called a mate later that night who was checking out the error codes from ipconfig which did suggest this to be the case. I removed the winsock and winsock2 references from the registry and also uninstalled TCP/IP. Upon reinstalling and checking Ipconfig the net fired up at about 10pm last night.

Now I'm not overly sure why this all happened but it does seem a little coincedental that the engineer suggested CM updates were going on and mine gets fried at the same time. Also, and it would seem from other posts on here that it's a standard thing, six days is nothing short of ludicrous for a call out. I would expect two days max from decent support. £60 a month to NTL and that level of call out? It's not exactly a selling point type feature is it. I may be making a way out comparison but if we'd have suggested a six day call out where I used to work we'd have had the rollocking of our lives and been lucky to be in a job but I guess that's the difference between decent customer relations and NTL.

I know some of you work for then and will argue against the above which is fine. The main thing for me is the timescale. Six days is shoddy no matter what anyone says or how it's dressed up. I expect a decent service if things go wrong. Things did and I didn't get one.