Jump to content

SUBIECTE NOI
« 1 / 5 »
RSS
Plasa de umbrire peste gard de pl...

O smecherie pe care nu o inteleg

Balcon parter fara acte

unde gasesc un speed bag in bucur...
 Programe TV cu altfel de sporturi

Laptop "bun la toate" max...

navigatie noua vw tiguan

ctfmon.exe - System Error (in Saf...
 Ați prins vremurile cand 120 Volț...

Whatsapp nu afișeaza numele ...

Medii admitere Politehnica Bucure...

Se extinde Baza de la Kogalniceanu
 Politist mutilat de caine in curt...

Trotineta- cat rezista?

Windows 11 si inregistrare de pe ...

Cont Facebook spart
 

Problema WAN Router ZyXeL!

- - - - -
  • Please log in to reply
5 replies to this topic

#1
Alyn1998

Alyn1998

    New Member

  • Grup: Members
  • Posts: 13
  • Înscris: 11.11.2014
Am un router ZyXeL NBG-416N, la care atunci cand conectez cablul de internet(cel din stalp) in WAN nu mi se aprinde beculetul si, logic, nu merge internetul. Acum va scriu cu cablul conectat in LAN(adica folosesc practic reuter-ul ca un prelungitor :) ). Am incercat sa dau reset, l-am reconfigurat(la WAN acolo cu numele si parola de la ISP), dar tot nu merge. uitati rezultatele pingurilor:

Microsoft Windows [Version 6.4.9860]
© 2014 Microsoft Corporation. All rights reserved.
C:\Users\Duruian>ping 188.209.103.247
Pinging 188.209.103.247 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Ping statistics for 188.209.103.247:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
C:\Users\Duruian>ping 198.162.1.1
Pinging 198.162.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 198.162.1.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Duruian>1p
'1p' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Duruian>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Duruian>ping 74.125.45.100
Pinging 74.125.45.100 with 32 bytes of data:
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Ping statistics for 74.125.45.100:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
C:\Users\Duruian>ping yahoo.com
Ping request could not find host yahoo.com. Please check the name and try again.
C:\Users\Duruian>ipconfig
Windows IP Configuration

Ethernet adapter Ethernet:
   Connection-specific DNS Suffix  . : zyxel.com
   Link-local IPv6 Address . . . . . : fe80::192b:f32e:c508:b18%3
   IPv4 Address. . . . . . . . . . . : 192.168.1.52
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
Tunnel adapter Local Area Connection* 3:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
Tunnel adapter isatap.zyxel.com:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : zyxel.com
C:\Users\Duruian>ping 192.168.1.52
Pinging 192.168.1.52 with 32 bytes of data:
Reply from 192.168.1.52: bytes=32 time<1ms TTL=128
Reply from 192.168.1.52: bytes=32 time<1ms TTL=128
Reply from 192.168.1.52: bytes=32 time<1ms TTL=128
Reply from 192.168.1.52: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.52:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Duruian>ping 192.168.1.189
Pinging 192.168.1.189 with 32 bytes of data:
Reply from 192.168.1.52: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.189:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss)

#2
carmenclara1

carmenclara1

    Guru Member

  • Grup: Moderators
  • Posts: 19,371
  • Înscris: 08.12.2008
despre ce distante discutam?  de ce ai da ping pe propriul ip chiar nu inteleg!  

ofera mai multe detalii despre tot setupul.

#3
Alyn1998

Alyn1998

    New Member

  • Grup: Members
  • Posts: 13
  • Înscris: 11.11.2014

 carmenclara1, on 24 noiembrie 2014 - 21:11, said:

despre ce distante discutam?  de ce ai da ping pe propriul ip chiar nu inteleg!  

ofera mai multe detalii despre tot setupul.
Am dat ping pe IP-ul meu ca asa am gasit pe net sa fac... adica sa dau ping pe toate adresele. Am un pc cu dual-core 2.4, 4 gb ram, no big deal.
Problema cred ca e cu router-ul si oricate resetari si reinregistrari i-as da se conporta la fel. Router-ul merge; dar nu cred ca e ceva de la mn idn PC. Adevarul e ca folosesc Windows 10 Preview dar nu am probleme cu alte aplicatii, plus ca netul merge daca ma conectez direct la cablul din stalp. Eu vreau sa folosesc router-ul, logic, pentru wireless; dar nu merge.
Nu stiu ce informatii sa mai dau... daca mai vreti sa aflati ceva scrieti aici.

#4
carmenclara1

carmenclara1

    Guru Member

  • Grup: Moderators
  • Posts: 19,371
  • Înscris: 08.12.2008
cloneaza adresa mac de pe calculator pe router si vezi daca merge. daca nu cablu si/sau mufe noi (de calitate)

#5
Alyn1998

Alyn1998

    New Member

  • Grup: Members
  • Posts: 13
  • Înscris: 11.11.2014

 carmenclara1, on 25 noiembrie 2014 - 22:39, said:

cloneaza adresa mac de pe calculator pe router si vezi daca merge. daca nu cablu si/sau mufe noi (de calitate)
Am incercat cu MAC si cu mufe.. nimic:(

POST UPDATE!!!
De curand mi s-a reparat din senin problema(am bagat odata mufa inapoi in WAN sa vad daca se intampla vreun miracol, si s-a intamplat :D). A mers asa cateva zile, dupa mi s-a intamplat ca a inceput netul sa mearga prost iar dupa ce l-am deconectat iarasi nu se mai aprindea becul la WAN. Si din nou stau fara WAN. Am sunat la IPS si am cautat si pe net si aparent nu s-a schimbat nimic in transmiterea datelor.(Poate suna putin deplasat dar eu ma gandeam ca cei de la companie trimit mai multe feluri de unde si unele nu-s recunoscute de router :))))

#6
carmenclara1

carmenclara1

    Guru Member

  • Grup: Moderators
  • Posts: 19,371
  • Înscris: 08.12.2008
semnalul nefiind optic,  nu putem discuta de unde.

Anunturi

Bun venit pe Forumul Softpedia!

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Forumul Softpedia foloseste "cookies" pentru a imbunatati experienta utilizatorilor Accept
Pentru detalii si optiuni legate de cookies si datele personale, consultati Politica de utilizare cookies si Politica de confidentialitate