Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
There is a file in the /etc/ direcroty; i forget the name. It contains all of the devices (serial, telnet, etc) that root is allowed to login from. I suggest you use ssh instead of telnet, as your communications are encrypted, and you can login as root.
the SSH suggestion is the most likely to serve what you need. SSH is far more secure than telnet, and will give you full terminal funcionality from a remote system.
To use SSH from a Windows box to your linux host, you will need a program that can do SSH. My favorite is PuTTY, which gives both Telnet and SSH capability. Search on the internet for PuTTY and it should do what you need.