Sagemcom Tools Telnet

Posted on  by 

Mar 22, 2017 Basically, if you don't know the admin password of your SagemCom F@st2704R router, you can still get a root shell with the user account's hardcoded password. Root.sh is a simple shell script that provides the root shell. It interracts with telnet on port 23. Sagemcom is an ever-growing group that designs. And manufactures innovative products. And solutions addressing three fundamental needs: access to energy, access to internet, access to audio/video contents.

-->

You can use Telnet to test Simple Mail Transfer Protocol (SMTP) communication between messaging servers. SMTP is the protocol that's used to send email messages from one messaging server to another. Using Telnet can be helpful if you're having trouble sending or receiving messages because you can manually send SMTP commands to a messaging server. In return, the server will reply with responses that would be returned in a typical connection. These results can sometimes help you to figure out why you can't send or receive messages.

You can use Telnet to test SMTP communication to:

  • Test mail flow from the Internet into your Exchange organization.

  • Test mail flow from your Exchange to another messaging server on the Internet.

Tip

Did you know that, instead of using Telnet to test SMTP connectivity, you can use the Microsoft Remote Connectivity Analyzer at https://testconnectivity.microsoft.com/? With the Remote Connectivity Analyzer, you can choose the connectivity test you want to do, in this case Inbound SMTP Email, and follow the instructions shown. It'll step you through the information you need to enter, run the test for you, and then give you the results. Give it a try!

F@ST

What do you need to know before you begin?

  • Estimated time to complete: 15 minutes

  • Exchange permissions don't apply to the procedures in this topic. These procedures are performed in the operating system of the Exchange server or a client computer.

  • This topic shows you how to use Telnet Client, which is included with Windows. Third-party Telnet clients might require syntax that's different from what's shown in this topic.

  • The steps in this topic show you how to connect to an Internet-facing server that allows anonymous connections using TCP port 25. If you're trying to connect to this server from the Internet, you need to make sure your Exchange server is reachable from the Internet on TCP port 25. Similarly, if you're trying to reach a server on the Internet from your Exchange server, you need to make sure your Exchange server can open a connect to the Internet on TCP port 25.

  • You might notice some Receive connectors that use TCP port 2525. These are internal Receive connectors and aren't used to accept anonymous SMTP connections.

  • If you're testing a connection on a remote messaging server, you should run the steps in this topic on your Exchange server. Remote messaging servers are often set up to make sure the IP address where the SMTP connection is coming from matches the domain in the sender's email address.

  • For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.

Tip

Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.

Sagemcom F@ST 3864 V2 - Get Admin Password

Step 1: Install the Telnet Client on your computer

On most versions of Windows, you'll need to install the Telnet client before you can use it. To install it, see Install Telnet Client.

Step 2: Find the FQDN or IP address of the destination SMTP server

To connect to an SMTP server by using Telnet on port 25, you need to use the fully-qualified domain name (FQDN) (for example, mail.contoso.com) or the IP address of the SMTP server. If you don't know the FQDN or IP address, you can use the Nslookup command-line tool to find the MX record for the destination domain.

Note

Network policies might prevent you from using the Nslookup tool to query public DNS servers on the Internet. As an alternative, you can use one of the freely-available DNS lookup or MX record lookup web sites on the Internet.

  1. At a command prompt, type nslookup, and then press Enter. This command opens the Nslookup session.

  2. Type set type=mx, and then press Enter.

  3. Type the name of the domain for which you want to find the MX record. For example, to find the MX record for the fabrikam.com domain, type fabrikam.com., and then press Enter.

    Note

    When you use a trailing period ( . ), you prevent any default DNS suffixes from being unintentionally added to the domain name.

    The output of the command looks like this:

    You can use any of the host names or IP addresses that are associated with the MX records as the destination SMTP server. A lower value for preference (preference = 10 vs. 20) indicates a preferred SMTP server. Multiple MX records and different values of preference are used for load balancing and fault tolerance.

  4. When you're ready to end the Nslookup session, type exit, and then press Enter.

Step 3: Use Telnet on Port 25 to test SMTP communication

In this example, we're going to use the following values. When you run the commands on your server, replace these values with ones for your organization's SMTP server, domain, etc.

  • Destination SMTP server: mail1.fabrikam.com
  • Source domain: contoso.com
  • Sender's e-mail address: chris@contoso.com
  • Recipient's e-mail address: kate@fabrikam.com
  • Message subject: Test from Contoso
  • Message body: This is a test message

Tip

The commands in the Telnet Client aren't case-sensitive. The SMTP command verbs in this example are capitalized for clarity. You can't use the backspace key in the Telnet session after you connect to the destination SMTP server. If you make a mistake as you type an SMTP command, you need to press Enter, and then type the command again. Unrecognized SMTP commands or syntax errors result in an error message that looks like this: 500 5.3.3 Unrecognized command.

  1. Open a Command Prompt window, type telnet, and then press Enter.

    This command opens the Telnet session.

  2. Type set localecho, and then press Enter.

    This optional command lets you view the characters as you type them, and it might be required for some SMTP servers.

  3. Type set logfile <filename>, and then press Enter.

    This optional command enables logging and specifies the log file for the Telnet session. If you only specify a file name, the log file is located in the current folder. If you specify a path and file name, the path needs to be on the local computer, and you might need to enter the path and file name in the Windows DOS 8.3 format (short name with no spaces). The path needs to exist, but the log file is created automatically.

  4. Type OPEN mail1.fabrikam.com 25, and then press Enter.

  5. Type EHLO contoso.com, and then press Enter.

  6. Type MAIL FROM:<chris@contoso.com>, and then press Enter.

  7. Type RCPT TO:<kate@fabrikam.com> NOTIFY=success,failure, and then press Enter.

    The optional NOTIFY command specifies the particular delivery status notification (DSN) messages (also known as bounce messages, nondelivery reports, or NDRs) that the SMTP is required to provide. In this example, you're requesting a DSN message for successful or failed message delivery.

  8. Type DATA, and then press Enter.

  9. Type Subject: Test from Contoso, and then press Enter.

  10. Press Enter again.

    A blank line is needed between the Subject: field and the message body.

  11. Type This is a test message, and then press Enter.

  12. Type a period ( . ), and then press Enter.

  13. To disconnect from the SMTP server, type QUIT, and then press Enter.

  14. To close the Telnet session, type quit, and then press Enter.

Here's what a successful session using the steps above looks like:

Step 4: Success and error messages in the Telnet Session

This section provides information about the success and failure responses to the commands that were used in the previous example.

Note

The three-digit SMTP response codes that are defined in RFC 5321 are the same for all SMTP messaging servers, but the text descriptions in the responses might be slightly different.

SMTP reply codes

SMTP servers respond to commands with a variety of numerical reply codes in the format of x.y.z where:

  • X indicates whether the command was good, bad, or incomplete.
  • Y indicates the kind of response that was sent.
  • Z provides additional information about the command

Sagemcom F@ST 3864 V2 - Get Admin Password

Tools

When a response is received by the server that opened the connection, it can tell whether the remote server accepted the command and is ready for the next one, or if an error occurred.

The first digit (X) is particularly important to understand because it indicates the success or failure of the command that was sent. Here are its possible values, and their meanings.

Reply codeMeaning
2.y.zThe command that was sent was successfully completed on the remote server. The remote server is ready for the next command.
3.y.zThe command was accepted but the remote server needs more information before the operation can be completed. The sending server needs to send a new command with the needed information.
4.y.zThe command wasn't accepted by the remote server for a reason that might be temporary. The sending server should try to connect again later to see if the remote server can successfully accept the command. The sending server will continue to retry the connection until either a successful connection is completed (indicated by a 2.y.z code) or fails permanently (indicated by a 5.y.z code).
An example of a temporary error is low storage space on the remote server. Once more space is made available, the remote server should be able to successfully accept the command.
5.y.zThe command wasn't accepted by the remote server for a reason that is isn't recoverable. The sending server won't retry the connection and will send a non-delivery report back to the user who sent the message.
An example of an unrecoverable error is a message that's sent to an email address that doesn't exist.

The table above is based on information provided by RFC 5321 (Simple Mail Transfer Protocol), section 4.2.1. Additional information, including descriptions of the second (Y) and third (Z) digits of SMTP reply codes is included in this section, and in sections 4.2.2 and 4.2.3.

OPEN command

Successful response: 220 mail1.fabrikam.com Microsoft ESMTP MAIL Service ready at <day-date-time>

Failure response: Connecting to mail1.fabrikam.com...Could not open connection to the host, on port 25: Connect failed

Possible reasons for failure:

  • The destination SMTP service is unavailable.
  • Restrictions on the destination firewall.
  • Restrictions on the source firewall.
  • Incorrect FQDN or IP address for the destination SMTP server.
  • Incorrect port number.

EHLO command

Successful response: 250 mail1.fabrikam.com Hello [<sourceIPaddress>]

Failure response: 501 5.5.4 Invalid domain name

Possible reasons for failure:

  • Invalid characters in the domain name.
  • Connection restrictions on the destination SMTP server.

Note

EHLO is the Extended Simple Message Transfer Protocol (ESMTP) verb that's defined in RFC 5321. ESMTP servers can advertise their capabilities during the initial connection. These capabilities include the maximum accepted message size and supported authentication methods. HELO is the older SMTP verb that is defined in RFC 821. Most SMTP messaging servers support ESMTP and EHLO. If the non-Exchange server that you're trying to connect to doesn't support EHLO, you can use HELO instead.

MAIL FROM command

Successful response: 250 2.1.0 Sender OK

Failure response: 550 5.1.7 Invalid address

Possible reasons for failure: A syntax error in the sender's e-mail address.

Failure response: 530 5.7.1 Client was not authenticated

Possible reasons for failure: The destination server doesn't accept anonymous message submissions. You receive this error if you try to use Telnet to submit a message directly to a Mailbox server that doesn't have a Receive connector that's configured to accept anonymous connections.

RCPT TO command

Successful response: 250 2.1.5 Recipient OK

Failure response: 550 5.1.1 User unknown

Possible reasons for failure: The specified recipient doesn't exist.

  • 2SpeedTouch
    • 2.4Accessing Telnet
  • 3TP-Link

The operational status of your Sagemcom DSL modem is indicated by lights (LEDs). Sagemcom modems have lights to indicate power, the status and activity of the DSL line, and the status and activity of wireless connections to your computer.

Information is communicated by whether the lights are on, off or flashing. Activity on a line is often indicated by flickering lights, when the line is active.

Here's a summary of how to read the lights on Sagemcom modems:

The operational status of your SpeedTouch DSL modem is usually indicated by lights (LEDs). Different modem models vary in detail, of course, but typically they have lights to indicate power, the status and activity of the DSL line, and the status and activity of connections to your computer, whether by ethernet or by wireless.

The Thomson SpeedTouch 585 modems have five lights on the front (Power, Ethernet, WLAN, DSL and Internet) and four lights on the back, which show the status of each of the four ethernet ports.

Information is communicated by the colour of the lights and whether they are steady or flashing. Activity on a line is often indicated by flickering lights, when the line is active.

Here's a summary of how to read the lights of a Thomson 585 v7 (other models are similar):

LED Light LED Status Troubleshooting Options
Power light steady greenIf it is unlit, there is a power problem or the unit is broken. Check that the modem is plugged in and switched on.
Power light red or amber The unit has discovered a problem. Try unplugging the unit from the power and disconnecting it from all cables, waiting more than 5 seconds (for capacitors to discharge) and then connecting it to power again. If the power light goes green, then connect cables. Otherwise, if the power light remains red or amber then the unit is most likely broken and will have to be replaced.
Ethernet light green (steady or flickering) As long as there is at least one ethernet cable connected to a working computer. Ethernet traffic is indicated by flickering of the light. To check individual cables, most SpeedTouch modems have green LEDs at the back of the modem where the ethernet cables plug in which will be green (and flicker with activity) if ethernet is active on that particular cable.
WLAN light flashes indicate wireless activity. The colour of the light indicates the security mode of the wireless service
WLAN light green is highest security, using WPA encryption
WLAN light amber is medium security, using WEP;
WLAN light red indicates no security (anyone can use your wireless without providing a password)
WLAN light unlit wireless is disabled (turned off)
Broadband (DSL) light steady green indicating that the unit has detected a DSL signal and is able to synchronize with it. It indicates that the unit is in sync.
Broadband (DSL) light flash green During the process of obtaining DSL synchronization, the Broadband light flashes . If it flashes indefinitely, there is a problem.
Internet light steady green the Central Office has accepted your modem's login and password and is ready to provide internet service via DSL to your modem.
Internet light red or unlit there is a problem

Troubleshooting Notes

  1. For information about configuring wireless and enabling/disabling it, please consult the modem manual for your unit.
  2. If you previously had a working connection and nothing has changed at your location (eg., no new devices attached to your phone line), try power cycling your modem (see above). If that doesn't work, likely it's an external problem and it is best to wait 10 minutes and see if it clears up. Sometimes the modem needs to be power-cycled for it to notice a line that has returned to service and to connect to it.
  3. If you are installing the modem for the first time, and the DSL Light keeps flashing here are possible solutions:
    • Make sure there is no filter on the line that connects your modem to the phone line. The modem must be plugged directly into the phone line.
    • Make sure all other devices, including telephones, answering machines, fax machines and security alarms at your location are connected through DSL line filters.
    • If problems persist, try temporarily disconnecting all other devices from your phone line as a phone or even a filter that is failing can cause interference.
  4. If you can find a working internet connection (by dial-up, cellphone, at a friend's home or at an office or library), you can check online with NCF to see if anyone else is experiencing problems. If not, it is best to send a problem report to the NCF office for further action.
  5. If your unit was able to log in earlier and you have not made any changes, a red internet light likely means that there is a temporary network problem (at the Central Office or NCF) making it temporarily impossible to check your login and password. In this case it is best to just wait for the problem to be fixed. You may need to power-cycle or restart your modem for it to notice that service has been restored. If you can get online elsewhere (by dial-up, at a friend's home or at an office or library), you can check the NCF web site to see if others are experiencing problems. If not, report the problem, although network-wide problems are almost always noticed quickly.
  6. If you are installing your modem for the first time and the DSL light is green but the Internet light is red, likely your unit hasn't been configured with a correct login and password. Check the configuration instructions for information about configuring.
  7. If you are having problems and find any of the back-side ethernet LEDs flashing at a steady rate (on-off-on-off...), it indicates a hardware problem that requires service, but try power-cycling just in case that resolves it.

Beyond the lights

Lights can indicate only a small amount of information about your modem. To learn more about what your modem is doing, you can view your DSL usage log (this link is also available from the NCF StartPage, under 'Internet Access'). Often the pattern of connect/disconnects will reveal more information.

It is also possible to log into your modem (there is a computer with a UNIX operating system in there) using a web browser, and then view its event log. For information about the modem's event log, consult the modem manual for your modem model.

Troubleshooting reboots

Sagemcom Tools Telnet 2764 Download

Some older ST585 units have had problems as they seem to reboot themselves over and over. One member solved this by telnetting into the unit via command line and deactivating Universal Plug and Play (UPnP):

Accessing Telnet

Linux and Mac

On Linux operating systems you can access telnet by opening a terminal and typing in 'telnet 192.168.1.254' at the prompt.

Windows

On Windows XP and Vista operating systems telnet can be accessed by opening 'run' and the 'cmd' command and entering telnet.

In Windows 7 and 8 you can bring up the command line by entering 'cmd' in the search bar.

In any version of Windows you can also run telnet by installing and using the PuTTY free software application.

The operational status of your TP-Link DSL modem is indicated by lights (LEDs). TP-Link modems have lights to indicate power, the status and activity of the DSL line, and the status and activity of connections to your computer, whether by ethernet or by wireless.

TP-Link modems have lights on the front (8901G and 8950) or the top (8816, 8951, 8961 and 9970).

Information is communicated by whether the lights are on, off or flashing. Activity on a line is often indicated by flickering lights, when the line is active.

This article includes a summary of how to read the lights on TP-Link modems.

TD-8816

Power
Should be solid green. If it is unlit, there is a power problem or the unit is broken. Check that the modem is plugged in and switched on.
LAN (Local Area Network)
Should be solid green if a computer is connected to the ethernet port.
ADSL (Asymmetric Digital Subscriber Line)
Flashes green when the modem is synchronizing, will be solid green once synchronization has occurred.

Optus NBN - Router Admin Access, Using A BYO Router With VOIP

Internet
Will illuminate green when authentication has been successful, and will flash to show data traffic.

TD-W8901G & TD-W8950ND

Power
Should be solid green. If it is unlit, there is a power problem or the unit is broken. Check that the modem is plugged in and switched on.
ADSL (Asymmetric Digital Subscriber Line)
Flashes green when the modem is synchronizing, will be solid green once synchronization has occurred.
Internet
Will illuminate green when authentication has been successful, and will flash to show data traffic.
WLAN light (Wireless Local Area Network)
Will be solid green or flashing green if a computer is connected to the wireless.
Numbers
These lights correspond to Ethernet ports connected. These will show a solid green light when a computer is connected to the corresponding port by Ethernet cable and will flash to show data traffic.

TD-W8951ND, TD-W8961ND & TD-W9970N

Sagemcom Tools Telnet
  1. If the DSL LED is off, check your internet connection first.
  2. If the internet LED is off, check your DSL LED first. If your DSL LED is also off, please refer to Note 1. If your DSL LED is GREEN ON, check your internet configuration.

Internet

The internet light is steady green when the NCF authentication server has accepted your modem's login and password and is ready to provide internet service via DSL to your modem. If the light remains unlit, there is a problem.

If your unit was able to log in earlier and you have not made any changes, an unlit light likely means that there is a temporary network problem (at the Central Office or NCF) making it temporarily impossible to check your login and password. In this case it is best to just wait for the problem to be fixed. You may need to power-cycle or restart your modem for it to notice that service has been restored. If you can get online elsewhere (by dial-up, at a friend's home or at an office or library), you can check the NCF web site to see if others are experiencing problems. If not, report the problem, although network-wide problems are almost always noticed quickly.

If you are installing your modem for the first time and the DSL light is green but the Internet light is unlit, likely your unit has not been configured with a correct login and password. Check the configuration instructions for information about configuring:

Beyond the lights

Lights can indicate only a small amount of information about your modem. To learn more about what your modem is doing, you can view your DSL usage log (this link is also available from the NCF StartPage, under 'Internet Access'). Often the pattern of connect/disconnects will reveal more information.

It is also possible to log into your modem (there is a computer with a Linux operating system in there) using a web browser, and then view its event log. For information about the modem's event log, consult the modem manual for your modem model.

The operational status of your SmartRG DSL modem is indicated by lights (LEDs). SmartRG modems have lights to indicate power, Wide Area Network (WAN), Local Area Network (LAN), wireless (WLAN), Wi-Fi Protected Set-up (WPS), DSL and Internet connection.

Information is communicated by whether the lights are green, red, off or flashing. Activity on a line is often indicated by flickering lights, when the line is active.

Here's a summary of how to read the lights on SmartRG modems:

Retrieved from 'https://help.ncf.ca/index.php?title=Modem_Lights&oldid=5608'

Coments are closed