alchemy Posted January 24, 2011 Share Posted January 24, 2011 Стига сте човъркали настройките на рутера, ами прегледайте как са ви кримпнати кабелите и то ВСИЧКИ. Ако трябва, пробвайте с нови фабрични. Аз точно такъв го ядох (нали съм си мАстор и си кримпнах сам вътрешната мрежа) с един почти невидимо неравномерно кримпнат, който натискаше повече пиновете на смарт-суича и те потъват навътре и кога захапе, кога - не. Аз се имам за сравнително грамотен човек в тая област, обаче налице е гореописаната левашка грешка. П.П. Може и при samkijot проблема да е от такова естество. П.П.П. Прегледайте пинчетата на суича, на WAN порта на рутера, също и на ланките на компютъра дали не са хлътнали. Link to comment Share on other sites More sharing options...
samkijot Posted January 25, 2011 Share Posted January 25, 2011 с друг рутер проблемите са идентични: Microsoft Windows [Version 6.1.7600] (c) 2009 Microsoft Corporation. Всички права запазени. C:\Users\samkijot>ping -t www.google.com Pinging www.l.google.com [209.85.135.99] with 32 bytes of data: Reply from 209.85.135.99: bytes=32 time=52ms TTL=53 Reply from 209.85.135.99: bytes=32 time=115ms TTL=53 Reply from 209.85.135.99: bytes=32 time=63ms TTL=53 Reply from 209.85.135.99: bytes=32 time=54ms TTL=53 Reply from 209.85.135.99: bytes=32 time=130ms TTL=53 Reply from 209.85.135.99: bytes=32 time=225ms TTL=53 Reply from 209.85.135.99: bytes=32 time=167ms TTL=53 Reply from 209.85.135.99: bytes=32 time=55ms TTL=53 Reply from 209.85.135.99: bytes=32 time=55ms TTL=53 Reply from 209.85.135.99: bytes=32 time=51ms TTL=53 Reply from 209.85.135.99: bytes=32 time=189ms TTL=53 Reply from 209.85.135.99: bytes=32 time=175ms TTL=53 Reply from 209.85.135.99: bytes=32 time=53ms TTL=53 Reply from 209.85.135.99: bytes=32 time=52ms TTL=53 Request timed out. Reply from 209.85.135.99: bytes=32 time=483ms TTL=53 Reply from 209.85.135.99: bytes=32 time=846ms TTL=53 Reply from 209.85.135.99: bytes=32 time=587ms TTL=53 Reply from 209.85.135.99: bytes=32 time=470ms TTL=53 Reply from 209.85.135.99: bytes=32 time=639ms TTL=53 Reply from 209.85.135.99: bytes=32 time=602ms TTL=53 Reply from 209.85.135.99: bytes=32 time=153ms TTL=53 Reply from 209.85.135.99: bytes=32 time=336ms TTL=53 Reply from 209.85.135.99: bytes=32 time=53ms TTL=53 Reply from 209.85.135.99: bytes=32 time=54ms TTL=53 Reply from 209.85.135.99: bytes=32 time=53ms TTL=53 Reply from 209.85.135.99: bytes=32 time=51ms TTL=53 Reply from 209.85.135.99: bytes=32 time=50ms TTL=53 Reply from 209.85.135.99: bytes=32 time=112ms TTL=53 Reply from 209.85.135.99: bytes=32 time=53ms TTL=53 Reply from 209.85.135.99: bytes=32 time=54ms TTL=53 Reply from 209.85.135.99: bytes=32 time=51ms TTL=53 Reply from 209.85.135.99: bytes=32 time=59ms TTL=53 Reply from 209.85.135.99: bytes=32 time=52ms TTL=53 Reply from 209.85.135.99: bytes=32 time=56ms TTL=53 Reply from 209.85.135.99: bytes=32 time=52ms TTL=53 Reply from 209.85.135.99: bytes=32 time=52ms TTL=53 Reply from 209.85.135.99: bytes=32 time=52ms TTL=53 Reply from 209.85.135.99: bytes=32 time=80ms TTL=53 Reply from 209.85.135.99: bytes=32 time=52ms TTL=53 Reply from 209.85.135.99: bytes=32 time=112ms TTL=53 Reply from 209.85.135.99: bytes=32 time=77ms TTL=53 Reply from 209.85.135.99: bytes=32 time=52ms TTL=53 Reply from 209.85.135.99: bytes=32 time=62ms TTL=53 Reply from 209.85.135.99: bytes=32 time=79ms TTL=53 Reply from 209.85.135.99: bytes=32 time=102ms TTL=53 Reply from 209.85.135.99: bytes=32 time=55ms TTL=53 Reply from 209.85.135.99: bytes=32 time=53ms TTL=53 Reply from 209.85.135.99: bytes=32 time=315ms TTL=53 Request timed out. Reply from 209.85.135.99: bytes=32 time=1015ms TTL=53 Request timed out. Reply from 209.85.135.99: bytes=32 time=312ms TTL=53 Reply from 209.85.135.99: bytes=32 time=241ms TTL=53 Reply from 209.85.135.99: bytes=32 time=418ms TTL=53 Reply from 209.85.135.99: bytes=32 time=370ms TTL=53 Reply from 209.85.135.99: bytes=32 time=479ms TTL=53 Reply from 209.85.135.99: bytes=32 time=196ms TTL=53 Reply from 209.85.135.99: bytes=32 time=59ms TTL=53 Reply from 209.85.135.99: bytes=32 time=61ms TTL=53 Reply from 209.85.135.99: bytes=32 time=51ms TTL=53 Reply from 209.85.135.99: bytes=32 time=53ms TTL=53 Reply from 209.85.135.99: bytes=32 time=51ms TTL=53 Reply from 209.85.135.99: bytes=32 time=65ms TTL=53 Ping statistics for 209.85.135.99: Packets: Sent = 64, Received = 61, Lost = 3 (4% loss), Approximate round trip times in milli-seconds: Minimum = 50ms, Maximum = 1015ms, Average = 177ms Control-C ^C C:\Users\samkijot> Link to comment Share on other sites More sharing options...
w00x Posted January 25, 2011 Share Posted January 25, 2011 samkijot, в панела на рутера иди на Network > WAN и виж настройката ти на WAN Connection Type: дали е Dynamic IP. Link to comment Share on other sites More sharing options...
samkijot Posted January 25, 2011 Share Posted January 25, 2011 samkijot, в панела на рутера иди на Network > WAN и виж настройката ти на WAN Connection Type: дали е Dynamic IP. да, динамично е. п.п. само да вметна, че въпросните обструкции не са постоянни, а само от време на време т.е. има моменти когато зареждам страниците почти мигновено, но и такива когато бавенето е супер изнервящо. Link to comment Share on other sites More sharing options...
didsanka Posted January 26, 2011 Author Share Posted January 26, 2011 Здравейте всички, Страшно много ви благодаря за отговорите )) Проблема е решен - оказа се кофти кримпване към конектора. Момчетата от Cooolbox дойдоха и го оправиха веднага. Сега ми се иска да им се бях обадила по-рано и да бях обяснила по-подробно какъв ми е проблема... Поздрави, Даниела Link to comment Share on other sites More sharing options...
pAbLo_ Posted January 26, 2011 Share Posted January 26, 2011 Един по малко. Остана само samkijot Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.