Re: laip paziureti kas tinkle stabdo [S54 @ 2012-01-19 11:59:42]

Tema: Re: laip paziureti kas tinkle stabdo
Autorius: S54
Data: 2012-01-19 11:59:42
tai parskanuok su antivirusu ir paziurek tinklo plokstes nustatymus to 
192.168.1.114;  kompo.

"Telekomaz"  wrote in message news:jf5vps$d01$1@trimpas.omnitel.net...

na tinklai - man tamsus miškas, tai tenka kažkaip aprgraibom ieškoti bėdų...

va mano swičas duoda toki loga, iš kurio matosi, kad 114 kompas tankiai
kažko nori:

1 2925861:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
2 2925876:DHCPS: request(): cid=1:0x0050bf5c42e8; ip=192.168.1.104;
send_dhcp(ACK) done.
3 2925880:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
4 2925903:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
5 2925916:DHCPS: request(): cid=1:0x000b6a9e6715; ip=192.168.1.101;
send_dhcp(ACK) done.
6 2926187:DHCPS: request(): cid=1:0xe06995c31c2c; ip=192.168.1.108;
send_dhcp(ACK) done.
7 2926247:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
8 2926261:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
9 2926267:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
10 2926275:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
11 2926277:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
12 2926280:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
13 2926283:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
14 2926289:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
15 2926292:DHCPS: request(): cid=1:0x001a4dfcd872; ip=192.168.1.102;
send_dhcp(ACK) done.
16 2926295:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
17 2926303:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
18 2926323:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
19 2926347:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
20 2926363:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
21 2926431:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
22 2926455:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
23 2926465:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
24 2926470:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
25 2926482:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
26 2926489:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
27 2926491:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
28 2926495:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
29 2926499:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
30 2926508:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
31 2926523:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
32 2926525:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
33 2926529:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
34 2926534:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
35 2926538:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
36 2926543:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
37 2926546:DHCPS: request(): cid=1:0x001fd015f238; ip=192.168.1.103;
send_dhcp(ACK) done.
38 2926549:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
39 2926567:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.
40 2926595:DHCPS: request(): cid=1:0x0023541805f1; ip=192.168.1.114;
send_dhcp(ACK) done.


2012.01.18 10:17, locked rašė:
> neklysti, bet as ne apie tai ir rasiau, o apie tai, kad jeigu ir stabdo, 
> tai
> ne del sesiju skaiciaus, paprasti switchai/hubai dirba ne su sesijomis
>
> "Telekomaz"<v.teodoras@gmail-bubu.com>  wrote in message
> news:jf5qhb$6n9$1@trimpas.omnitel.net...
>> na, suinstaliavus i konkretu PC koki network monitoriu, jei tinla dalina
>> sti?as tai tas monitorius rodys tik to PC paketus, o hubo atveju -
>> pamaty?iau viso tinklo. ar klystu? nes dabar tik savo paketus ir matau
>>
>> 2012.01.18 01:22, locked ra??:
>>> hubas ar switchas ne su sesijom dirba jei ka
>>>
>>> "telekomas"<v.teodoras@gmail_trinti.com>   wrote in message
>>> news:jeu36e$eff$1@trimpas.omnitel.net...
>>> nu margalina visi tankiai :)
>>> meginsiu wireshark, reiks tik sugalvoti, kaip pajungti PC, kad sektu
>>> visa lano srauta, dabar gi svicas atsiuncia tik instaliuoto pc srauta...
>>>
>>> p.s. beja, klausimelis - ar gali buti, kad 16 portu hubas nesusitvarko
>>> su dideliu kiekiu sesiju is kazkurio kompo, ir del to stringa visas lano
>>> darbas - PC network properciuose rodo "limited connectivity"
>>>
>>>
>>> 2012.01.14 21:17, arulis rase:
>>>> kartais ant swicho gali pamatyt,kuris labai margalina
>>>> "Telekomaz"<v.teodoras@gmail-bubu.com>    wrote in message
>>>> news:jep1mt$rni$1@trimpas.omnitel.net...
>>>>> sveiki,
>>>>>
>>>>> tinkle yra 20 kompu. vienas kazkuris arba virusuotas arba kazkas - 
>>>>> varo
>>>>> labai daug sesij? - kaip (kokiu softu) pamatyti koks tai kompas?
>>>>>
>>>>> T.V
>>>>
>>>>
>>>
>>>
>>>
>>
>
>
>