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.
I want to configure dual network cards in Redhat 9.0. Actually the problem is that, I have Samba Server and 120 (round about) clients of windows 2000 professional. Sometimes the server does't answer the queries due to the outgoing traffic from server. I want to configure two network cards so that the server can communicate with both. Plz Help me in this regard.
Sounds like a network issue that might be better resolved elsewhere.
When I begin to think of this issue, I immedietly begin to think that with two interfaces, you get get two IP's. Duh right... But then your clients will have to contend with two domain names resolving to either one of them. Sounds like you'd be creating more work for yourself trying to solve the problem in the manner you have suggested.
I could be wrong though... Just trying to brain-storm a little...
I have installed second nic. I have assigned Ip 10.10.10.101 to the eth0 and 10.10.10.102 to the eth1. But the problem is Server receives the request from both. When i configure any client (windows 2000) then the message display after booting *Duplicate Name*. I want that server will receive the requests from eth0 and sends the data from eth1. Is it possible. What will i have to do?
If your load on your server is really that intense, I would think it is time to think about a second server to work next to it. Do a lot of your client PCs really use the server hard (as far as network file usage goes). Are there any other net services running on the server.
If a client pc wants a file from a specific host name it will search for the associated IP address. A single host name cannot be applied to 2 IPs. The only way for the 2nd nic to work is if you start sharing your files based on the ip address (ex. \\10.10.10.101\myfolder and \\10.10.10.102\myfolder instead of \\overworkedserver\sharedfiles). You would then have to divie up the different desination IPs among the different host. I'm sure you could see this is not good practice. It will eventually get confusing try to figure out which computer calls which ip.
edit: I reread your post and saw I didn't answer the question correctly. It doesn't seem like what you want is possible. Think about this: computerA asks 10.10.10.101 for a file and then 10.10.10.102 tell computerA it has a file it asked for. Well, computerA wants the replies, and ultimately the file, to come from 10.10.10.101. Not 10.10.10.102. Think about how tcp/ip works. I may be totally off on that, but that's how I see it in my head.
Last edited by benjithegreat98; 01-13-2004 at 08:52 PM.
Thanx for reply. I have understood what u want to tell me. Now Plz tell me about 2nd server. What will have to do for this. Tell me the topic and source ( if possible ).
I have never done this, but what about subnetting your 200 node network in half and dedicating a server to each subnet? This would (theoretically) disperse the server load considerably and make administration slightly easier over the long haul.
On the 2nd server, I meant get a physical 2nd server. If you have that many computers I'll assume it is for a business. I'll also assume that the business has internal departments (ie. administration, maintenance, human resources). I would distribute the files between the 2 servers. For example server 1 would hold the files for administration, human resources, etc. and server 2 would hold the files for maintenance, whoeverelse, etc. Or you could distribute it where people's personal documents are on one and departmental files are on the other. Whichever make more sense to you.
I say get another one because there is obviously a big load on the server. Adding a 2nd nic and having different people connect to different IPs will not cut the load in half. I'm sure it will help some, but it sounds like you are delaying the inevitable.
If money has to be approved first, you could do the dual nic idea and anticpate buying a 2nd server in the near future.
I think the solution is making linux as BDC (Backup Domain Controller). But i don't know wether Samba works as BDC or not. I have configured Samba as PDC (Primary Domain Controller). I found some documentation on net using Samba as BDC but not complete. He made Windows Server as PDC and Linux system as BDC
I work in university campus. Plz Tell me in this regard.
Thanx in anticipation
Last edited by linuxeagle; 01-15-2004 at 12:40 AM.
If you think your server is capable of serving the whole domain/group, and you only want to have a bigger bandwidth but using the same or one server then you can do it by:
creating different segment on your linux server
OR
bonding network cards
I would suggest for you to bond 3 NIC (or 4), in that way you can have 200MBps x 3 bandwidth (full duplex) on 1 server that would give you 600MBps. if you have a gigabit port then you might as well use it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.