Ruter se može spojit adsl

poruka: 30
|
čitano: 23.422
|
moderatori: Lazarus Long, pirat, XXX-Man, DrNasty, vincimus
1
+/- sve poruke
ravni prikaz
starije poruke gore
13 godina
offline
Ruter se NE može spojit na adsl

pozdrav

ovako, jučer sam u stan dobio ruter od t coma za pristup adsl-u ali imam problem

u papirima od njega piše da kad se sve prikopča, kod prvog paljenja on bi se trebo sam konfigurirat i spojit na net, no on meni cijelo vrijeme lampica od adsl-a blica, tako već 24 sata i bez uspijeha spajanja na net i bez pomaka

pokušao sam ga više puta i ugasit pa ponovno pokrenut, napisat u ruteru sam korisničko ime i lozinku ali bez uspijeha

na ruter se mogu spojit, wiereless radi ali stalno ali mi blica žaruljica od adsl-a i nikak da stupi u kontakt sa internetom

 

dal je imo tko tak nešto slično i dal zna kak da to se riješi, ili je problem u tome da oni još nisu osposobili broj da može obavljat adsl uslugu il je nešt sjebano negdje

ruter je gigaset sx763

 

P.S: naslov teme ima zajeb, treba pisat da se ne može spojit na adsl

Poruka je uređivana zadnji put uto 19.10.2010 12:12 (matija656).
Moj PC  
0 0 hvala 0
14 godina
protjeran
offline
Ruter se može spojit adsl
08009000


Zovi i pitaj zasto ti to neradi
lijepo li je Hrvat biti,majko hvala ti
Moj PC  
0 0 hvala 0
13 godina
offline
RE: Ruter se ne može spojit adsl

to ću pokušat ako vamo ne uspijem dobit kakvu pomoć, ako ništa vamo onda zovem tamo

16 godina
neaktivan
offline
RE: Ruter se ne može spojit adsl

Kako si kablove prikopcao? Stavio adsl spliter? Radi li ti telefon?

 

:)
13 godina
offline
RE: Ruter se ne može spojit adsl
sve sam kablove više puta pregledao i sve je dobro prikopčano, spliter sam stavio i telefon radi sad neznam dal da probam direkt spojit ruter u zid bez splitera, da telefon iskopčam da vidim dal bi bilo kakvog pomaka
14 godina
neaktivan
offline
Ruter se može spojit adsl

Koje ti lampice svijetle i koje su boje?

 

 
0 0 hvala 0
13 godina
offline
RE: Ruter se može spojit adsl
svijetle mi trenutno za wiereless, power a adsl lampica mi stalno blica, ove lampice za lan rade al mi ne trebaju jer se spajam na ruter preko lapa, i zelene su boje sve lampice
14 godina
neaktivan
offline
Ruter se može spojit adsl
192.168.0.1 ili 192.168.1.1 postavke rutera. Kad uđes u postavke tamo imas sve. Jel ti tel. Kabl uđe u modem, pa lanom u ruter?
 
0 0 hvala 0
13 godina
offline
RE: Ruter se može spojit adsl
telefonski kabel mi iz telefona ide u splitter u utičnicu phone, iz zida mi kabel ide u utičnicu line a dsl kabel iz splitera (utičnica dls) ide na ruter u utičnicu adsl, i opet mi ne šljaka, a ovo za postavke neznam šta da mijenjam pa da vidim dal bude proradilo, to bi trebalo samo od sebe počet radti, jedino šta sam pisao u postavkama su korisničko ime i lozinka ali opet je bilo bez uspijeha
15 godina
offline
RE: Ruter se može spojit adsl
matija656 kaže...
telefonski kabel mi iz telefona ide u splitter u utičnicu phone, iz zida mi kabel ide u utičnicu line a dsl kabel iz splitera (utičnica dls) ide na ruter u utičnicu adsl, i opet mi ne šljaka, a ovo za postavke neznam šta da mijenjam pa da vidim dal bude proradilo, to bi trebalo samo od sebe počet radti, jedino šta sam pisao u postavkama su korisničko ime i lozinka ali opet je bilo bez uspijeha

 -prvo, tel. linija (glavna, čista žica) koja dolazi do tebe, na nju se stavlja spliter i sve dalje se nesmije miješati tel-ADSL. (obično su utičnise spojene na nekoliko mjesta, drugi tel itd. to je vjerojatni problem).

Najkonkretnije je otvoriti utičnicu i direktno spojiti.

-Router možeš spijiti direktno bez splitera. Tako testiraš spliter.

Paljenjem, po redu power, DSL, line.. moraju blicati unutar 1-2 minute se DSL mora stabilizirati.

Uvjek za probleme zoveš SZK, to je njihov posao, to plačaš i tako se ponašaj. (bez obzira i kad je tvoja krivica, oni su tamo zbog tebe).

Jer je moguće da ti nisu ni aktivirali liniju...

Od mogućih stvari, recimo neispravan router ili spliter, problematičan kabel, previše smetnji po kućnim instalacijama.. svašta je moguće.

Nagađam da je ipak samo problem u spojenim žicama-dodatnim utičnicama telefonima. Tel. može raditi ali ADSL ne.

C64/TurboModul-OpenSourceProject.org.cn.部分作品为网上收集整理,供开源爱好者学习使用
16 godina
neaktivan
offline
RE: Ruter se može spojit adsl

Kako si ukucao username? Mozda ti treba username@ADSL. Imas u routeru log pa iskopiraj sta tamo pise.

:)
13 godina
offline
RE: Ruter se može spojit adsl
sad sam uštekao router direktno u utičnicu od telefona, znači splitter i telefon nisu u finkciji ali meni opet dsl lampica stalno blica
a username naravno da sam upisao sa nastavkom i nije pomoglo, a za log dal da cijeli stavim u post, pitam zato da ne bude prevelik post
15 godina
neaktivan
offline
RE: Ruter se može spojit adsl
Ti si 100% spliter pogresno nastimao...
In Control... MNOGE države imaju mafiju. Ali u Hrvatskoj mafija ima državu...
16 godina
neaktivan
offline
RE: Ruter se može spojit adsl

Stavi zadnjih 10 redova.

:)
13 godina
offline
RE: Ruter se može spojit adsl

kak se to uopće može, svaki kabal sam uštekao u njegovo mjesto, i to više puta i nije pomoglo, sad sam uštekao ruter direkt u zid i opet mi je ista prića...

 

evo iz loga (stavljam sve pa šta bude): 

Jan  1 00:00:03 War <EVENT> kernel:  wdt_open:wdt_open

Jan  1 00:00:03 War <EVENT> kernel:  wdt_ioctl:enable watch dog timer!

Jan  1 00:00:03 Inf <EVENT> syslog: TMOND: My PID is 97 

Jan  1 00:00:03 Inf <EVENT> syslog: TMOND: Starting Watchdog... 

Jan  1 00:00:03 Eme <EVENT> syslog: TMOND: Setting PWL! 3 

Jan  1 00:00:03 Eme <EVENT> syslog: TMOND: Setting CLKDIV ! 3 

Jan  1 00:00:03 Inf <EVENT> syslog: TMOND: Watchdog started. Timeout is set to 4s. 

Jan  1 00:00:05 Inf <EVENT> scm: 000-00-00  Starting Service Management Framework, Version 2 (2.0.1)

Jan  1 00:00:06 Inf <EVENT> scm: 016-00-00  scm::DeviceInfo::Service created

Jan  1 00:00:06 Inf <EVENT> scm: 017-00-00  scm::DeviceConfig::Service created

Jan  1 00:00:06 Inf <EVENT> scm: 055-00-00  FileVerification::Verificator created

Jan  1 00:00:06 Inf <EVENT> scm: 056-00-00  FileVerification::Creator created

Jan  1 00:00:06 Inf <EVENT> scm: 058-00-00  scm::SoftwareImageInstaller::ImageOnFlashService created

Jan  1 00:00:06 Inf <EVENT> scm: 057-00-00  scm::PlatformInfo Service created

Jan  1 00:00:06 Inf <EVENT> scm: 022-00-00  scm::SoftwareImageMngmt::Service created

Jan  1 00:00:06 Inf <EVENT> scm: 025-00-00  scm::DownloadAgent created

Jan  1 00:00:06 Inf <EVENT> scm: 085-00-00  FileDownload::Service created

Jan  1 00:00:06 Inf <EVENT> scm: 084-00-00  FileUpload::Service created

Jan  1 00:00:06 Inf <EVENT> scm: 107-00-00  scm::FileUpgrade::Service created

Jan  1 00:00:06 Inf <EVENT> scm: 026-00-00  scm::LoggingService created.

Jan  1 00:00:06 Inf <EVENT> scm: 027-00-00  scm::PasswordService created.

Jan  1 00:00:06 Inf <EVENT> scm: 095-00-00  Security::Service created

Jan  1 00:00:06 Inf <EVENT> scm: 071-00-00  CM_ATM: constructor

Jan  1 00:00:06 Inf <EVENT> scm: 092-00-00  scm:: MacService created.

Jan  1 00:00:06 Inf <EVENT> scm: 092-00-00  MAC:: init:ethcount = 8

Jan  1 00:00:06 Inf <EVENT> scm: 092-00-00  MAC:: init:ethaddress = 98:8B:5D:F3:C7:88

Jan  1 00:00:06 Inf <EVENT> scm: 044-00-00  scm::LinkComponent created.

Jan  1 00:00:06 Inf <EVENT> scm: 047-00-00  scm::BridgingComponent created.

Jan  1 00:00:06 Inf <EVENT> scm: 046-00-00  scm::DHCPComponent created.

Jan  1 00:00:06 Inf <EVENT> scm: 042-00-00  scm::RoutingComponent created.

Jan  1 00:00:06 Inf <EVENT> scm: 045-00-00  scm::IPComponent created.

Jan  1 00:00:06 Inf <EVENT> scm: 049-00-00  PPP:: processChildEvent, ppp_cm is down, ignore event [92]

Jan  1 00:00:06 Inf <EVENT> scm: 033-00-00  scm::DHCPComponentManager created [ID=33]

Jan  1 00:00:06 Inf <EVENT> scm: 032-00-00  scm::DnsServerComponentManager created.

Jan  1 00:00:06 Inf <EVENT> scm: 050-00-00  scm::QDisciplineComponentManager created. [ID=50]

Jan  1 00:00:06 Inf <EVENT> scm: 090-00-00  scm::IcProxyCM created. [ID=90])

Jan  1 00:00:06 Inf <EVENT> scm: 096-101-00  created CM_DYNAMICCLASSIFICATION [96]

Jan  1 00:00:06 Inf <EVENT> scm: 077-00-00  scm::FirewallComponent created [77]

Jan  1 00:00:06 Inf <EVENT> scm: 067-00-00  scm::SipAlgComponentManager created

Jan  1 00:00:06 Inf <EVENT> scm: 065-00-00  scm::EthernetSwitchADM6996ComponentManager created

Jan  1 00:00:06 Inf <EVENT> scm: 080-00-00  scm::IPTVComponentManager created. [ID 80]

Jan  1 00:00:06 Inf <EVENT> scm: 074-00-00  L2XP: component manager created [ID=74]

Jan  1 00:00:06 Inf <EVENT> scm: 029-00-00  scm::TR69Component--created

Jan  1 00:00:06 War <EVENT> scm: 083-00-00  TimeServiceComponentManager first_use_date; default interface not yet known; asuming bridged for now

Jan  1 00:00:06 Inf <EVENT> scm: 083-00-00  scm::TimeService created.

Jan  1 00:00:06 Inf <EVENT> scm: 028-00-00  scm::AllegroComponent created

Jan  1 00:00:06 Inf <EVENT> scm: 048-00-00  scm::ssh server created

Jan  1 00:00:06 Inf <EVENT> scm: 051-00-00  scm::PingDiagnostic created.

Jan  1 00:00:06 Inf <EVENT> scm: 052-00-00  scm::DynDnsComponent created

Jan  1 00:00:06 Inf <EVENT> scm: 053-00-00  scm::TraceRouteDiagnostic created.

Jan  1 00:00:06 Inf <EVENT> scm: 054-00-00  scm::Diagnostic created.

Jan  1 00:00:06 Inf <EVENT> scm: 086-00-00  PortTriggering component created.

Jan  1 00:00:06 Inf <EVENT> scm: 088-00-00  scm::WanReconnectSchedulingService created. [ID=88])

Jan  1 00:00:06 Inf <EVENT> scm: 089-00-00  STUNService component created

Jan  1 00:00:06 Inf <EVENT> scm: 102-00-00  Host:Component manager: Created [102]

Jan  1 00:00:06 Inf <EVENT> scm: 000-00-00  rtpsd::ComponentManager Created [103]

Jan  1 00:00:06 Inf <EVENT> scm: 108-00-00  scm::PortRelayService created. [ID=108])

Jan  1 00:00:06 Inf <EVENT> scm: 094-00-00  FirmwareUpdate--Created

Jan  1 00:00:06 Inf <EVENT> scm: 109-00-00  OopsComponent created

Jan  1 00:00:06 Inf <EVENT> scm: 015-00-00  scm::ManagedParametersService [IGD] created

Jan  1 00:00:06 Inf <EVENT> scm: 060-00-00  HTTPclient recieved event 127

Jan  1 00:00:06 Inf <EVENT> scm: 060-00-00  HTTPClient: allegro state received DOWN, allegroTaskDataPtr 0  

Jan  1 00:00:06 Inf <EVENT> scm: 028-00-00  AllegroComponent: send state: 0, allegroTaskDataPtr: 0 to component_id: 60 

Jan  1 00:00:06 Inf <EVENT> scm: 061-00-00  FileTransfer::Agent created

Jan  1 00:00:06 Inf <EVENT> scm: 062-00-00  HTTPclient recieved event 127

Jan  1 00:00:06 Inf <EVENT> scm: 062-00-00  HTTPClient: allegro state received DOWN, allegroTaskDataPtr 0  

Jan  1 00:00:06 Inf <EVENT> scm: 028-00-00  AllegroComponent: send state: 0, allegroTaskDataPtr: 0 to component_id: 62 

Jan  1 00:00:06 Inf <EVENT> scm: 030-00-00  TR69Agent--Created

Jan  1 00:00:06 Inf <EVENT> scm: 000-00-00  UPnP: upnp_param_changed_callback==NULL

Jan  1 00:00:06 Inf <EVENT> scm: 014-00-00  Updating system running level from 1 to 3

Jan  1 00:00:06 Inf <EVENT> scm: 014-00-00  Start component 16 (DeviceInfoService)

Jan  1 00:00:06 Inf <EVENT> scm: 014-00-00  Start component 17 (DeviceConfigService)

Jan  1 00:00:06 Inf <EVENT> scm: 017-00-00  Start requested, retrieving DeviceConfig settings

Jan  1 00:00:06 Inf <EVENT> scm: 017-00-00  active configfile version 52.11.310

Jan  1 00:00:06 Inf <EVENT> scm: 017-00-00  runtime image version 52.11.310

Jan  1 00:00:06 Inf <EVENT> scm: 000-00-00  Version 1: 52 -- 11 -- 310

Jan  1 00:00:06 Inf <EVENT> scm: 000-00-00  Version 2: 52 -- 11 -- 310

Jan  1 00:00:06 Inf <EVENT> scm: 017-00-00  no configfile up/downgrade needed

Jan  1 00:00:06 Err <EVENT> scm: 017-05-00  Unable to create Device Config File for elements file: Elements file does not exist.

Jan  1 00:00:06 Inf <EVENT> scm: 017-00-00  checkCopyDefault

Jan  1 00:00:06 Inf <EVENT> scm: 000-00-00  Version 1: 0 -- 0 -- 0

Jan  1 00:00:06 Inf <EVENT> scm: 000-00-00  Version 2: 52 -- 11 -- 300

Jan  1 00:00:06 Inf <EVENT> scm: 017-00-00  Configuring services with settings from configuration file

Jan  1 00:00:17 Inf <EVENT> scm: 000-00-00  UPnP: upnp_param_changed_callback==NULL

Jan  1 00:00:17 Inf <EVENT> scm: 000-00-00  UPnP: upnp_param_changed_callback==NULL

Jan  1 00:00:17 Inf <EVENT> scm: 000-00-00  UPnP: upnp_param_changed_callback==NULL

Jan  1 00:00:17 Inf <EVENT> scm: 000-00-00  UPnP: upnp_param_changed_callback==NULL

Jan  1 00:00:17 Inf <EVENT> scm: 017-00-00  Configuring services with settings from /config/system_configfile_f

Jan  1 00:00:17 Inf <EVENT> scm: 017-00-00  Configuring services with settings from /config/system_configfile_r

Jan  1 00:00:17 Inf <EVENT> scm: 017-00-00  Provisioning mode = Dormant

Jan  1 00:00:17 Inf <EVENT> scm: 017-00-00  Provisioning complete

Jan  Jan  1 00:00:19 War <EVENT> kernel: Porta WLAN EEPROM driver: v0.3 

Jan  1 00:00:19 War <EVENT> kernel: -> wlan_eesim_write 0x0 4096

Jan  1 00:00:19 War <EVENT> kernel: wlan_eesim_write ok

Jan  1 00:00:19 War <EVENT> kernel: Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved

Jan  1 00:00:20 War <EVENT> kernel: Copyright (c) 2001-2004 Atheros Communications, Inc, All Rights Reserved

Jan  1 00:00:20 War <EVENT> kernel: wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps

Jan  1 00:00:20 War <EVENT> kernel: wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps

Jan  1 00:00:20 War <EVENT> kernel: wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps

Jan  1 00:00:20 War <EVENT> kernel: wifi0: mac 7.9 phy 4.5 radio 5.6

Jan  1 00:00:20 War <EVENT> kernel: wifi0: Use hw queue 1 for WME_AC_BE traffic

Jan  1 00:00:20 War <EVENT> kernel: wifi0: Use hw queue 0 for WME_AC_BK traffic

Jan  1 00:00:20 War <EVENT> kernel: wifi0: Use hw queue 2 for WME_AC_VI traffic

Jan  1 00:00:20 War <EVENT> kernel: wifi0: Use hw queue 3 for WME_AC_VO traffic

Jan  1 00:00:20 War <EVENT> kernel: wifi0: Use hw queue 8 for CAB traffic

Jan  1 00:00:20 War <EVENT> kernel: wifi0: Use hw queue 9 for beacons

Jan  1 00:00:22 War <EVENT> scm: 032-03-00  DnsComponentManager:processChildEvent ignoring event while not started

Jan  1 00:00:22 War <EVENT> kernel: eth0.2: Setting MAC address to  98 8b 5d f3 c7 88.

Jan  1 00:00:22 War <EVENT> kernel: VLAN (eth0.2):  Setting underlying device (eth0) to promiscious mode.

Jan  1 00:00:22 War <EVENT> scm: 032-03-00  DnsComponentManager:processChildEvent ignoring event while not started

Jan  1 00:00:22 War <EVENT> scm: 032-03-00  DnsComponentManager:processChildEvent ignoring event while not started

Jan  1 00:00:22 War <EVENT> scm: 032-03-00  DnsComponentManager:processChildEvent ignoring event while not started

Jan  1 00:00:22 War <EVENT> scm: 032-03-00  DnsComponentManager:processChildEvent ignoring event while not started

Jan  1 00:00:22 War <EVENT> kernel: eth0.4: Setting MAC address to  98 8b 5d f3 c7 88.

Jan  1 00:00:23 War <EVENT> scm: 032-03-00  DnsComponentManager:processChildEvent ignoring event while not started

Jan  Jan  1 00:00:28 War <EVENT> scm: 033-01-00  DhcpComponentManager state==idle (ignore event)

Jan  1 00:00:28 War <EVENT> scm: 032-03-00  DnsComponentManager:processChildEvent ignoring event while not started

Jan  1 00:00:28 Err <EVENT> scm: 086-00-00  PortTriggering received EV_NET_IPSTATUS

Jan  1 00:00:28 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 00:00:28 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 00:00:28 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 00:00:28 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 00:00:28 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 00:00:28 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 00:00:28 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 00:00:28 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 00:00:28 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 00:00:28 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 00:00:28 War <EVENT> scm: 080-01-00  IPTVCm: processChildEvent state==Idle (ignore event)

Jan  1 00:00:31 Err <EVENT> scm: 995-00-00  WebGUI::ProductRows Initialize: unsupported customer:4 for boardid: sx763 detected !!!:

Jan  1 00:00:32 War <EVENT> scm: 077-00-00  FW::resolveInterface: interface nas4 not in service

Jan  1 00:00:32 War <EVENT> scm: 029-00-00  scm::TR69Component--Got IP status, interface is inactive

Jan  1 01:00:32 War <EVENT> scm: 077-00-00  FW::resolveInterface: interface nas4 not in service

Jan  1 01:00:32 Err <EVENT> kernel: devfs_mk_dir(usb): using old entry in dir: 810686c0 ""

Jan  1 01:00:33 War <EVENT> kernel: 

Jan  1 01:00:33 War <EVENT> kernel: 

Jan  1 01:00:33 War <EVENT> kernel: 

Jan  1 01:00:33 War <EVENT> kernel: 

Jan  1 01:00:33 War <EVENT> kernel: dwc_otg proc initialization okay! 

Jan  1 01:00:34 War <EVENT> kernel: UFSD version 6.12 (May  5 2008, 18:36:58)

Jan  1 01:00:34 War <EVENT> kernel: NTFS read/write support included

Jan  1 01:00:34 War <EVENT> kernel: Big endian platform

Jan  1 01:00:34 War <EVENT> kernel: $Id: ufsdvfs.c,v 1.148 2008/04/30 11:11:28 shura Exp $

Jan  1 01:00:37 War <EVENT> kernel: ifx_mps_init_gpt_danube() - calibration done, waited 715 loops!

Jan  1 01:00:37 War <EVENT> scm: 050-20-00  QDisciplineCM:handleEvent  skipping EV_Link_InterfaceStatus (no linuxdevice name) 

Jan  1 01:00:39 Err <EVENT> scm: 086-00-00  PortTriggering received EV_NET_IPSTATUS

Jan  1 01:00:40 War <EVENT> kernel: 

kernel: Got MODEM_READY_MSG

Jan  1 01:01:41 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:02:42 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:03:05 War <EVENT> kernel: wsc oui=dd, 9, 0,10,18, 2

Jan  1 01:03:43 Err <EVENT> kernel: meiMailboxWrite: 

Jan  1 01:03:43 War <EVENT> kernel: 

Jan  1 01:03:43 Err <EVENT> kernel:  MEI_TO_ARC_MSGAV not cleared by ARC<3>meiCMV: 

Jan  1 01:03:43 War <EVENT> kernel: 

Jan  1 01:03:43 War <EVENT> kernel:  MailboxWrite Fail.kernel: Got MODEM_READY_MSG

Jan  1 01:03:44 War <EVENT> scm: 995-00-00  WebGUI::prepareDataForPageLoad Apply Rollback on existing scm session:

Jan  1 01:03:48 Err <EVENT> scm: 995-00-00  GetCfgParamById() PrepareData has failed for FormInputId: country, PrepareDataState:4 :

Jan  1 01:03:53 Err <EVENT> scm: 995-00-00  GetCfgParamById() PrepareData has failed for FormInputId: country, PrepareDataState:4 :

Jan  1 01:04:44 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:05:45 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:06:46 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:07:47 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:08:48 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:09:49 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:10:50 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:11:51 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:12:52 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:13:53 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:14:54 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:15:55 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:16:56 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:17:57 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:18:58 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:19:59 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:21:00 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:22:01 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:22:23 War <EVENT> scm: 995-00-00  WebGUI::prepareDataForPageLoad Apply Rollback on existing scm session:

Jan  1 01:22:25 Err <EVENT> scm: 995-00-00  GetCfgParamById() PrepareData has failed for FormInputId: country, PrepareDataState:4 :

Jan  1 01:22:30 Err <EVENT> scm: 995-00-00  GetCfgParamById() PrepareData has failed for FormInputId: country, PrepareDataState:4 :

Jan  1 01:23:02 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:23:09 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 01:23:09 Err <EVENT> scm: 046-00-00  Dhcp on interface nas2 is down, no pid file(/etc/dhcpc/dhcpcd-nas2.pid).

Jan  1 01:23:09 Err <EVENT> scm: 017-00-00  Received EV_NET_IPSTATUS broadcast: [nas2]

Jan  1 01:23:09 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 01:23:09 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 01:23:09 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 01:23:10 Err <EVENT> scm: 086-00-00  PortTriggering received EV_NET_IPSTATUS

Jan  1 01:23:10 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 01:23:10 Err <EVENT> scm: 046-00-00  Dhcp on interface nas4 is down, no pid file(/etc/dhcpc/dhcpcd-nas4.pid).

Jan  1 01:23:10 Err <EVENT> scm: 017-00-00  Received EV_NET_IPSTATUS broadcast: [nas4]

Jan  1 01:23:10 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 01:23:10 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 01:23:10 Err <EVENT> scm: 077-00-00  Commit failed: iptFix sent back commit_failed 

Jan  1 01:23:10 War <EVENT> scm: 029-00-00  scm::TR69Component--Got IP status, interface is inactive

Jan  1 01:23:10 Err <EVENT> scm: 086-00-00  PortTriggering received EV_NET_IPSTATUS

Jan  1 01:23:10 Err <EVENT> scm: 077-00-00  FirewallComponent::NAT Notification. Unable to remove NAT for address none

Jan  1 01:24:03 Err <EVENT> kernel: meiMailboxWrite: 

Jan  1 01:24:03 War <EVENT> kernel: 

Jan  1 01:24:03 Err <EVENT> kernel:  MEI_TO_ARC_MSGAV not cleared by ARC<3>meiCMV: 

Jan  1 01:24:03 War <EVENT> kernel: 

Jan  1 01:24:03 War <EVENT> kernel:  MailboxWrite Fail.kernel: Got MODEM_READY_MSG

Jan  1 01:25:04 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:26:05 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:27:06 Err <EVENT> kernel: meiMailboxWrite: 

Jan  1 01:27:06 War <EVENT> kernel: 

Jan  1 01:27:06 Err <EVENT> kernel:  MEI_TO_ARC_MSGAV not cleared by ARC<3>meiCMV: 

Jan  1 01:27:06 War <EVENT> kernel: 

Jan  1 01:27:06 War <EVENT> kernel:  MailboxWrite Fail.kernel: Got MODEM_READY_MSG

Jan  1 01:28:07 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:29:08 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:30:09 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:31:10 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:31:15 Err <EVENT> dhcpd: missing tinydns input

Jan  1 01:32:11 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:33:12 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:34:13 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:35:14 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:36:15 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:37:16 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:38:17 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:39:18 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:40:19 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:41:20 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:42:21 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:43:22 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:44:23 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:45:24 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:46:25 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:47:26 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:48:27 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:49:28 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:50:29 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:51:30 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:52:31 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:53:32 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:54:33 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:55:34 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:56:35 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:57:36 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:58:00 War <EVENT> scm: 995-00-00  WebGUI::prepareDataForPageLoad Apply Rollback on existing scm session:

Jan  1 01:58:04 Err <EVENT> scm: 995-00-00  GetCfgParamById() PrepareData has failed for FormInputId: country, PrepareDataState:4 :

Jan  1 01:58:37 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 01:59:38 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:00:39 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:01:40 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:02:41 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:03:42 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:04:43 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:05:44 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:06:45 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:07:46 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:08:47 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:09:48 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:10:49 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:11:48 War <EVENT> scm: 995-00-00  WebGUI::prepareDataForPageLoad Apply Rollback on existing scm session:

Jan  1 02:11:50 War <EVENT> kernel: Got MODEM_READY_MSG

Jan  1 02:11:52 Err <EVENT> scm: 995-00-00  GetCfgParamById() PrepareData has failed for FormInputId: country, PrepareDataState:4 :

---

 

Poruka je uređivana zadnji put uto 19.10.2010 13:00 (matija656).
15 godina
neaktivan
offline
RE: Ruter se može spojit adsl
Mozda je u spliteru problem? Ja sam imao jednom situaciju kad nije valjao spliter... smjesno ali istinito...

Ajde stavi log pa da vidimo...

I da jesi ti zvao uopce tcom? mozda ti jos nisu ADSL ukljucili u centrali a mi te pilimo s 200 stvari...
In Control... MNOGE države imaju mafiju. Ali u Hrvatskoj mafija ima državu...
15 godina
neaktivan
offline
Ruter se može spojit adsl

aaaaa mozda ti je jednostavno router neispavan.... zovi 9000 pa ce ti oni dat rjesenje ili novi router( znam da su vecina u podrsci idioti al kad se mora mora se)

Moj PC  
0 0 hvala 0
13 godina
offline
RE: Ruter se može spojit adsl
zvao sam jučer tamo i rekli su nešto u roku nekoliko dana ovo ono, nisam točno skužio, budem opet zvao pa budem vidio
a sumnjam da su poslali da nešto ne valja jer sa spliterom mi je telefon radio, ruter isto blicao ko i sad kad sam ruter stavio direkt u zid
15 godina
neaktivan
offline
RE: Ruter se može spojit adsl
Pa zovi opet pa pitaj... mozda ti stvarno DSL nisu ukljucili a onda samo moras cekati...
In Control... MNOGE države imaju mafiju. Ali u Hrvatskoj mafija ima državu...
15 godina
neaktivan
offline
Ruter se može spojit adsl

a provaj ga vratit na tvornicke postavke ako nisi... nikad neznas...

Moj PC  
0 0 hvala 0
13 godina
offline
RE: Ruter se može spojit adsl
ma za tvorničke postavke neću pokušavat ovi kak su stavili tak nek bude pa budem vidio dal će se šta promijenit jbg
ako neće bit promjena spamam službu za korisnike pa budem vidio dal bude bilo ploda
15 godina
neaktivan
offline
Ruter se može spojit adsl

Otvori 192.168.1.1 i stisni onaj gumb Connect. Meni je ovo bilo više puta i radilo je nakon toga.

E usput šta piše iznad tog gumba?

Nulla e reale, tutto e lecito. Requiescat in pace
 
0 0 hvala 0
15 godina
offline
RE: Ruter se može spojit adsl
matija656 kaže...
ma za tvorničke postavke neću pokušavat ovi kak su stavili tak nek bude pa budem vidio dal će se šta promijenit jbg
ako neće bit promjena spamam službu za korisnike pa budem vidio dal bude bilo ploda

 -reset na tvorničke postavke mora raditi, nemože ništa pokvariti, jer ga 'izrađuje' ISP. Samo makne sve korisničke izmjene i podatke -user pass. To nije ni potrebno za provjeru DSL linije.

DSL mora raditi da bi prihvatio korisnički username i pass.

C64/TurboModul-OpenSourceProject.org.cn.部分作品为网上收集整理,供开源爱好者学习使用
15 godina
neaktivan
offline
RE: Ruter se može spojit adsl
Ne kuzis IZGR...

njemu se uopce ne spaja na DSL...

(a za sam DSL nemaš connect nego samo za konekciju koja se ostvaruje preko Digital Subscriber Line-a )

Sto bi opet znacilo da mu vrlo vjerojatno nisu jos DSL ukljucili...

Rekao sam mu da nazove... ali ocito ne zeli...
In Control... MNOGE države imaju mafiju. Ali u Hrvatskoj mafija ima državu...
15 godina
neaktivan
offline
RE: Ruter se može spojit adsl
EnlightenedPhoenix kaže...
Ne kuzis IZGR...

njemu se uopce ne spaja na DSL...

(a za sam DSL nemaš connect nego samo za konekciju koja se ostvaruje preko Digital Subscriber Line-a )

Sto bi opet znacilo da mu vrlo vjerojatno nisu jos DSL ukljucili...

Rekao sam mu da nazove... ali ocito ne zeli...

Aha da,krivo sam razumio,na brzinu sam pročitao prvi post.

Neka nazove T-Scum.

Nulla e reale, tutto e lecito. Requiescat in pace
13 godina
offline
RE: Ruter se može spojit adsl
zvao sam i rekli su da moram čekat tehničara da se vidi kak i šta , jbg, znači još duže bez neta... -.-

a za ovo od IZGR piše mi iznad toga za kliknut connect, disconnected line loopback
14 godina
neaktivan
offline
Ruter se može spojit adsl

Ma daj možeš ih nazvat, utvrdit da li je DSL uključen sa strane T-Coma.

Ako je, provjeri još jednom sve kablove i

zovi ih te namještaj/konfiguriraj modem dok pričaš s njima.

Oni će te vodit stavku po stavku, nemaš tu nikakvih problema.

 

To ti je 5-15 min posla.

 
0 0 hvala 0
13 godina
neaktivan
offline
RE: Ruter se NE može spojit na adsl

bok nadam se da si uspio rjesit problem ako nisi problem je sta nemas stabila signal zaruljica blica jer se priblizava protoku podataka ali nije stabilna je ne svetl zelena da si konektiran bez obzira sta nemas wifi mozes se spojit na t com antenu i ot je to jednostavno cak ti ni netreba adsl wec mrezna karica ili usb sa antenom

antun
16 godina
neaktivan
offline
Ruter se može spojit adsl

Mene su prije 2 i pol godine kad sam tražio uslugu slali da zovem neki njihov 060 broj gdje bi onda aktivirali adsl uslugu kod sebe.

Could it be, nothing that you learned from ash and debris?
 
0 0 hvala 0
13 godina
neaktivan
offline
Ruter se može spojit adsl

da li imaš više od jednog telefona na priključku,ako imaš to ti vjerojatno radi probleme

 
0 0 hvala 0
1
Nova poruka
E-mail:
Lozinka:
 
vrh stranice