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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Well, I'm having some problems with SAMBA that are really pissing me off. Let me explain:
At first, we had a RH 9 server running. It always crashed and it was far away from update and since RH isn't releasing any more free updates, we've chosen to change it to Debian. I choose it because I'm pretty more used to it.
When we were zeroing the server, we setup it to run at 192.168.3.5 until we bring up all the services (SAMBA, NAMED, DHCP, NIS and NFS). We had a lot of problems during the process and a implementation that usually would take nothing more than 2 days is taking a week, just because SAMBA isn't tunned up.
Well, that especific problem is that when we changed the IP address to 192.168.3.2, the clients can't login at first, but when they try again, with the same user and password, all became and things work out. The error seems to be something related to users or passwords, because it pops up a message talking about it (I'm not at work right now, so I can't paste it).
The guy that works with me say it's something related to WINS, but my guess is that is something related to passwords and all that plain-encrypted-ntlm-ntlm2-and-blah-blah-blah stuff. I guess that because since the client finds out the server and receive an answer like that, it seems that there are connection after all.
I was looking for the answer in Google and all the search engines that I never heard of and I stiff have no answer. So... if anybody could help not losing my job, I would be happy.
Are you having your users authenticating via Samba for workstation logins, or simply to access Windows shares / printers? Moving the IP address shouldn't make a difference so long as the relevant services (smbd, winbind, etc.) are restart accordingly. How are your clients becoming aware of the IP address change?
I've managed to correct the problem deleting the content of the /var/lib/samba directory and restarting the service. The problem was that the wins.dat (The file that is responsible for NetBIOS name resolving) was pointing to an unknown host with the old IP address. So when it tries to log in, the request is sent to the old address. When the user tries again, the request is sent to the right address.