cancel
Showing results for 
Search instead for 
Did you mean: 

ISDN Service delays too

N/A

ISDN Service delays too

ISDN also slow...maybe your problems are not ADSL-specific?

My ISDN line has been terribly slow for the last two weeks and intermittently times out on web pages. Problems with DNS timeouts were solved with a new set of name servers, but web pages are extremely slow at times and the system becomes totally unusable. After five years of ok service, problem began several weeks ago with delays in late afternoon/early evening which I ascribed to busy hour for services, but now occurs better part of the business day as well. Reporting using web page seems odd for this type of service problem, when it occurs there is no access to reporting! Below are details from (admittedly short) default report, but I'm reporting while I have some access.

Traceroute Results: View Traceroutes
Traceroute Time (24 Hour): 08:15 to 08:16
Traceroute Duration: 1 minutes
Traceroute Packet Size: 64 bytes
Exchange: st. margarets
Problem: Permanently Slow Web Browsing (But everything else is fine)
Duration of Problem: More than 1 week
Minimum Speed Achieved On PlusNet Speedtest: 61.1 kbps
Maximum Speed Achieved On PlusNet Speedtest: 62.8 kbps
Average Speed Achieved On PlusNet Speedtest: 61.95 kbps
Account: ADSL Office 500 (20:1)
IP Block Size: Single (default)
Ticket Number: None
Additional Information: This is ISDN service Biz +.
BT have tested line ok (also for noise)
9 REPLIES
Community Veteran
Posts: 14,469
Registered: 30-07-2007

ISDN Service delays too

Your tracert appears strange with not being able to get the DNS name for IP addresses, at least some of your route should be resolvable.

I'm wondering if you still have a DNS issue? What DNS servers are you currently using?
N/A

ISDN Service delays too

Heres another traceroute with losses near 1000 this morning. Also appended are the DNS servers. I get very long response times from pings on www.mirror.ac.uk when using the address (194.83.57.15) that can be over 2 seconds (see below), so I don't think DNS is the problem.

C:\Documents and Settings\Jack L. King>ping 194.83.57.15

Pinging 194.83.57.15 with 32 bytes of data:

Reply from 194.83.57.15: bytes=32 time=2377ms TTL=245
Reply from 194.83.57.15: bytes=32 time=1193ms TTL=245
Reply from 194.83.57.15: bytes=32 time=941ms TTL=245
Reply from 194.83.57.15: bytes=32 time=889ms TTL=245

Ping statistics for 194.83.57.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 889ms, Maximum = 2377ms, Average = 1350ms

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| No response from host - 100 | 2412 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2411 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2411 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2411 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2411 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2411 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2411 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2411 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2411 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2411 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2411 | 0 | 0 | 0 | 0 | 0 |
| newton.mirror.ac.uk - 1 | 2411 | 2397 | 50 | 79 | 2243 | 60 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )


Username genoauk

We are pleased to be able to inform you that a member of our Customer Support
Centre has now returned ticket number [ 12066969 ] to yourself.

The following comment was added to the ticket
Dear Customer



If you specify the DNS addresses of :-



212.159.6.9

212.159.13.50



This should help



Regards,

link:CSA Removed
Community Veteran
Posts: 14,469
Registered: 30-07-2007

ISDN Service delays too

Yes, very long ping times but it is still strange that the tracert does not work - unless for some reason it is blocked on ISDN routes.

What are your ping times to portal.plus.net, www.bbc.co.uk and www.mirror.ac.uk?

My ISDN knowledge is a bit rusty but have you tried using the other 64K line on the ISDN termination box (if that is actually possible) or removed your cable from your TA and ISDN box and reconnected. Just a wild idea but you never know.

This is one for PlusNet/BT to investigate further I think, so you will need to raise a ticket and copy the tracert details and the ping times you have performed and mention any other info like the BT line test and see what they can find.
N/A

ISDN Service delays too

Has any aspect of your hardware changed in any way prior to this happening?

Have you had any power cuts or storms in recent times?

Do you have any firewall active at all on the system?
N/A

ISDN Service delays too

Ping time are long (can be more than 2000 ms) examples shown below. Doesn't make much difference if ip addresses are used (nor does it make a difference useing tracert -d, so I don't think name servers are the problem.

I've gone through the ticketing, winmtr stuff and made little progress so far. I get the same sort of 'check your modem' kinds of things and talk to BT. I've done that and they've tested the line. Also there is no problem with the voice over the line (remember its ISDN).

The problem becomes most severe with packet loss over 78% during peak times (e.g. 1000 am) as shown below:

Here is a traceroute from 10:18 on 15 June with 78% of the 500 packets failing!

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| No response from host - 100 | 501 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 500 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 500 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 500 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 500 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 500 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 500 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 500 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 500 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 500 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 500 | 0 | 0 | 0 | 0 | 0 |
| hubble.mirror.ac.uk - 78 | 500 | 112 | 50 | 603 | 2593 | 951 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )

Finally, I must say that I've been using the service for many years and this problem has grown proceedingly worse over the last several weeks. The transmission test shows 61k throughput and BT claims no noise on the line (which this would tend to support). I am using the same equipment and have no problems whatsoever sometimes, so I think a hardware malfuntion is unlikely.




Pinging www.mirror.ac.uk [194.83.57.15] with 32 bytes of data:

Reply from 194.83.57.15: bytes=32 time=2017ms TTL=246
Reply from 194.83.57.15: bytes=32 time=569ms TTL=246
Reply from 194.83.57.15: bytes=32 time=61ms TTL=246
Reply from 194.83.57.15: bytes=32 time=654ms TTL=246

Ping statistics for 194.83.57.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 2017ms, Average = 825ms

C:\Documents and Settings\Jack L. King>time
The current time is: 10:07:20.33
Enter the new time:

C:\Documents and Settings\Jack L. King>ping 194.83.57.15

Pinging 194.83.57.15 with 32 bytes of data:

Reply from 194.83.57.15: bytes=32 time=816ms TTL=246
Reply from 194.83.57.15: bytes=32 time=883ms TTL=246
Reply from 194.83.57.15: bytes=32 time=950ms TTL=246
Reply from 194.83.57.15: bytes=32 time=385ms TTL=246

Ping statistics for 194.83.57.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 385ms, Maximum = 950ms, Average = 758ms

C:\Documents and Settings\Jack L. King>ping 194.83.57.15

Pinging 194.83.57.15 with 32 bytes of data:

Reply from 194.83.57.15: bytes=32 time=860ms TTL=246
Reply from 194.83.57.15: bytes=32 time=933ms TTL=246
Reply from 194.83.57.15: bytes=32 time=1793ms TTL=246
Reply from 194.83.57.15: bytes=32 time=1775ms TTL=246

Ping statistics for 194.83.57.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 860ms, Maximum = 1793ms, Average = 1340ms
N/A

ISDN Service delays too

Further too my questions above. Have you attempted the same tests when using the 0845 dialup number.

Although the argument that you shouldn;t need to pay to perform tests is true, they can and do help.

The 0845 equipment is different to that of the 0808 equipment, and can help rule out ISDN issues completly.
N/A

ISDN Service delays too

Yes, I've been working on the problem for several weeks now and of course one of the original suggestions from PlusNet was to try the 0845 number which I did for a short time without any improvement in service. I was also given several other 'suggestions' such as my modem, my drivers, my .... to check and told that no one else is having problems, so it must be something in my equipment.

Frankly, it seems hard to imagine that an ISDN malfunction could create such long delays in pings, traceroutes and web pages without any problem with emails or telephone voice service using the same ISDN line, unless you suspect a problem in your 0808 equipment and not the BT ISDN service to me. If so, do you not have any way of testing this equipment's throughput? I don't have a problem paying for testing my equipment (such as BT or the systems here) as I've spent a good amount of my time already following suggestions and providing diagnostic information, but I'm sure you understand I would have a problem spending any significant amount testing your 0808 service equipment.
N/A

ISDN Service delays too

The 0808 equipment is actualy BT's.

ISPs like PlusNet purchase ports on the Friaco platform. Buying 50 ports means 50 maximum concurrent connections (from different users).

As such, it is BT that manages this equipment.

PlusNet (possibly another supplier, never asked. I mainly deal with DSL) host the 0845 number themselves, and I know they have better control over this.

The fact this happens on both 0808 & 0845 sugests this is not a generic issue in the 0808, or 0845 platforms, but somthing related more specificly to your circuit.

This can be anything from exchange side, the cable, the HH point your end, your equipment or software/drivers on the computer.

The real problem here is that the onus is on your to proove that it isn't your own eqipment. Regardless of how much you pay BT or PlusNet, you are responsible for your own equipment.

Normaly, the only real way to disproove issues here, is to use other equipment, using your line and your dialup accounts, to proove they fail too.

Once you have done this, PlusNet could possibly get BT to investigate because of the 0808 failure. However, BT can and will charge you direct, if they are able to test without issue from your premesis.
Community Veteran
Posts: 14,469
Registered: 30-07-2007

ISDN Service delays too

Just seen another ISDN user post some trace info and they can resolve names from IP addresses - see it here

Can you try using windows tracert command to www.mirror.ac.uk to see what it looks like. If it is still not resolving DNS lookups then that may indicate an issue to sort out. Whether this is a local issue or not I can't tell.

I would check your DNS configuration and maybe try some the these other ones to see if the tracert come out properly:

212.159.13.49
212.159.13.50
212.159.6.9
212.159.6.10
212.159.11.150
212.159.13.150

All 6 are responding well to DNS queries.