Question: |
Do not open these sites on your hosting:Merekehotel.kzUkzto.comSvinecstroy.kzНе work through our provider \"Megaline\", but work through provider \"Beeline\". (Kazakhstan, East Kazakhstan, Ust-Kamenogorsk)Ping and tracert through the \"Megaline\":Microsoft Windows [Version 6.2.9200](c) Corporation Microsoft, 2012. All rights reserved.C:\\Users\\***>tracert svinecstroy.kzТрассировка route to svinecstroy.kz [91.231.84.106]with a maximum of 30 hops: 1 1 ms 1 ms 1 ms 2 192.168.3.3 9 ms 8 ms 14 ms 95.58.176.8.megaline.telecom.kz [95.58.176.8] 3 8 ms 8 ms 7 ms 95.57.217.58 4 85 ms 82 ms 82 ms ustk-core-l2-1-2.online.kz [95.59.170.90] 5 91 ms 90 ms 90 ms 92.47.144.178 6 85 ms 85 ms 83 ms asta-core-l1-1-2.online.kz [92.47.145.50] 7 30 ms 30 ms 29 ms asta-gate-1.online.kz [92.47.151.166] 8 81 ms 78 ms 78 ms 92.47.144.138 9 91 ms 90 ms 90 ms 178.18.226.172.msk.peering.dataix.ru [178.18.226.172] 10 87 ms 87 ms 94 ms ukrnames.maxnet.ua [79.171.125.210] 11 90 ms 90 ms 90 ms zala.host17.info [91.231.84.106]Trace complete.C:\\Users\\***>ping svinecstroy.kzОбмен packs svinecstroy.kz [91.231.84.106] with 32 bytes of data:Reply from 91.231.84.106: bytes=32 time=88мс TTL=55Ответ from 91.231.84.106: bytes=32 time=91мс TTL=55Ответ from 91.231.84.106: bytes=32 time=87мс TTL=55Ответ from 91.231.84.106: bytes=32 time=102мс TTL=55Статистика 91.231.84.106 to Ping: Packets: sent = 4, received = 4, lost = 0 (0% of losses)Approximate time of reception-transfer in a msec: Minimum = 87мсек, Maximum = 102 msec, Average = 92 MS Ping and tracert via Beeline: Microsoft Windows [Version 6.2.9200](c) Corporation Microsoft, 2012. All rights reserved.C:\\Users\\***>tracert svinecstroy.kzТрассировка route to svinecstroy.kz [91.231.84.106]with a maximum of 30 hops: 1 <1 MS <1 MS <1 MS 192.168.3.5 2 1 ms 1 ms 1 ms comp35-83.2day.kz [80.241.35.83] 3 1 ms 2 ms 1 ms 172.25.255.225 4 5 ms 1 ms 1 ms comp35-253.2day.kz [80.241.35.253] 5 3 ms 5 ms 1 ms comp35-149.2day.kz [80.241.35.149] 6 * * * timed for the request. 7 21 ms * 28 ms 46.227.189.37 8 85 ms 77 ms 78 ms 213.33.228.201 9 81 ms 77 ms 78 ms p3.Moscow.gldn.net [79.104.235.81] 10 99 ms 101 ms 95 ms mx01.Stockholm.gldn.net [79.104.225.38] 11 126 ms 120 ms 120 ms r22.amstnl02.nl.bb.gin.ntt.net [195.69.144.36] 12 * 121 ms 120 ms ae-3.r23.amstnl02.nl.bb.gin.ntt.net [129.250.2.158] 13 128 ms 126 ms 126 ms ae-1.r20.frnkge04.de.bb.gin.ntt.net [129.250.3.178] 14 138 ms 131 ms 131 ms ae-2.r02.frnkge03.de.bb.gin.ntt.net [129.250.5.218] 15 126 ms 129 ms 151 ms 213.198.77.214 16 166 ms 166 ms 175 ms ae0-6.RT.BH.HRK.UA.retn.net [87.245.233.193] 17 175 ms * 161 ms GW-MaxNet.retn.net [87.245.243.210] 18 170 ms * 162 ms ukrnames.maxnet.ua [79.171.125.210] 19 164 ms 164 ms 165 ms zala.host17.info [91.231.84.106]Trace complete.C:\\Users\\***>ping svinecstroy.kzОбмен packs svinecstroy.kz [91.231.84.106] with 32 bytes of data:Reply from 91.231.84.106: bytes=32 time=162мс TTL=45Ответ from 91.231.84.106: bytes=32 time=170мс TTL=45Ответ from 91.231.84.106: bytes=32 time=168мс TTL=45Ответ from 91.231.84.106: bytes=32 time=168мс TTL=45Статистика 91.231.84.106 to Ping: Packets: sent = 4, received = 4, lost = 0 (0% of losses)Approximate time of reception-transfer in a msec: Minimum = 162мсек, Maximum = 170 MS, Average = 167 MS |
Question: |
Also cant get into CPanel |
Question: |
http://i67.fastpic.ru/big/2014/0730/87/70fe53fc195945fb560900f5e1921b87.jpg |
Answer: |
Hello. The problem is not with the website and not with the server but your Internet provider. you`re from Kazakhstan? we can transfer your website to another server if your ISP have problems accessing the current |
Question: |
Then you need to do it.Just a week or two ago everything was fine. |
Answer: |
n andelu two, but two days ago, everything was fine, what hit them we do not know contacts theirs we have no |
Question: |
About their contacts: http://megaline.kz/kontakti (East Kazakhstan Region) |
Answer: |
account moved Details sent to [email protected]
|
Question: |
The site is still not open. What to do? |
Answer: |
please Make a trace to Your domain: start - run - enter cmd - in the black window enter tracert YOUR DOMAIN - after-click to select - enter to get to skopirovat here in the ticket
If You are zatrudina, watch a training video http://ded07.net/helphost/tracert.htm |
Question: |
Now sites do not open with error \"the webpage is not available\"Route also fails.Log in CPanel doesn`t work (even copy-pasting details from letter)http://i65.fastpic.ru/big/2014/0801/66/decf0ec5c1bf96320eb4486910a31066.jpg |
Answer: |
please Check now. If you did not receive access, please inform your IP, we will check it for binding. Your IP you can find on the site 2ip.ru |
Question: |
Still does not work.Address: 2.134.199.216 the Name of your computer: 2.134.199.216.megaline.telecom.kzОперационная system: Microsoft Windows 8.0 Your browser: Opera Next 0Откуда you: Kazakhstan Your ISP: Megaline Proxy: No используетсяhttp://i68.fastpic.ru/big/2014/0801/5d/09539d6a978d31164072950f3d3b575d.jpg |
Answer: |
This IP is not blocked. Please provide the full text of the resulting trace. |
Question: |
Microsoft Windows [Version 6.2.9200](c) Corporation Microsoft, 2012. All rights reserved.C:\\Users\\***>tracert svinecstroy.kzНе resolve target system name svinecstroy.kz.C:\\Users\\***>tracert ukzto.doubt resolve target system name ukzto.com.C:\\Users\\***>tracert merekehotel.kzНе resolve target system name merekehotel.kz.C:\\Users\\***> |
Answer: |
please make a trace to the server 144.76.202.179 |
Answer: |
please Check now.
|
Question: |
It worked, thank you. |
Answer: |
ok
|
Question: |
Tracert scares:C:\\Users\\***>144.76.202.179 tracert Tracing route to tisza.hostven02.ru [144.76.202.179]with a maximum of 30 hops: 1 <1 MS <1 MS <1 MS 192.168.3.2 2 * * * timed out for the request. 3 * * * timed for the request. 4 * * * timed for the request. 5 * * * timed for the request. 6 * * * timed for the request. 7 * * * timed for the request. 8 * * * timed for the request. 9 * * * timed for the request. 10 * * * timed for the request. 11 * * * timed for the request. 12 * * * timed for the request. 13 * * * timed for the request. 14 144 ms 143 ms 140 ms tisza.hostven02.ru [144.76.202.179]Trace complete.C:\\Users\\***>144.76.202.179 tracert Tracing route to tisza.hostven02.ru [144.76.202.179]with a maximum of 30 hops: 1 <1 MS <1 MS <1 MS 192.168.3.2 2 * * * timed out for the request. 3 * * * timed for the request. 4 * * * timed for the request. 5 * * * timed for the request. 6 * * * timed for the request. 7 * * * timed for the request. 8 * * * timed for the request. 9 * * * timed for the request. 10 * * * timed for the request. 11 * * * timed for the request. 12 * * * timed for the request. 13 * * * timed for the request. 14 140 ms 140 ms 143 ms tisza.hostven02.ru [144.76.202.179]Trace complete.C:\\Users\\***> |
Answer: |
do you operate websites? a strange sort of tracing. trace your packets don`t go any further than your computer |
Question: |
The sites are working. Loaded with no problems even. Tracert same as above, but normal pings:Microsoft Windows [Version 6.2.9200](c) Corporation Microsoft, 2012. All rights reserved.C:\\Users\\***>ping svinecstroy.kzОбмен packs svinecstroy.kz [144.76.202.179] with 32 bytes of data:Reply from 144.76.202.179: bytes=32 time=141мс TTL=52Ответ from 144.76.202.179: bytes=32 time=140мс TTL=52Ответ from 144.76.202.179: bytes=32 time=139мс TTL=52Ответ from 144.76.202.179: bytes=32 time=144мс TTL=52Статистика Ping to 144.76.202.179: Packets: sent = 4, received = 4, lost = 0 (0% of losses)Approximate time of reception-transfer in a msec: Minimum = 139мсек, Maximum = 144 MS, Average = 141 msecs:\\Users\\***>ping 144.76.202.179 pinging 144.76.202.179 on with 32 bytes of data:Reply from 144.76.202.179: bytes=32 time=143мс TTL=52Ответ from 144.76.202.179: bytes=32 time=143мс TTL=52Ответ from 144.76.202.179: bytes=32 time=143мс TTL=52Ответ from 144.76.202.179: bytes=32 time=143мс TTL=52Статистика Ping to 144.76.202.179: Packets: sent = 4, received = 4, lost = 0 (0% of losses)Approximate time of reception-transfer in a msec: Minimum = 143мсек, Maximum = 143 msec, Mean = 143 MS |
Answer: |
so you blocked part of the snmp packets by your ISP. |