Neurochirurgie minim invazivă
"Primum non nocere" este ideea ce a deschis drumul medicinei spre minim invaziv. Avansul tehnologic extraordinar din ultimele decenii a permis dezvoltarea tuturor domeniilor medicinei. Microscopul operator, neuronavigația, tehnicile anestezice avansate permit intervenții chirurgicale tot mai precise, tot mai sigure. Neurochirurgia minim invazivă, sau prin "gaura cheii", oferă pacienților posibilitatea de a se opera cu riscuri minime, fie ele neurologice, infecțioase, medicale sau estetice. www.neurohope.ro |
Nu se incarca paginile web cum trebuie
Last Updated: Feb 11 2017 22:15, Started by
musicallro
, Feb 11 2017 20:03
·
0
#1
Posted 11 February 2017 - 20:03
Ce se intampla? Sa fie probleme de la ISP? Astazi pentru prima data pe conexiunea de VDSL nu se incarca paginile asa cum trebuie (fonturi, imagini si css). Cand am intrat de pe telefon prin WIFI imi facea aceeasi faza...
Am atasat un ex. cu pagina https://fonts.google.com/ Mi-a mers corect si paginile s-au incarcat normal doar cand m-am conectat la net prin alt provider si am realizat tethering catre laptop. Sigur nu e din browser... cum am schimbat providerul cum s-au incarcat paginile corect. Ceva sugestii? Attached FilesEdited by musicallro, 11 February 2017 - 20:25. |
#2
Posted 11 February 2017 - 20:14
Daca dai un F5 nu isi revin paginile ?
Poti incerca si un restart la modem/router. |
#3
Posted 11 February 2017 - 20:14
musicallro, on 11 februarie 2017 - 20:03, said:
Ce se intampla? Sa fie probleme de la ISP? ......................... ................................................................................... Sigur nu e din browser... cum am schimbat providerul cum s-au incarcat paginile corect. Ceva sugestii? |
#4
Posted 11 February 2017 - 20:17
#5
Posted 11 February 2017 - 20:27
Eu sunt tot pe VDSL si nu am probleme, ce-i drept folosesc dns-urile de la opendns. Incearca si tu, poate e vreun dns care raspunde prost.
|
#6
Posted 11 February 2017 - 20:29
Ce DNS folosesti? Dupa ce le salvezi dai reboot la modem?
Update: Le-am pus pe cele de la google tot asa apare... Update 2: Gata afiseaza acum corect cu DNS-urile de la google! Attached FilesEdited by musicallro, 11 February 2017 - 20:37. |
#7
Posted 11 February 2017 - 20:37
Atunci deschide in chrome developer tools (ctrl shift i) si in tabul network vezi ce se intampla exact. Ar trebui sa vezi de ce unele elemente nu se descarca.
LE: sa stergi si cache din windows dupa ce ai schimbat dns-urile (ipconfig /flushdns). LE2: Opendns raspunde mult mai repede decat google, fiind conectati in interlan: Pinging 208.67.222.222 with 32 bytes of data: Reply from 208.67.222.222: bytes=32 time=14ms TTL=58 Reply from 208.67.222.222: bytes=32 time=14ms TTL=58 Reply from 208.67.222.222: bytes=32 time=14ms TTL=58 Reply from 208.67.222.222: bytes=32 time=14ms TTL=58 Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=28ms TTL=57 Reply from 8.8.8.8: bytes=32 time=28ms TTL=57 Reply from 8.8.8.8: bytes=32 time=28ms TTL=57 Tracing route to google-public-dns-a.google.com [8.8.8.8] over a maximum of 30 hops: 1 3 ms <1 ms <1 ms 192.168.10.1 2 14 ms 14 ms 13 ms 109.102.182.1 3 27 ms 31 ms 27 ms 10.0.244.65 4 28 ms 27 ms 27 ms 10.0.201.161 5 30 ms 28 ms 28 ms 10.0.200.70 6 28 ms 27 ms 27 ms 72.14.210.42 7 27 ms 31 ms 27 ms 209.85.248.217 8 28 ms 28 ms 28 ms google-public-dns-a.google.com [8.8.8.8] Tracing route to resolver1.opendns.com [208.67.222.222] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.10.1 2 14 ms 14 ms 15 ms 109.102.182.1 3 14 ms 14 ms 14 ms 10.0.221.73 4 15 ms 15 ms 15 ms 10.0.201.165 5 14 ms 14 ms 14 ms 10.0.241.238 6 14 ms 14 ms 14 ms opendns.interlan.ro [86.104.125.121] 7 14 ms 14 ms 14 ms resolver1.opendns.com [208.67.222.222] Edited by MembruAnonim, 11 February 2017 - 20:53. |
#8
Posted 11 February 2017 - 21:09
Asta e ping-ul pe care il am cu 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=63ms TTL=45 Reply from 8.8.8.8: bytes=32 time=64ms TTL=45 Reply from 8.8.8.8: bytes=32 time=63ms TTL=45 Reply from 8.8.8.8: bytes=32 time=63ms TTL=45 Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 63ms, Maximum = 64ms, Average = 63ms Iar dupa ce am schimbat DNS-urile in opendns.com Pinging 208.67.222.222 with 32 bytes of data: Reply from 208.67.222.222: bytes=32 time=22ms TTL=57 Reply from 208.67.222.222: bytes=32 time=22ms TTL=57 Reply from 208.67.222.222: bytes=32 time=22ms TTL=57 Reply from 208.67.222.222: bytes=32 time=22ms TTL=57 Ping statistics for 208.67.222.222: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 22ms, Maximum = 22ms, Average = 22ms -- Pinging www.google.com [80.97.208.34] with 32 bytes of data: Reply from 80.97.208.34: bytes=32 time=18ms TTL=56 Reply from 80.97.208.34: bytes=32 time=18ms TTL=56 Reply from 80.97.208.34: bytes=32 time=18ms TTL=56 Reply from 80.97.208.34: bytes=32 time=18ms TTL=56 Ping statistics for 80.97.208.34: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 18ms, Maximum = 18ms, Average = 18ms Edited by musicallro, 11 February 2017 - 21:15. |
#9
Posted 11 February 2017 - 22:15
Corect e asa
"Pinging 208.67.222.222 with 32 bytes of data: Reply from 208.67.222.222: bytes=32 time=3ms TTL=60 Reply from 208.67.222.222: bytes=32 time=1ms TTL=60 Reply from 208.67.222.222: bytes=32 time<1ms TTL=60 Reply from 208.67.222.222: bytes=32 time=1ms TTL=60 Ping statistics for 208.67.222.222: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 3ms, Average = 1ms Opendns-urile merg foarte bine pentru ca te ruteaza pe locale. Edited by andreic, 11 February 2017 - 22:15. |
Anunturi
▶ 0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users