M
M
Muzhaos2014-04-10 10:57:38
Domain Name System
Muzhaos, 2014-04-10 10:57:38

Can't ping external addresses from client machines (Mikrotik)

Good afternoon.
The problem is this: There is a Mikrotik RB2011 router, Router OS 6.11. There is no ping from client machines to external addresses. That is, if I write "yandex.ru" in the browser, I will get where I need to, but if I write ping yandex.ru in the console, it will determine the IP address, but the ping will not work. The same goes for 8.8.8.8. From Mikrotik itself, ping goes anywhere. The network also has a DNS server on Windows 2012, and for the same reason it cannot fight on public DNS, only on Mikrotik within the network, and it already fights on the provider's DNS.
I understand that the problem is somewhere either in the routes or in the rules. But I tried to disable all the rules that I have written there - the effect is zero. Yes, and there are no such rules ... Poke your nose where to look.
Thank you.

Answer the question

In order to leave comments, you need to log in

6 answer(s)
O
Oleg Burca, 2014-04-10
@Muzhaos

You need to set up a masquerade (masquerade/srcnat).

G
German Sukhachev, 2014-04-10
@g3fox

On Mikrotik in the direction of the "outside" is everything closed, except for the 80th port?

V
Valentine, 2014-04-10
@vvpoloskin

1. Watch the nata rules
2. Watch the firewall on the hardware
3. Watch the firewall on client machines.

S
Sergey, 2014-04-10
@edinorog

reset the firmware to default.

K
Kirill 1, 2014-04-11
@SmileyK

@Muzhaos try to update, a lot of things have been fixed compared to 6.11
www.mikrotik.com/download/share/routeros-mipsbe-6....

G
Grims, 2014-05-16
@grims

Colleagues, the problem is with a bug in 6.11, update to 6.13 (release date 15-05-2014)
WAS:
C:\Users\Test>ping yandex.ru -t
Packet exchange with yandex.ru [93.158.134.11] with 32 bytes of data :
Request timed out.
Timed out request.
Ping stats for 93.158.134.11: Packets
: Sent = 509, Received = 20, Lost = 489 (96% loss)
Approximate Round Trip Time in ms:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
\Test>tracert 87.250.251.3
Trace route to www.yandex.ru [87.250.251.3]
with a maximum number of hops 30:
1 <1 ms <1 ms <1 ms 172.100.100.1
2 * * * Query timed out.
3 * * * Query timed out.
4 1 ms <1 ms 1 ms 217.106.30.222
5 * * * Query timed out.
6 3 ms 3 ms 3 ms iva-p2-be5.yndx.net [87.250.239.19]
7 * * * Request timed out.
.....
30 * * * Query timed out.
BECOMING:
C:\Users\Test>ping yandex.ru -t
Packet exchange with yandex.ru [93.158.134.11] with 32 bytes of data:
Response from 93.158.134.11: number of bytes=32 time=2ms TTL=56
Response from 93.158.134.11: byte count=32 time=2ms TTL=56
Response from 93.158.134.11: byte count=32 time=2ms TTL=56
Ping statistics for 93.158.134.11:
Packets: sent=3, received=3, lost = 0 (0% loss)
Approximate round-trip time in ms:
Minimum = 2ms, Maximum = 2ms, Average = 2ms
C:\Users\Test>tracert yandex.ru
Tracert route to yandex.ru [93.158.134.11]
with max hop count 30:
1 <1 ms <1 ms <1 ms 172.100.100.1
2 1 ms <1 ms <1 ms xxx.xxx.0.133
3 1 ms 1 ms <1 ms 217.107.215.217
4 * * * Interval exceeded waiting for a request.
5 * * * Query timed out.
6 * * * Query timed out.
7 1 ms 1 ms 1 ms ugr-b-c1-ae5.yndx.net [87.250.239.97]
8 2 ms 1 ms 1 ms yandex.ru [93.158.134.11]
Tracing completed.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question