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 have 2 windows boxes Box A (Prof) and box B (Home)
then 1 linux box Box B (redhat).
Now when one of my windows computers goes down or has a major problem it is verry eazy to just format it and start over but the only problem with this is when i do this some times they wont see the linux box or any other computer for that matter in the work group all i get is the List of servers for this work group is currently unavailable i have fixed it before but i can not remember exactly what the problem was has any one had a problem like this useing redhat btw its 7.2
the fact that the rebuilt machines dont see other windoze machines either, strong indicates a windows issue rather than an issue with samba on your redhat server....
Distribution: Linux Redhat 9.0, Fedora Core 2,Debian 3.0, Win 2K, Win95, Win98, WinXp Pro
Posts: 344
Rep:
You may experience this type of reaction any time there is a requirement to "revote" for the PDC. Each time a new PC shows up on the network, Samba forces a revote of all the available PC's in order to establish the domain controller (which is usually Samba, but it doesn't know otherwise). There is a MS KB item on this because the windows machines may take up to 11 hours to do this. I apologize for not having it right at the tip of my fingers right now, but it is out there. It isn't a Samba issue: it's windows. Many times when I have to do this, I do it just before I go home for the evening and by the next morning everything is kosher. You actually don't have to do it very often, just when a new PC shows up on the network. If you turn off an existing one, and then turn it back on; it is already established on the network (through the netbios names) and it is accepted. At least this has been my experience.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.