Gaming Zone > [MiA] Servers

Server not see in Romania today in my town Ploiesti

<< < (4/6) > >>

HandsomeBob:
I have exactly the same problem (location isp privder, n/a server) as Gaby .

>tracert  80.4.151.145
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.


Tracing route to 80.4.151.145 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.0.1
  2    18 ms    13 ms     7 ms  95.76.169.1
  3     9 ms    11 ms    17 ms  95.77.36.177
  4    15 ms    10 ms     8 ms  136.255.248.200
  5     9 ms    11 ms    14 ms  ae12-100-ucr1.bch.cw.net [195.2.15.49]
  6    15 ms    22 ms    16 ms  ae0-ucr1.clj.cw.net [195.2.8.66]
  7    28 ms    31 ms    34 ms  ae44-xcr1.vie.cw.net [195.2.2.114]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.

Veica:
I got curious and tried it myself, it seelsm like something happens after the traffic gets to London?

hagis:
gaps with "Request timed out" are not in themselves a problem (or indication of a problem) - it means the 'thing' (router or whatever) is not replying to a ping request,. that might well be normal because not every hop on the route can be bothered to reply to ping request

but.. if all you see is  "Request timed out" and it never gets to the server that shows a routing problem

Nardaq_NL:
You can try using a mobile connection by means of a mobile hotspot to see the trace is the same with your mobile ISP.

If HandsomeBob has this issue to I'd say call your ISP and ask them why you can't access the server and the rest of the world can.

q(Ö°Ö)p:
It have been established further above that the game server name "miasma.rocks" have an ip of 80.4.151.145!

So if i do a "ping miasma.rocks" will returns the ip address or "ping -a 80.4.151.145" should returns server name miasma.rocks and the same ip address.

Take look at the following ping and tracert results:

>ping -a 80.4.151.145

Pinging miasma.rocks [80.4.151.145] with 32 bytes of data:
Reply from 80.4.151.145: bytes=32 time=44ms TTL=117
Reply from 80.4.151.145: bytes=32 time=45ms TTL=117
Reply from 80.4.151.145: bytes=32 time=49ms TTL=117
Reply from 80.4.151.145: bytes=32 time=55ms TTL=117

Ping statistics for 80.4.151.145:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 55ms, Average = 48ms

>ping miasma.rocks

Pinging miasma.rocks [172.96.184.193] with 32 bytes of data:
Reply from 172.96.184.193: bytes=32 time=36ms TTL=53
Reply from 172.96.184.193: bytes=32 time=39ms TTL=53
Reply from 172.96.184.193: bytes=32 time=41ms TTL=53
Reply from 172.96.184.193: bytes=32 time=41ms TTL=53

Ping statistics for 172.96.184.193:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 41ms, Average = 39ms

Tracert result to follow....

Navigation

[0] Message Index

[#] Next page

[*] Previous page