Telnet is not working

RouterOS Beginner Basics
1

Hello everybody!I want to learning the next to GUI configuration,the CLI configuration also.

But i can not log in Telnet my RB 750 GL

I am using Ubuntu 10.10 Linux,when i open a terminal i want to use telnet,and trying log in but just this message display:

Trying… and not happend nothing,we have got some other Mikrotik devices in this subnet,and on all RBs working the telnet.

What cause the problem?

Thank for your replies

2

On the mikrotik go to ip.services and make sure Telnet is enabled and that there is no IP address restriction stopping you.

Also check your ip.firewall.filter that no input rules are stopping access.

By default the rb750gl will block any input to ether1.

3

Telnet is enabled,the firewall not blocking,i know the ether1 port is a wan port default,and the ether2 is a master port for eth3-5

I am using now the eth3 port with 10.10.10.10/24 IP address

I reseted the default configuration,but not helped

4

try using ssh

5

Can you use the telnet tool from one of your other routers to talk to the offending mikrotik ?

6

Hello,sorry my late responding,telnet is already working and i want to give for you a description my network:

We have got a little network with some devices:pc,laptop, RB AP…etc

Mikrotik 750 wan port (eth1) on running dhcp client and another from 750 get IP (192.168.1.120 in this case)

There are 2 RB 750 between we have got a tp link switch,for this 8 ports tp link switch connected some devices:pc,laptop,RB 411 AP etc…


I want to asking from you if my RB 750 connected to the switch in this case:

RB 750>>>>>>>>>switch>>>>>PC

I am not experiencing in networks,but the telnet using IP package and the switch Mac frames?So if i want use telnet it is won’t working because the switch will drop IP package?

7

Normally no. The whole purpose of a switch it to forward traffic based on MAC/IP of the devices on it’s various ports. A smart/managed switch can often be configured to drop certain traffic but a common unmanaged switch just forwards packets based on address and who is connected where.

That said, given a choice you should always use ssh rather than telnet. Even if you think your private segement is secure and you trust everyone on it, it’s still a good reflex to aquire. Telnet is a plaintext protocol and open to snooping, packet injection and other issues.

8

Thank you for your reply,i everyday learning something here in this forum