FedoraThis forum is for the discussion of the Fedora Project.
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.
[root@localhost cuda]# /sbin/chkconfig --level35 nmb on
--level35: unknown option
[root@localhost cuda]# /sbin/chkconfig --level35 smb on
--level35: unknown option
[cuda@localhost ~]$ /sbin/chkconfig nmb on
failed to make symlink /etc/rc2.d/S91nmb: Permission denied
failed to make symlink /etc/rc3.d/S91nmb: Permission denied
failed to make symlink /etc/rc4.d/S91nmb: Permission denied
failed to make symlink /etc/rc5.d/S91nmb: File exists
[cuda@localhost ~]$ su
[root@localhost cuda]# /sbin/chkconfig nmb on
[root@localhost cuda]# /sbin/chkconfig smb on
I would l like to keep trying to fix this but if its to big of a pain in I can just go back to fedora 7 IM not in any hurry
ok this is wild if I use the command sudo /sbin/chkconfig --level 35 smb on
it asks for my password and it wont accept it is says thais incorrect
then if I log in to root and use the command sudo /sbin/chkconfig --level 35 smb on
One thing you also need to do is to run "smbpasswd -a <username>" to add the same username and password that exists in windows. There needs to be a one-to-one mapping between the windows user and the samba user.
Also, check your logs for selinux. You may want to check what it's configuration says for samba.
[root@localhost cuda]# /sbin/chkconfig --list smb
smb 0: off 1: off 2: on 3: on 4: on 5: on 6: off
and I added a new user it had no effect
I got windows to tell me that "you were not connected because a duplicate name exists"
I changed the name of my win box with no help but when I changed the name of my fedora box it made it so that I can access my shared files from windows on my fedora box
so I ca live with it this way however I like it when I can access my win box from fedora I will check windows again and see if its something there will update if I find something
Last edited by cuda; 12-16-2007 at 09:06 PM.
Reason: update it
I was having the same problem with the latest version of Solaris 10. The fix for me was to put the netbios name and IP address of the workgroup master browser into the /etc/hosts file of the Solaris machine.
I have several PCs, running various versions of Linux, Solaris and Windows, on my home network. I'm connected to the Internet through a DSL router that does NAT and acts as a DHCP server. It gives it's own address to it's clients as a DNS server. Then, forwards lookup requests to my ISP's DNS servers. Unfortunately, it doesn't resolve the names of the machines on my local network. It passes queries to my ISP even if one of my computers is looking for the address of another. Of course, my ISP knows knows nothing of my internal network and the lookup fails.
What appears to be happening with this version of Samba is that it's using DNS to get the IP address of the workgroup master browser after finding the name. If that fails, you get the error message.
All my PCs showed up in the Nautilus browser after I put the master browser's address into the /etc/hosts file. Since it's possible for any of the Windows PCs to be the master browser I reserved all their addresses and put them all in the /etc/hosts file.
linux machines are not connecting to local running websites
I have 10 linux machines and 40 windows machines in my office. I have install a new share-point server in my office. problem is this that my share-point sites is not opening in linux machines, like as I open that in windows machine by http://share-point:8080/projects ,its working fine but when I open it with my linux firefox browser then it directly goes to my squid server which unable to resolve the address for this local running share-point site, and by auto detect proxy that is also not working .
any help please............