Abysmal Orcon performance

Forums › Orcon and iServe › Abysmal Orcon performance

1 | 2 | 3

Jase2985

8955 posts

Uber Geek

Lifetime subscriber

# 1408107 17-Oct-2015 06:58

why are you testing via wifi? eliminate all the variables with your control

hyperman

412 posts

Ultimate Geek

# 1408126 17-Oct-2015 08:33

I am not sure if it's just a modem thing and feel free to correct me if I am wrong

The attenuation figures look weird to me

14db up and 37db down!

The views expressed by me are not necessarily those of my employer

Noodlepiss

15 posts

Geek

# 1408130 17-Oct-2015 09:10

hyperman: I am not sure if it's just a modem thing and feel free to correct me if I am wrong

The attenuation figures look weird to me

14db up and 37db down!

It is weird, but my PC was off and I had just got inside from street drags and no other devices in the house were on. The router is in my bedroom- I've posted a picture above showing similar figures from my PC too.
Man this is so frustrating, I don't want to pay for service like this.

Noodlepiss

15 posts

Geek

# 1408131 17-Oct-2015 09:13

Jase2985: why are you testing via wifi? eliminate all the variables with your control

Because I've tested countless times via my PC. No other devices were online (or even turned on) in the household, it was like 3:30am haha I'd just got home from street drags.
I feel testing from my phone (iPhone 5S, 32GB) would put something else to the table to eliminate the chances of a faulty network service or adapter on my PC.
The performance is still abysmal. Same or similar stats to what I get on my PC tests.

Nebbie

457 posts

Ultimate Geek

Trusted

# 1408174 17-Oct-2015 11:47

Noodlepiss: How is this acceptable? For $100/month?

With latency of about 1156ms I'm surprised the speedtest even connected.
There's several problems that could cause this:

1.) wifi....
2.) router (or any bridge in between)
3.) Faulty master filter
4.) Faulty exchange port where its a Chours ISAM or a Orcon MSAN

Run a ping to the router and see what you get... Latency should be 1ms or less on Ethernet and no more than 10ms on Wifi the more traffic you and other people of the same wifi channel the slower the speeds will go.

"CMD --> ping -n 10 192.168.1.1 (Assuming the router is 182.168.1.1)
"CMD --> tracert -d 8.8.8.8 (-d will not resolve the hostnames makes it tidy for pasting here)

Run these when the network is doing no traffic... I never trust speedtest's these days I only use when I know there's no issues and want to know the total throughput speeds. Using it to troubleshoot speed issues if you already know your speed is slow is a waste of time.

First lets see those pings/traceroutes first.

---------------------------------------------------------------
Nebukadnessar

Noodlepiss

15 posts

Geek

# 1408247 17-Oct-2015 14:33

Nebbie:
Noodlepiss: How is this acceptable? For $100/month?

With latency of about 1156ms I'm surprised the speedtest even connected.
There's several problems that could cause this:

1.) wifi....
2.) router (or any bridge in between)
3.) Faulty master filter
4.) Faulty exchange port where its a Chours ISAM or a Orcon MSAN

Run a ping to the router and see what you get... Latency should be 1ms or less on Ethernet and no more than 10ms on Wifi the more traffic you and other people of the same wifi channel the slower the speeds will go.

"CMD --> ping -n 10 192.168.1.1 (Assuming the router is 182.168.1.1)
"CMD --> tracert -d 8.8.8.8 (-d will not resolve the hostnames makes it tidy for pasting here)

Run these when the network is doing no traffic... I never trust speedtest's these days I only use when I know there's no issues and want to know the total throughput speeds. Using it to troubleshoot speed issues if you already know your speed is slow is a waste of time. First lets see those pings/traceroutes first.

Hey man, cheers for the response.
Completed those tasks, here are the results.
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ping -n 10 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Windows\system32>tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 20 ms 19 ms 19 ms 121.98.9.141
4 20 ms 19 ms 19 ms 121.99.12.0
5 20 ms 19 ms 19 ms 121.99.1.34
6 19 ms 19 ms 20 ms 121.99.1.35
7 43 ms 42 ms 42 ms 72.14.243.237
8 42 ms 42 ms 42 ms 72.14.243.236
9 43 ms 42 ms 43 ms 216.239.40.233
10 43 ms 42 ms 42 ms 216.239.41.3
11 43 ms 42 ms 43 ms 8.8.8.8

Trace complete.

C:\Windows\system32>

I can't see the router being a problem, as I've tested another router (Asus DSL N66U (only 3 weeks old at the time, too)) and had the same results, as well as the same erratic performance.
I hope that data is useful for you!

Cheers,
Alistair

Nebbie

457 posts

Ultimate Geek

Trusted

# 1408300 17-Oct-2015 17:20

Noodlepiss:

I can't see the router being a problem, as I've tested another router (Asus DSL N66U (only 3 weeks old at the time, too)) and had the same results, as well as the same erratic performance.
I hope that data is useful for you!

Cheers,
Alistair

ok cool, good Router :) replaced recently good.
All the pings looks good was the issues at the time of the tests?

Can you do one more thing...
Run a ping test and do a speed test at the same time? (I'm expecting some rise but want to see it while a speedtest is running)

What I'm trying to get here is if your latency shoots though the roof when a small amount of data is transferred Usually indicates packet loss for larger frames possibly due to a faulty port at the exchange.

You got a bastard of a fault here :)

---------------------------------------------------------------
Nebukadnessar

airdale

11 posts

Geek

# 1412993 23-Oct-2015 19:14

I am having similar problems and also in a rural location.

Orcon's response has been nothing short of abysmal. At one point they tried to tell me that a 4 hour disconnection was an acceptable service level!

Now they are trying to tell me that the problem is because I am not using a filter on the line and the disconnections are occurring when the phone is in use. Nice theory but for the fact that I am on a naked connection!

1 | 2 | 3