ICS trouble, please help

Status
Not open for further replies.

mephisto_007

Posts: 225   +1
Hi, guy I have this issue I can't figure it out unless you guyz help me... I want to enable Internet Connection Sharing for our wifi-billing software, I thought everything is setting up correctly but it's always turn out the Clients can't use the internet but to my amaze its can ping every site/address? (of course DNS are corrects)

How do I correct this issue help me guyz... I am really really frustrated..

Thanx in advance
 

Attachments

  • ICS.JPG
    ICS.JPG
    17.5 KB · Views: 8
this is a routing issue.

you show the ICS Comp with Nic#1+2 but also connected to router at x.1.2;
if precisely correct, then there's a thrid nic in the ICS Computer --
what's it's address?

The issues is to add or change the DEFAULT Route to be your top level router at 192.168.1.2.

PING? You're pinging what? Your client systems need to be successful when using run->cmd and entering:
if (1) fails, then so will (2), showing that access to the DNS is failing which is a requirement for all browser to access any website or email server.
 
Hi, jobeard

Clients computer can ping google.com or router no problem, but cannot use browser or application that's require internet. Our ICS comp only has 2 NICs 1 is connected to TOP router (for internet) and second NIC connect to WiFi-Repeater for clients.

When you're said what is the address for #3 NICs, is that's mean I needed to obtains the 3rd NICs for ICS comp? also by add or change the DEFAULT Route to be our top level router simply mean replacing current router IP? please clear this for me I really need this :-(
 
Clients computer can ping google.com or router no problem, but cannot use browser or application that's require internet. Our ICS comp only has 2 NICs 1 is connected to TOP router (for internet) and second NIC connect to WiFi-Repeater for clients.
Your drawing (very good btw) but IMPLIES three nics by the way it is drawn.
the NIC on the ICS, connected to the router then, must apparently be 192.168.1.x
When you're said what is the address for #3 NICs, is that's mean I needed to obtains the 3rd NICs for ICS comp?
NO!
also by add or change the DEFAULT Route to be our top level router simply mean replacing current router IP? please clear this for me I really need this :-(
NO.
hum; If all clients can ping www.google.com then the browsers should work too.
here's how ping works;
1) given a name like www.google.com, it first accesses the DNS to convert to an IP address
Code:
lookup [url]www.google.com[/url] ---> DNS
returns ip address <---- DNS
2) using the ip address, it starts the ping protocol
Code:
send icmp data ------> google's ip address
return timing data <----- google's website
if your clients get back data like
Code:
ping www.google.com

Pinging www.google.com [74.125.19.47] with 32 bytes of data:

Reply from 74.125.19.47: bytes=32 time=30ms TTL=244
Reply from 74.125.19.47: bytes=32 time=32ms TTL=244
Reply from 74.125.19.47: bytes=32 time=31ms TTL=244
Reply from 74.125.19.47: bytes=32 time=31ms TTL=244

Ping statistics for 74.125.19.47:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 32ms, Average = 31ms
(your specific address may vary)
then you should be getting website data too.

When a client enters
Code:
http://www.google.com/
in the browser address bar, what comes back?
 
Hi

The return pings from the clients is

Pinging www.google.com [74.125.45.100] with 32 bytes of data:

Reply from 74.125.45.100: bytes=32 time=600ms TTL=239
Reply from 74.125.45.100: bytes=32 time=820ms TTL=239
Reply from 74.125.45.100: bytes=32 time=530ms TTL=239
Reply from 74.125.45.100: bytes=32 time=350ms TTL=239

Ping statistics for 74.125.45.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 350ms, Maximum = 820ms, Average = 575ms

I know its sound weird but that's issue really got me on my nerve for day...

The return browser for Clients seem to be very very in slow process to accessing the sites (I could see the loading bars) but its never get there so it's just stuck there. without saying there is no internet connection or page cannot display... I' also have disable firewall on ICS as well. What seem to be the problem, I can't figure it out... arggg :(
 
>>Reply from 74.125.45.100: bytes=32 time=600ms TTL=239
>>Reply from 74.125.45.100: bytes=32 time=820ms TTL=239
>>Reply from 74.125.45.100: bytes=32 time=530ms TTL=239
>>Reply from 74.125.45.100: bytes=32 time=350ms TTL=239

OUCH! not only are the times highly variable (ie +- 300ms from best to worst), but they're 10x what is expected!

you've got a node in the path that is terrible; find it with
pathping 74.125.45.100
make sure the last two lines read
## yx-in-f100.google.com [74.125.19.47]
Computing statistics for xxx seconds...​
I suspect you'll have trouble getting to the f100.google.com due to timeouts (which will not show in the display)
 
Hi,
Here is the result... and what is the command do? do I have to run this command everytime clients connected? is it the NICs issue? and how do I resolve this problem? and thank for replying I thought you've abandon me :)


Tracing route to yx-in-f100.google.com [74.125.45.100]
over a maximum of 30 hops:
0 5eb2bc987810499 [192.168.0.15]
1 yx-in-f100.google.com [74.125.45.100]

Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 5eb2bc987810499 [192.168.0.15]
0/ 100 = 0% |
1 685ms 0/ 100 = 0% 0/ 100 = 0% yx-in-f100.google.com [74.125.45.1
00]

Trace complete.
 
Tracing route to yx-in-f100.google.com [74.125.45.100]
over a maximum of 30 hops:
0 5eb2bc987810499 [192.168.0.15]
1 yx-in-f100.google.com [74.125.45.100]​
quiet impossible! (you must have edited the data)
If true, this says your LAN is DIRECTLY attached to Google :(

this should have looked something like
Code:
  0  LTbeard [192.168.0.4]
  1  localRouter [192.168.0.1]
  2  cpe-ww-xx-yy-zz.socal.res.rr.com [ww-xx-yy-zz]
  3  gig11-14.vntrca1-rtr1.socal.rr.com [76.167.3.85]
  4  tge9-3.lamdca1-swt1.socal.rr.com [76.167.2.52]
  5     *        *     tge4-0-0.lsanca1-rtr1.socal.rr.com [76.167.2.56]
  6  ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
  7  ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
  8  72.14.197.157
  9  216.239.46.180
 10  216.239.43.125
 11  72.14.232.213
 12  209.85.253.133
 13  yx-in-f100.google.com [74.125.45.100]

[COLOR="DarkOrange"]Hop [/COLOR] RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           LTbeard [192.168.0.4]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     [COLOR="DarkOrange"]0/ 100 =  0%[/COLOR]  localRouter [192.168.0.1]
                                [COLOR="DarkOrange"]0/ 100 =  0%[/COLOR]   |
  2    9ms     0/ 100 =  0%     0/ 100 =  0%  cpe-ww-xx-yy-zz.socal.res.rr.com [ww-xx-yy-zz]
                                0/ 100 =  0%   |
  3   10ms     0/ 100 =  0%     0/ 100 =  0%  gig11-14.vntrca1-rtr1.socal.rr.com [76.167.3.85]
                                0/ 100 =  0%   |
  4   18ms     0/ 100 =  0%     0/ 100 =  0%  tge9-3.lamdca1-swt1.socal.rr.com [76.167.2.52]
                                0/ 100 =  0%   |
  5   25ms     0/ 100 =  0%     0/ 100 =  0%  tge4-0-0.lsanca1-rtr1.socal.rr.com [76.167.2.56]
                                0/ 100 =  0%   |
  6   26ms     0/ 100 =  0%     0/ 100 =  0%  ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
                                0/ 100 =  0%   |
  7   26ms     0/ 100 =  0%     0/ 100 =  0%  ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
                                0/ 100 =  0%   |
  8   24ms     0/ 100 =  0%     0/ 100 =  0%  72.14.197.157
                                0/ 100 =  0%   |
  9   24ms     0/ 100 =  0%     0/ 100 =  0%  216.239.46.180
                                0/ 100 =  0%   |
 10   91ms     0/ 100 =  0%     0/ 100 =  0%  216.239.43.125
                                0/ 100 =  0%   |
 11  103ms     0/ 100 =  0%     0/ 100 =  0%  72.14.232.213
                                0/ 100 =  0%   |
 12  103ms     0/ 100 =  0%     0/ 100 =  0%  209.85.253.133
                                0/ 100 =  0%   |
 13   98ms     0/ 100 =  0%     0/ 100 =  0%  yx-in-f100.google.com [74.125.45.100]

Trace complete.
each HOP is a system in the path to google and
we look for ANYTHING that is not 0/ 100 = 0%
which would say TCP packets are being dropped at the node.
 
Hi, I have no reason why to edit the data but this is what I got when entering the command... I just did it again and there is no long list code that look similar to your... I dont know what's should I do next...
 
ok so here is what I got from computers in the office, and I dont know why the clients still display what its seem to be even if I change it's to pathping google.com

Tracing route to yx-in-f100.google.com [74.125.45.100]
over a maximum of 30 hops:
0 diablo-01 [192.168.1.150]
1 192.168.1.2
2 124.108.51.1
3 120.136.31.133
4 124.108.48.19
5 203.113.185.245
6 203.113.158.138
7 74.125.50.245
8 72.14.233.27
9 209.85.249.236
10 216.239.43.212
11 209.85.250.126
12 * * *
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 diablo-01 [192.168.1.150]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.2
0/ 100 = 0% |
2 137ms 0/ 100 = 0% 0/ 100 = 0% 124.108.51.1
0/ 100 = 0% |
3 155ms 1/ 100 = 1% 1/ 100 = 1% 120.136.31.133
0/ 100 = 0% |
4 181ms 1/ 100 = 1% 1/ 100 = 1% 124.108.48.19
0/ 100 = 0% |
5 175ms 4/ 100 = 4% 4/ 100 = 4% 203.113.185.245
0/ 100 = 0% |
6 181ms 2/ 100 = 2% 2/ 100 = 2% 203.113.158.138
0/ 100 = 0% |
7 230ms 0/ 100 = 0% 0/ 100 = 0% 74.125.50.245
0/ 100 = 0% |
8 191ms 4/ 100 = 4% 4/ 100 = 4% 72.14.233.27
0/ 100 = 0% |
9 281ms 5/ 100 = 5% 5/ 100 = 5% 209.85.249.236
0/ 100 = 0% |
10 367ms 0/ 100 = 0% 0/ 100 = 0% 216.239.43.212
0/ 100 = 0% |
11 370ms 0/ 100 = 0% 0/ 100 = 0% 209.85.250.126
100/ 100 =100% |
12 --- 100/ 100 =100% 0/ 100 = 0% diablo-01 [0.0.0.0]

Trace complete.
 
hum; I just performed tracert to wallstreet journal (wsj.com) from LA and it is
20 hops (nodes or systems) from me and got replies in 100ms

your 300-600ms timings are bogus.

a) does this occur (ie huge delays) for ALL your clients or just one?

On the system that has ICS active
Code:
modem --- MajorSystem--(ics)--router--othersystems
eg the MajorSystem,

suggest you start diagnosis shown here

I suspect an infected proxy in the system ...
 
did you notice the inconsistency?
Code:
Tracing route to [B]yx-in-f100.google.com [74.125.45.100][/B]
over a maximum of 30 hops:
0 diablo-01 [192.168.1.150]
1 192.168.1.2
2 124.108.51.1
....
[COLOR="Red"]12 * * *[/COLOR] [COLOR="Purple"]<<ERROR[/COLOR]
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 diablo-01 [192.168.1.150]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.2
0/ 100 = 0% |
2 137ms 0/ 100 = 0% 0/ 100 = 0% 124.108.51.1
0/ 100 = 0% |
...
12 --- 100/ 100 =100% 0/ 100 = 0% [COLOR="Red"]diablo-01 [0.0.0.0][/COLOR]

Trace complete.
you did NOT reach google.com but the <<ERROR above prematurely terminated the test!
 
I don't know but all computer in Offices can access Internet ok and here is the result from another comp from Offices

Tracing route to google.com [209.85.171.100]
over a maximum of 30 hops:
0 NARY-01 [192.168.1.180]
1 192.168.1.2
2 124.108.51.1
3 120.136.31.129
4 124.108.48.19
5 203.113.185.245
6 203.113.158.138
7 74.125.50.245
8 72.14.233.27
9 209.85.249.236
10 216.239.43.212
11 216.239.46.204
12 64.233.174.127
13 209.85.251.129
14 74.125.30.6
15 cg-in-f100.google.com [209.85.171.100]

Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 NARY-01 [192.168.1.180]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.2
28/ 100 = 28% |
2 785ms 32/ 100 = 32% 4/ 100 = 4% 124.108.51.1
0/ 100 = 0% |
3 836ms 28/ 100 = 28% 0/ 100 = 0% 120.136.31.129
0/ 100 = 0% |
4 796ms 30/ 100 = 30% 2/ 100 = 2% 124.108.48.19
0/ 100 = 0% |
5 909ms 28/ 100 = 28% 0/ 100 = 0% 203.113.185.245
0/ 100 = 0% |
6 844ms 28/ 100 = 28% 0/ 100 = 0% 203.113.158.138
1/ 100 = 1% |
7 882ms 30/ 100 = 30% 1/ 100 = 1% 74.125.50.245
0/ 100 = 0% |
8 915ms 29/ 100 = 29% 0/ 100 = 0% 72.14.233.27
1/ 100 = 1% |
9 908ms 30/ 100 = 30% 0/ 100 = 0% 209.85.249.236
0/ 100 = 0% |
10 1048ms 31/ 100 = 31% 1/ 100 = 1% 216.239.43.212
0/ 100 = 0% |
11 976ms 31/ 100 = 31% 1/ 100 = 1% 216.239.46.204
0/ 100 = 0% |
12 955ms 31/ 100 = 31% 1/ 100 = 1% 64.233.174.127
0/ 100 = 0% |
13 993ms 30/ 100 = 30% 0/ 100 = 0% 209.85.251.129
1/ 100 = 1% |
14 1042ms 43/ 100 = 43% 12/ 100 = 12% 74.125.30.6
0/ 100 = 0% |
15 1021ms 31/ 100 = 31% 0/ 100 = 0% cg-in-f100.google.com [209.85.171.
100]

Trace complete.
 
I've re-setup ICS but stil the same things happen (every computers can access Internet, of course ICS has no problem either) the client computers both from WiFi and Cable can't access internet through browser or other application but all get ping replied from websites, here is another result from the client comp

C:\Users\HENG SOVICHET>pathping www.yahoo.com

Tracing route to www-real.wa1.b.yahoo.com [209.131.36.158]
over a maximum of 30 hops:
0 HENGSOVICHET-PC [192.168.0.4]
1 BAE31F9878964E8 [192.168.0.1]
2 192.168.1.2
3 124.108.51.1
4 120.136.31.129
5 124.108.48.19
6 203.113.185.245
7 203.113.158.138
8 pos13-3.cr02.hkg04.pccwbtn.net [63.218.2.173]
9 TenGE12-3.br02.sjo01.pccwbtn.net [63.218.6.194]
10 yahoo.ge5-2.br02.sjo01.pccwbtn.net [63.218.7.102]
11 ae0-p160.msr1.sp1.yahoo.com [216.115.107.57]
12 te-8-1.bas-a2.sp1.yahoo.com [209.131.32.19]
13 f1.www.vip.sp1.yahoo.com [209.131.36.158]

Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 HENGSOVICHET-PC [192.168.0.4]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% BAE31F9878964E8 [192.168.0.1]
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.2
5/ 100 = 5% |
3 254ms 8/ 100 = 8% 3/ 100 = 3% 124.108.51.1
0/ 100 = 0% |
4 277ms 10/ 100 = 10% 5/ 100 = 5% 120.136.31.129
0/ 100 = 0% |
5 296ms 7/ 100 = 7% 2/ 100 = 2% 124.108.48.19
0/ 100 = 0% |
6 310ms 9/ 100 = 9% 4/ 100 = 4% 203.113.185.245
0/ 100 = 0% |
7 301ms 10/ 100 = 10% 5/ 100 = 5% 203.113.158.138
0/ 100 = 0% |
8 350ms 10/ 100 = 10% 5/ 100 = 5% pos13-3.cr02.hkg04.pccwbtn.net [63
.218.2.173]
0/ 100 = 0% |
9 496ms 7/ 100 = 7% 2/ 100 = 2% TenGE12-3.br02.sjo01.pccwbtn.net [
63.218.6.194]
0/ 100 = 0% |
10 487ms 11/ 100 = 11% 6/ 100 = 6% yahoo.ge5-2.br02.sjo01.pccwbtn.net
[63.218.7.102]
0/ 100 = 0% |
11 479ms 5/ 100 = 5% 0/ 100 = 0% ae0-p160.msr1.sp1.yahoo.com [216.1
15.107.57]
3/ 100 = 3% |
12 507ms 9/ 100 = 9% 1/ 100 = 1% te-8-1.bas-a2.sp1.yahoo.com [209.1
31.32.19]
0/ 100 = 0% |
13 499ms 8/ 100 = 8% 0/ 100 = 0% f1.www.vip.sp1.yahoo.com [209.131.
36.158]

Trace complete.

what's the next step I should do?
 
This link has massive losses:
  • 1-2 from your router to your ISP
These links (ie the wires) between systems have small losses:
  • 6-7
    8-9
    13-14
Node 14 has heavy losses too, but you can't fix that.
Code:
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0                         NARY-01 [192.168.1.180]
                         0/ 100 = 0% |
1        0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.2
                        [color="Red"]28/ 100 = 28% |[/color]
2 785ms 32/ 100 = 32% 4/ 100 = 4% 124.108.51.1  [B]<<would appear to be your ISP connection[/B]
                         0/ 100 = 0% |
3 836ms 28/ 100 = 28% 0/ 100 = 0% 120.136.31.129
                         0/ 100 = 0% |
4 796ms 30/ 100 = 30% 2/ 100 = 2% 124.108.48.19
                         0/ 100 = 0% |
5 909ms 28/ 100 = 28% 0/ 100 = 0% 203.113.185.245
                         0/ 100 = 0% |
6 844ms 28/ 100 = 28% 0/ 100 = 0% 203.113.158.138
                         1/ 100 = 1% |
7 882ms 30/ 100 = 30% 1/ 100 = 1% 74.125.50.245
                         0/ 100 = 0% |
8 915ms 29/ 100 = 29% 0/ 100 = 0% 72.14.233.27
                         1/ 100 = 1% |
9 908ms 30/ 100 = 30% 0/ 100 = 0% 209.85.249.236
                         0/ 100 = 0% |
10 1048ms 31/ 100 = 31% 1/ 100 = 1% 216.239.43.212
                         0/ 100 = 0% |
11 976ms 31/ 100 = 31% 1/ 100 = 1% 216.239.46.204
                         0/ 100 = 0% |
12 955ms 31/ 100 = 31% 1/ 100 = 1% 64.233.174.127
                         0/ 100 = 0% |
13 993ms 30/ 100 = 30% 0/ 100 = 0% 209.85.251.129
                         1/ 100 = 1% |
14 1042ms 43/ 100 = 43%  [color="Red"]12/ 100 = 12%[/color] 74.125.30.6
                         0/ 100 = 0% |
15 1021ms 31/ 100 = 31% 0/ 100 = 0% cg-in-f100.google.com [209.85.171.100]
your total losses exceed 50%
Recommendation:
  1. Replace all wires from the phone jack to the ADSL modem and to the 192.168.1.2 router.
  2. update the firmware in that router
  3. move the A/P to directly connect to the router and bypass ICS altogether
Monitor the response time from node 1-2, 785ms is just terrible!
 
Totally agree with jobeard.

Also, another way to look at these results is that approx. 75% of the latency is between you and your ISP!!!

I also note that you're originating in Southeast Asia which may or may not be relevant to the quality of your phone lines but it issue is certainly something you should address with your ISP
 
Monitor the response time from node 1-2, 785ms is just terrible!
Here's how
run -> cmd /k ping -t 124.108.51.1​
just let it run and watch the timings change.
On a good link, they should not change more the +-1%
results from Los Angeles, CA, U.S.A
Pinging 124.108.51.1 with 32 bytes of data:

Reply from 124.108.51.1: bytes=32 time=497ms TTL=242
Reply from 124.108.51.1: bytes=32 time=503ms TTL=242
Reply from 124.108.51.1: bytes=32 time=497ms TTL=242
Reply from 124.108.51.1: bytes=32 time=494ms TTL=242
...
Reply from 124.108.51.1: bytes=32 time=499ms TTL=242
Reply from 124.108.51.1: bytes=32 time=506ms TTL=242
Reply from 124.108.51.1: bytes=32 time=501ms TTL=242
Reply from 124.108.51.1: bytes=32 time=495ms TTL=242
Reply from 124.108.51.1: bytes=32 time=495ms TTL=242
Reply from 124.108.51.1: bytes=32 time=494ms TTL=242
Reply from 124.108.51.1: bytes=32 time=495ms TTL=242
Reply from 124.108.51.1: bytes=32 time=500ms TTL=242
This makes the point that the ISP at this address STINKS!
as an example of another long-haul from L.A. to Milan, IT (18 hops)
18 188 ms 189 ms 187 ms ae-4-4.car2.Milan1.Level3.net [4.69.133.137]

Pinging 4.69.133.137 with 32 bytes of data:
Reply from 4.69.133.137: bytes=32 time=191ms TTL=243
Reply from 4.69.133.137: bytes=32 time=188ms TTL=243
Reply from 4.69.133.137: bytes=32 time=190ms TTL=243
Reply from 4.69.133.137: bytes=32 time=189ms TTL=243
Reply from 4.69.133.137: bytes=32 time=188ms TTL=243
Reply from 4.69.133.137: bytes=32 time=190ms TTL=243
Reply from 4.69.133.137: bytes=32 time=187ms TTL=243
Reply from 4.69.133.137: bytes=32 time=190ms TTL=243
Reply from 4.69.133.137: bytes=32 time=189ms TTL=243
Reply from 4.69.133.137: bytes=32 time=190ms TTL=243
Reply from 4.69.133.137: bytes=32 time=187ms TTL=243​
Notice from best (187) to worst(191), is a change of only 4ms​

I fully appreciate that COST to you may be very expensive for any Internet access,
but suggestion you google for satellite isp providers as an alternative service.
 
I am consider of changing our current ISP but before I do so, I want to ask you is it possible that the issue I am encounting with caused by Hardware (eg: NICs, Router, Switch, Computers itself) or Software or the way I've setup the network (I've had 2 Switchs pickiback each other) and cause delay or lag? because I dont want to make the same mistake after we change to a new ISP. Neverthless thank you very much for your times and effort to help, I' truly appreciate that..
 
I think the simplest test is to connect one computer directly to the ADSL Modem. Then run the same tests on the computer.

If you still have the same latency issues, then the problem is the ADSL Modem, your ISP, anything in between the two. And in that case, is worth reporting the problem to ISP as for all we know it might simply be a bad ADSL modem (for example, that need be replaced)
 
it could be your Wi-Max device. Just yesterday a friend had his cable modem fail and
it had very similar symptoms --- food for thought
 
Hi, I've notice a very very steady ping reply from our ISP gateway (124.108.51.1) between 40ms to 50ms but if I try to access internet either using browser or application require internet than the ping reply will spike to 400ms to 1500 ms... any idea what is goin on?

How does your friend fix this? by replacing a new device or just simply remove it or switch off the option!?
 
Status
Not open for further replies.
Back