Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
'dig' queries the DNS system to find your host's IP address.
If your DNS isn't set up correctly, you might get some error messages.
Can you please post your 'dig' command as well as it's output? That may give
a clue as to what goes wrong.
If you don't have any internet connection and thus no connection to the DNS server of your ISP (internet provider), then you can always set up your own DNS server for your private network.
However, in most cases, you don't need to, unless your home network is really big.
Please give us more information about your network, like the number of computers attached, how they are connected (ie hardware or software routers, network connections), why you have set up the network (for example, the share files, to share a printer, etc). It would also be nice to know if you have any plans of connecting your network to the internet or not.
As for NCP, it is possible to make Linux use the IPX protocol, the protocol that is used by Novell netware
computers for networking. Unfortunately, I can't provide you with any details. Please search this forum or Google for the application of IPX under Linux.
now i have 10 computer with a different OS..and 100/1000 switch 16 port..they all ready connected each other...share file or printer look fine..
i'm build some web base application with PHP,MySQL and Apache as Web Server...each computer must open their browser to use my application..
do i need to set up dns..gimme a clue to solve this think...
PS: I'm using Fedora Core 4 as a server...my client using mandriva, win 98, win 2000 SP4, win 2003 Enterprise and win XP SP2
Your network isn't connected to the internet.
This means you can't have a publicly accessible server, like a webserver for the entire internet world,
or an FTP-server, etc.
As long as you don't need any such (publicly reachable) machine, I would not use DNS if I were you.
What does DNS do normally? Well, simply said, it translates hostnames (names of computers) to their IP addresses. DNS is used to look up the IP addresses of all the computers on the internet. Thus, if you want to have a machine that's publicly visible on the internet, you'll need to have a DNS server (either your own or the one of your ISP) that tells the internet computers which IP address they need to use to reach that computer.
For your home network, I don't think you need that yet.
What can you use instead? Well, you can either assign fixed IP addresses to all your computers or you can
use DHCP to automatically assign IP addresses, or a combination of both.
After that, you'll need to set up a router. This router will tell all your computers how they can reach the others. Such a router, used to interconnect a small network, is commonly called a "gateway". Think of a gateway as a computer that holds your network together, as the computer that is the only point of contact for all your network computers in case they want to reach each other.
In the simplest case, just assign host names and static IP addresses, specifying the IP address of your server (the FC4 machine) as the IP address of the "gateway" (both Linux and Windows machines need an IP address, a subnet mask and the IP address of the gateway to be able to interact in a network). Forget DNS for now.
On the FC4 machine, however, you'll need to set up a routing service. I think you need to use "iptables" for that. It can act both as a router and a firewall, if I'm not mistaken. This router probably only needs to have a list of all IP addresses and their corresponding hostnames.
If you don't want static IP addresses, but rather dynamically assigned ones, you'll need to configure your FC4 box as DHCP server (this is easy and can be handy to share certain system files, like /etc/passwd) and all the others as DHCP clients (no fixed IP addresses in this case).
If you were wondering what IP addresses and subnet mask you could use:
since your network is isolated from the internet, it doesn't really matter. But, just to make sure you don't need to reconfigure too much if you ever decide to connect it to the internet, I'd recommend using IP addresses in the range 192.168.*.* Such addresses are "private addresses", that are never reachable by the outside internet. When you connect to the internet, this configuration will come in handy (if you'll only have 1 internet connection for all your machines).
The only address you may never use to interconnect your machines is 127.0.0.1, because this address reserved
for the "localhost" network interface, which is nothing more than a network connection on each of your machines that connects the machine to itself.
For the subnet mask, again, it's up to you, but I'd recommend something like 255.255.255.0, which is very common.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.