Neka iskustva sa kbcnet?

@dzonihsv

Da li si probao Kotez_4? Dodushe i nije bilo bash vreme za okretanje antene...

Potpis

We are Borg. We shall assimilate you.
RESISTANCE IS FUTILE!

Asus P6T Deluxe V2
Intel Core i7 965 3.2GHz
OCZ 3x2GB DDR3 PC3-12800 Flex EX Low Voltage Triple Channel
2x1000GB Spinpoint F1
ATI Radeon HD5970
Lian Li PC-P80R
Samsung T240

www.me2everyone.com/213043

Antenu sam ja okrenuo pre skoro mesec dana i to bas na Kotez_4. Radilo je sve ok skoro ceo mesec i onda je pocelo ovo sto i sam vidis.

Sada sam jos uvek nakacen na Kotez_4 jer na Kotez_2 se nema smisla kaciti, na tom AP-u je krkljanac (zagusenje) za sve pare.

@Sleepless_mind

staje ovo sa ovim radijus serverom?
malo po malo pa je nedostupan da autorizuje logovanje
i veceras je isto nekih 20 min
pre par dana je bilo isto pa sam ukljucio dijagnostiku i lepo se videlo da je timeout u pokusaju komunikacije

E bem ti ping. Daj kbc resavajte to

hmm u jakovu je ping standardni skoro

C:\Users\Administrator>ping www.beotel.net -n 10

Pinging www.beotel.net [194.106.162.55] with 32 bytes of data:
Reply from 194.106.162.55: bytes=32 time=5ms TTL=57
Reply from 194.106.162.55: bytes=32 time=5ms TTL=57
Reply from 194.106.162.55: bytes=32 time=3ms TTL=57
Reply from 194.106.162.55: bytes=32 time=6ms TTL=57
Reply from 194.106.162.55: bytes=32 time=5ms TTL=57
Reply from 194.106.162.55: bytes=32 time=4ms TTL=57
Reply from 194.106.162.55: bytes=32 time=23ms TTL=57
Reply from 194.106.162.55: bytes=32 time=8ms TTL=57
Reply from 194.106.162.55: bytes=32 time=6ms TTL=57
Reply from 194.106.162.55: bytes=32 time=9ms TTL=57

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

C:\Users\Administrator>ping www.google.com -n 10

Pinging www.l.google.com [64.233.183.103] with 32 bytes of data:
Reply from 64.233.183.103: bytes=32 time=44ms TTL=236
Reply from 64.233.183.103: bytes=32 time=41ms TTL=236
Reply from 64.233.183.103: bytes=32 time=46ms TTL=236
Reply from 64.233.183.103: bytes=32 time=50ms TTL=236
Reply from 64.233.183.103: bytes=32 time=46ms TTL=236
Reply from 64.233.183.103: bytes=32 time=40ms TTL=236
Reply from 64.233.183.103: bytes=32 time=45ms TTL=236
Reply from 64.233.183.103: bytes=32 time=40ms TTL=236
Reply from 64.233.183.103: bytes=32 time=41ms TTL=236
Reply from 64.233.183.103: bytes=32 time=41ms TTL=236

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

i tvoj bf2 server

C:\Users\Administrator>ping 84.244.162.128 -n 10

Pinging 84.244.162.128 with 32 bytes of data:
Reply from 84.244.162.128: bytes=32 time=42ms TTL=49
Reply from 84.244.162.128: bytes=32 time=41ms TTL=49
Reply from 84.244.162.128: bytes=32 time=40ms TTL=49
Reply from 84.244.162.128: bytes=32 time=43ms TTL=49
Reply from 84.244.162.128: bytes=32 time=40ms TTL=49
Reply from 84.244.162.128: bytes=32 time=40ms TTL=49
Reply from 84.244.162.128: bytes=32 time=42ms TTL=49
Reply from 84.244.162.128: bytes=32 time=45ms TTL=49
Reply from 84.244.162.128: bytes=32 time=42ms TTL=49
Reply from 84.244.162.128: bytes=32 time=41ms TTL=49

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

C:\Documents and Settings\Stefan>ping www.google.com

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

Reply from 74.125.39.99: bytes=32 time=33ms TTL=237
Reply from 74.125.39.99: bytes=32 time=37ms TTL=237
Reply from 74.125.39.99: bytes=32 time=43ms TTL=237
Reply from 74.125.39.99: bytes=32 time=28ms TTL=237

Ping statistics for 74.125.39.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 43ms, Average = 35ms

C:\Documents and Settings\Stefan>ping 84.244.162.128

Pinging 84.244.162.128 with 32 bytes of data:

Reply from 84.244.162.128: bytes=32 time=43ms TTL=48
Reply from 84.244.162.128: bytes=32 time=47ms TTL=48
Reply from 84.244.162.128: bytes=32 time=50ms TTL=48
Reply from 84.244.162.128: bytes=32 time=39ms TTL=48

Ping statistics for 84.244.162.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 50ms, Average = 44ms

C:\Documents and Settings\Stefan>ping 84.244.162.128

Pinging 84.244.162.128 with 32 bytes of data:

Reply from 84.244.162.128: bytes=32 time=60ms TTL=48
Reply from 84.244.162.128: bytes=32 time=47ms TTL=48
Reply from 84.244.162.128: bytes=32 time=48ms TTL=48
Reply from 84.244.162.128: bytes=32 time=46ms TTL=48

Ping statistics for 84.244.162.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 60ms, Average = 50ms
Sad je bolja situacija ali se desi da skoci ping, nadam se da ce se potpuno stabilizovati ping u narednim danima.

C:\Documents and Settings\Stefan>tracert www.google.com

Tracing route to www.l.google.com [209.85.137.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms <1 ms 5 ms 10.151.66.2
3 <1 ms 4 ms 4 ms 10.151.66.1
4 2 ms 5 ms 4 ms 10.151.176.1
5 11 ms 1 ms 3 ms 10.151.186.1
6 2 ms 2 ms 2 ms 10.151.175.1
7 4 ms 2 ms 2 ms 10.150.1.2
8 5 ms 3 ms 9 ms 10.160.250.1
9 6 ms 3 ms 4 ms 194.106.163.201
10 14 ms 6 ms 8 ms 79.101.96.57
11 35 ms 28 ms 28 ms de-cix10.net.google.com [80.81.192.108]
12 143 ms 33 ms 37 ms 209.85.255.172
13 50 ms 55 ms 38 ms 72.14.233.106
14 48 ms 39 ms 43 ms 209.85.130.21
15 49 ms 55 ms 53 ms 216.239.43.102
16 36 ms 41 ms 37 ms mg-in-f99.google.com [209.85.137.99]

Trace complete.

Pronashli smo problem i reshili.

Potpis

We are Borg. We shall assimilate you.
RESISTANCE IS FUTILE!

Asus P6T Deluxe V2
Intel Core i7 965 3.2GHz
OCZ 3x2GB DDR3 PC3-12800 Flex EX Low Voltage Triple Channel
2x1000GB Spinpoint F1
ATI Radeon HD5970
Lian Li PC-P80R
Samsung T240

www.me2everyone.com/213043

Hvala bogu i vama, ping je stabilan.

Jao sto lepo radi KBC izgleda da je Sleepless_mind umeso svoje prste pa sredio sve

Pa sad... zavisi dokle se ide :(



ali do "Njemacku".



Paket je custom, 384/4096 (upload soho).

U maltene isto vreme ADSL...:


i


tako da ipak nije do KBC-a, izgleda da malo ka inostranstvu imamo zagusenje :(

Potpis

Kad sve ostalo zakaže, pročitaj uputstvo...

Ala ste ga opravili, ne dao bog nikome. Daj bre u pm sredjujte vec jednom ovo go***. Kako bre vec nedelju dana ne radi kako treba. Pa mrmoti da rade do sada bi popravili!





For the record, imam Soho 2 mbit/s...

meni deluje da je ok
5ghz Jakovo basic512

C:\Users\Administrator>ping www.beotel.yu -n 10

Pinging www.beotel.yu [194.106.162.55] with 32 bytes of data:
Reply from 194.106.162.55: bytes=32 time=5ms TTL=57
Reply from 194.106.162.55: bytes=32 time=6ms TTL=57
Reply from 194.106.162.55: bytes=32 time=6ms TTL=57
Reply from 194.106.162.55: bytes=32 time=7ms TTL=57
Reply from 194.106.162.55: bytes=32 time=5ms TTL=57
Reply from 194.106.162.55: bytes=32 time=5ms TTL=57
Reply from 194.106.162.55: bytes=32 time=5ms TTL=57
Reply from 194.106.162.55: bytes=32 time=6ms TTL=57
Reply from 194.106.162.55: bytes=32 time=6ms TTL=57
Reply from 194.106.162.55: bytes=32 time=5ms TTL=57

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

C:\Users\Administrator>ping www.google.com -n 10

Pinging www.l.google.com [64.233.183.99] with 32 bytes of data:
Reply from 64.233.183.99: bytes=32 time=39ms TTL=238
Reply from 64.233.183.99: bytes=32 time=39ms TTL=238
Reply from 64.233.183.99: bytes=32 time=37ms TTL=238
Reply from 64.233.183.99: bytes=32 time=38ms TTL=238
Reply from 64.233.183.99: bytes=32 time=40ms TTL=238
Reply from 64.233.183.99: bytes=32 time=38ms TTL=238
Reply from 64.233.183.99: bytes=32 time=40ms TTL=238
Reply from 64.233.183.99: bytes=32 time=38ms TTL=238
Reply from 64.233.183.99: bytes=32 time=38ms TTL=238
Reply from 64.233.183.99: bytes=32 time=40ms TTL=238

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

Pa dobro Milane ako on ima problem to ne znaci da moras i ti da ga imas

Prebacio sam se na drugu baznu stanicu i sada je kao ok, nije savrseno ali je bolje nego tamo gde sam bio...

Normalno ali ovako vidi da je do bazne a ne do cele mreze

Slazem se

Well, well, well... ;)
Lepo, mada bi ja radije furao 3mbit/s na 2.4GHz nego veci upload ali da ne cepidlacimo. ;)


Kompletnu vest imate na/u kbcnet nalogu/mail sanducetu.

Naime povecane su brzine upload-a SOHO paketima.

Korisnik sam KBCnet-a. Kacim se na F1KBCnet i F2KBCnet. Do skoro mi je jacina signala bila 32-36dB a u procentima Signal strenght-100% i Signal qualiti-100%, sve u svemu perfektno sto su mi i rekli kad sam pozvao korisnicki servis. Od pre nekoliko dana signal ne prelazi 20db ili ti signal strenght varira oko 80% a Signal qualiti je 0%, pa 30% pa 5% pa 70%...... Sve u svemu ne zadovoljavajuc je. Pokusavao sam i sa pomeranjem antene ali nista bitno se nije desilo. U cemu bi mogao da bude problem?

Inace koristim HyperLink grid antenu, 3m-kabla i TP-link651g. Od AP-a sam udaljen ne vise od 2km.

Proveri jer je bila kisa da ti nisu mokri prikljucci u konektorima, grid proveri da nije usla voda u fid da nema neke rupe gde bi mogla proci

Bilo je malo vode u konektoru, obrisao sam i ceo dan je kabal bio pored radijatora tako da se valjda dobro osusio. Jedino ne znam, dal je voda mogla kroz konektor da udje u kabal, u tom slucaju bi ceo kabal zamenio. Sto se tice Fid-a, deluje mi dobro hermeticki zatvoren. Ako ga otvorim da proverim dal je usla voda, nema sansi posle da vratim kako je bilo.