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.
I have a recently installed RH7.1 system and I cannot get the simplest networking features to work. I have Windows 2000 running on another machine. About all I can do is ping in both directions.
I was expecting an FTP daemon to be running on RH7.1 but it is not. xinetd is running and for some reason the configuration for every single service has the disable attribute set to yes.
I've tried setting it to 'no' for ftpd but it makes no difference. When I try FTP from the W2K machine I get the following:
> ftp: connect :Connection reset by peer
I've also tried running the ftpd daemon directly - it doesn't run for long and simply logs a syslog message, i.e.
Myhost ftpd: getpeername ((null)): Socket operation on non-socket.
Similarly, if I try to start the telnet daemon from the command line I get
telnetd: getpeername: Socket operation on non-socket.
I've tried the above after stopping xinetd but it makes no difference.
TCP/IP is set up as follows:
the "getpeername" thingie is a DNS lookup failure.
IIRC the easiest way is to make sure on both boxes the other is known by adding the ip addy and name to the /etc/hosts and %system32%\drivers\etc, and make sure resolv.conf uses file,dns precedence for lookups.