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.
This is probably (and hopefully) a stupid question with a trivial answer, so sorry in advance!
I've just installed CentOS 4.4, and all seems to be OK. What I'm attempting to do is to set the remote hostname of the computer (terminology probably wrong, but I'll attempt to explain).
The 'local' hostname of the computer is fine; when I log in, I see:
Which I was expecting. Typing 'hostname' returns 'webserver'.
What I do want to be able to do is to refer to the computer as //webserver from other computers on the network. The other Linux box (running FC5) can be accessed by //linuxserver... Could someone explain where I've gone wrong?
(As an aside, when I login via SSH, the 'password:' prompt takes a while - about 10-20 seconds - to appear; is this a function of me having cocked the DNS settings up a bit?)
//webserver would pull it up if
a) webserver was first resolved as the IP of this host from the host on which you're trying to pull it up in the browser (has to do with the DNS/resolv.conf on that machine rather than anything on webserver itself.
b) You are running something that is listening on the standard httpd port (80) on webserver. ("lsof -i :80" would verify that).
c) You are not blocking outside connections to port 80 in the firewall on webserver, firewall between the boxes or firewall on the server where you ran the browser.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 184.108.40.206, KDE 3.5.8 and KDE 4.0 beta, Plu
You want other machines to see the machine as //winserver instead of just a plain IP. For that to work on say the fc5 box you will need to edit /etc/hosts file and add a reference for the IP to hostname.
For ssh log delay can depend on a few things. I assume both machines are on the same network segment? If so then my guess the ssh conection is trying to do passphrases first. Usually a little delay but not much over 5 seconds. I am guessing you are on the right track with the DNS and not resolving correctly which if you are employ this then it can be the issue you have in question one. If you use the IP instead of a hostname does it work faster?
Ahh, linuxserver is running samba, so presumably WINS has something to do with its being resolved? On further investigation, I can't access it by hostname from webserver, whereas I can from my Windows machine with a samba network drive mounted. I'll have to sort samba out on webserver in that case, and then maybe come back to this one.
With that (hopefully) out of the way, does anyone have any ideas about the ssh login problem?