UTVip XL - Atrocious!

Páid

Same here.

It has definately degraded in the last week or so for me but I don't mind that much. I can bear it until I get ADSL.

Any semi flat rate product is bound to have teething problems and I imagine UTV are having to cope with a surge of new users which is bound to cause problems.

DirksDiggler, the only advice I can give is to move your modem to the furthest PCI slot away from your graphics card. In some cases the cooling fan on the graphics card can cause RF problems which may affect your connection speed.

gonker

I have been having problems too. Not recognizing my password not connecting and frequent disconnects. I have two computers and both are experiencing the same problems. I connect at between 12000kps and 19000kps but then i am in the middle of nowhere in laois but only about 2 miles from the N7 on a dacs line.:( Spoke to utv but they said it was a software conflict between my computer and their software?

gonk

Páid

I've seen that before.

A friend of mine had a modem that "heard" a busy signal when it was clearly the ISP's server part of the handshake (the squealing noise for 20 seconds or so when you dial up). The solution was to find the AT commands that the modem would respond to and disable busy signals on the modem. Then it worked.

I doubt if you have a problem like that but I could be wrong. More than likely though its your line.

dub45

Is it not a bit of a coincidence that all these problems have occurred around the same time as the introduction of a new product. And if the 'solution' is that the problem is at the customer's end why were the varying problems not occurring before now?

Martin-UTVi

Is it not a bit of a coincidence that all these problems have occurred around the same time as the introduction of a new product. And if the 'solution' is that the problem is at the customer's end why were the varying problems not occurring before now?

We are looking into these problems. Whilst we have launched a new product/service the backend systems within our own network have not changed drastically. Customers who have migrated from UTVIP to UTVIPXL are also more than likely to still be terminating on the same hardware within our POP So we're investigating these issues at a few different levels - obviously the fact that its only affecting some customers and these are not necessarily restricted to a certain location makes this a bit more difficult.

We obviously appreciate the feedback here and I wonder if users having this problem could do a bit of testing for us. Are you still experiencing the problem when dialled into 1890 927171 (username = testie password = testie)? Please feed this back to me at martin@u.tv

TIA

Nitrox

I have had a lot of problems connecting to the old 30 Euro a month service lately, i wonder if this is because of this new xl thing. Anyway i have decided to leave while i am still fairly happy as UTV has no unlimited offer like Netsource, so thx. for a good time UTV, just wish you had continued to offer the best, but i gues it is hard to always be the best.
Netsource here i come (If Ripwave is not rolled out within the next 2 months that is)

Ps. i Gues some would wonder why i continue to pay 30 euro a month when i could get more hours for 5 euro less, well, i just hope u all know that by changing to Xl you also get a new 3 month minimum contract, and i just dont want to get stuck with that right now, i want BB

moshpit77

I guess it's obvious why the 3 month contract was put in there now, even for those who were already UTV IP customers. They envisaged these problems and didn't want people deserting them.

RicardoSmith

My disconnects have reduced a lot in the last week, and I haven't changed anything so somebody somewhere is doing something. In fairness you'd expect some teething problems. But some of the responses that people have had from support are a little poor.

eth0_

Originally posted by DirksDiggler
.His solution was to (a) download a new dialer which I done and nothings changed (b) buy a new modem (for f*ck sake!) and (c) reformat my 80GB hard drive.

I don't for one minute believe someone in UTV support advised you to format your computer.

I know UTV are having problems right now with pings, but that's something they're trying to get their provider, Energis to fix...

Chowley

Oh but Everyone at UTV are great at what they do, you couldnt possibly get one idiot working there.
I think its very possible unfortunately, you could get someone like that in any product support.

BobbyBean

On a 56K I get the following

Reply from 217.114.166.147: bytes=32 time=80ms TTL=49
Reply from 217.114.166.147: bytes=32 time=92ms TTL=49
Reply from 217.114.166.147: bytes=32 time=86ms TTL=49
Reply from 217.114.166.147: bytes=32 time=87ms TTL=49

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 92ms, Average = 86ms

I can connect every time 56K or ISDN without any problems, might have had to re-connect once or twice after dialup cos of somthing strange but all in all very good service.


Bobby

dub45

I dont think anyone disputes that UTV provide a good service and thats why they have generated such loyalty. However lately there have been problems and in certain instances they are not being dealt with well.

Most people have had good service but now when difficulties arise those peoples modems or whatever are being blamed. As I say above it was alright before why are there problems now?

My own gut feel is that at the moment UTV have bitten off more than they can chew and their customers are suffering.

The Clicksilver thing has been a minor disaster from start to now.

And again as I say elsewhere it takes a long time to build a reptutation but a very short time to lose it.

UTV in most people's view set very high standards and therefore I suppose even a relative fall from excellence is felt very quickly however if UTV offer products it is up to them as a business to ensure that they have the proper resources (whether human or technical) in place to deliver. People's good will and patience only last so long.

Delphi91

Here are mine:

Pinging 217.114.166.147 with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=336ms TTL=49
Reply from 217.114.166.147: bytes=32 time=312ms TTL=49
Reply from 217.114.166.147: bytes=32 time=285ms TTL=49
Reply from 217.114.166.147: bytes=32 time=290ms TTL=49

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 285ms, Maximum = 336ms, Average = 305ms


I used to be able to connect at around 42-45k - now I'm getting 20-36k (connecting at 28.8k at the mo). Been having all sorts of problems for the last 10 days or so - support didn't seem to be able to solve problem. I used to connect at 44k, but then the connection ground to a halt despite being connected. Took a drastic step and changed modem (just in case) and while I can get a working connection, its speed is crap. Might as well have a carrier pigeon!

Mike

andrew163

Originally posted by Delphi91
I used to be able to connect at around 42-45k - now I'm getting 20-36k (connecting at 28.8k at the mo). Been having all sorts of problems for the last 10 days or so - support didn't seem to be able to solve problem. I used to connect at 44k, but then the connection ground to a halt despite being connected. Took a drastic step and changed modem (just in case) and while I can get a working connection, its speed is crap. Might as well have a carrier pidgeon!

Mike

:eek: wow

Are these speeds only happening over UTV? That seems like a very big speed difference, and it looks more like a line problem then an ISP problem.......

*cough*pairgain

Delphi91

Originally posted by andrew163
:eek: wow

Are these speeds only happening over UTV? That seems like a very big speed difference, and it looks more like a line problem then an ISP problem.......

*cough*pairgain

Yes, they are. I've tried another ISP (elive) and I get 45-49k everytime.....

I didn't think it would be a line problem if I could get such speeds on elive, but had problems with UTVipXL. Arising from another problem with my line (only since last Wednesday), I got Eircom to check the line and its fine according to them. But this problem has been around for a week prior to that. Its beginning to p**s me off big time now.

Mike

RicardoSmith

Have to say I've noticed in the past that some ISP's were noticeably faster had a signifcantly more stable line connection than others. The differences have to be at the ISP end since thats the only variable.

I have noticed that UTVip XL connection has been greatly improved for me over the last couple of weeks. Speeds are 44k, (were 42k) and disconnects are down to occasionally (were every 20mins) and I connect pretty much the first time I try. The only change I've made is to download the newer dialler when I've discovered a new ones been made available.

Incidentally be nice if UTVip would email or otherwise notify if a new dialler is posted since I've only been doing it when someone in the forums here has siad theres a newer one. Maybe its the same one each time though!

I haven't had time to play with my settings or try those other settings Martin posted. But I will once time allows. The service is now acceptable for me, but I don't assume that because I'm not having any problems that no one else is. Thats just dumb.

oscarBravo

Originally posted by RicardoSmith
The differences have to be at the ISP end since thats the only variable.

Hm. Not the only variable: the other is the fact that UTVipXL is being carried on an Eircom FRIACO port. Is there any possibility that this is introducing a problem somewhere along the line?

Chowley

Im having serious trouble with IOL Free, since last Thursday.

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>ping boards.ie -t

Pinging boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=532ms TTL=55
Reply from 217.114.166.147: bytes=32 time=328ms TTL=55
Reply from 217.114.166.147: bytes=32 time=140ms TTL=55
Reply from 217.114.166.147: bytes=32 time=140ms TTL=55
Reply from 217.114.166.147: bytes=32 time=422ms TTL=55
Reply from 217.114.166.147: bytes=32 time=219ms TTL=55
Reply from 217.114.166.147: bytes=32 time=141ms TTL=55
Reply from 217.114.166.147: bytes=32 time=516ms TTL=55
Reply from 217.114.166.147: bytes=32 time=312ms TTL=55
Reply from 217.114.166.147: bytes=32 time=140ms TTL=55
Reply from 217.114.166.147: bytes=32 time=140ms TTL=55
Reply from 217.114.166.147: bytes=32 time=406ms TTL=55
Reply from 217.114.166.147: bytes=32 time=203ms TTL=55

Ping statistics for 217.114.166.147:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 140ms, Maximum = 532ms, Average = 279ms

This is really bad. Im having real trouble connecting at 50k which is optimum.It keeps connecting at 52k which is always spiky but even worse now.

Anyone else having these troubles??

Martin-UTVi

As mentioned before we're trying to narrow down the problems some people are seeing with their connections. If possible, please email me with your name and the telephone number you are dialing from.

TIA

OHP

This is on ISDN.

C:\>ping boards.ie

Pinging boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=120ms TTL=49
Reply from 217.114.166.147: bytes=32 time=102ms TTL=49
Reply from 217.114.166.147: bytes=32 time=101ms TTL=49
Reply from 217.114.166.147: bytes=32 time=117ms TTL=49

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 101ms, Maximum = 120ms, Average = 110ms

Seem's ok to me but for gameing it's



OHP

corkey

[217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=102ms TTL=49
Reply from 217.114.166.147: bytes=32 time=107ms TTL=49
Reply from 217.114.166.147: bytes=32 time=106ms TTL=49
Reply from 217.114.166.147: bytes=32 time=100ms TTL=49

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 107ms, Average = 103ms

:eek:

OHP

Using Oceanfree:

C:\>ping boards.ie

Pinging boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=63ms TTL=55
Reply from 217.114.166.147: bytes=32 time=58ms TTL=55
Reply from 217.114.166.147: bytes=32 time=61ms TTL=55
Reply from 217.114.166.147: bytes=32 time=61ms TTL=55

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 63ms, Average = 60ms

Perfect for gameing


OHP

sci0x

Using UTVip XL

Pinging boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=213ms TTL=49
Reply from 217.114.166.147: bytes=32 time=202ms TTL=49
Reply from 217.114.166.147: bytes=32 time=192ms TTL=49
Reply from 217.114.166.147: bytes=32 time=190ms TTL=49

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 190ms, Maximum = 213ms, Average = 199ms

Eurorunner

Using UTVip with 56k modem...


Pinging www.boards.ie [217.114.166.147] with 32 bytes of data:

Reply from 217.114.166.147: bytes=32 time=154ms TTL=49
Reply from 217.114.166.147: bytes=32 time=596ms TTL=49
Reply from 217.114.166.147: bytes=32 time=162ms TTL=49
Reply from 217.114.166.147: bytes=32 time=164ms TTL=49

Ping statistics for 217.114.166.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 154ms, Maximum = 596ms, Average = 269ms

sceptre

<cough>
Please, everyone don't post pings.

I'm not even using UTV and I'm aware in a pretty precise way of the differences between UTv and Oceanfree with or without ISDN and the rather higher pings on UTV on both analogue 56k and ISDN compared to some competitors. We've had a few examples and that's fine and dandy. The last thing (really - the last thing) I want to do is come back tomorrow and find hundreds (or even any more) ping reports posted as it wouldn't add anything to the discussion.

I may sound crabby - I'm not really. After the first few there's absolutely nothing any more can add to the general discussion. If you're getting pings of one and a half seconds I suppose that would be new but that's more a technical issue for the UTV techies and whoever calls to take your phone line out of the puddle it's lying in.


ta muchy.

daveg

Is there any updates on the engaged line/dropping connection on UTV. Myself I find it very difficult to dial in an evening. Getting fed up of hearing that bloody engaged tone.... :mad:

spongebob

that may be your modem. Try putting x1, before the UTV number in the dialler or putting a , after the number itself.

tell us if that helps or not !

M

daveg

Thanks for the reply muck and I'll try it tonight but to be honest I doubt it will help as I can connect with IOL no problem and sometimes I dial straight in with UTV.

spongebob

a comma after the number gets the modem around some funny noises that may be issued by the answering system. It tells the modem to pause 2 seconds between dialling and negotiating.

The x1, bit (at the beginning) is probably unnecessary on reflection.

Sometimes modems 'hear' a noise and misinterpret it (say as an engaged tone) . My suggestion should therefore be irrelevant if you use ISDN but ya never know. Tell us if it improves anything.

M

trap4

Well I'm still suffering the same problems too and it's nothing to do with my modem as I had much fewer problems with my previous UTVip account