[NTLUG:Discuss] (no subject)

Thu Jul 25 04:14:45 CDT 2002

At 7/24/02 10:22:00 PM, you wrote:
>Hi all,
>
>Ok, now that the dual boot nightmare is over,

How did you finally resolve that issue?

> I have a question about 
>setting up a Samba server.  I have already installed Samba, I can start it 
>using /etc/rc.d/init.d/smb start ("service smb start" doesn't seem to work, 
>not sure why)and I can sign on with a samba client on my own 
>workstation.  However, when I go to my Win98 box and check the Network 
>Neighborhood, I can see both the Win98 computer and one called Localhost 
>(the Linux box...I haven't changed the domain name on it), so it looks like 
>the Win98 box is seeing it, right? 

You can see the machine, but did you set up the shared folder in the users directory?

> Except when I attempt to map a network 
>drive to it or double click on the Localhost icon, it tells me the computer 
>or sharename could not be found.  So...it sees it, but it doesn't see it.
>

Again, you see the machine, but is there a shared folder.

>Now, I have made sure the inetd.conf file has netbios set up for port 139 
>for tcp and port 137 for udp.  I have also set up the workgroup in the 
>smb.conf file and set up the allowed hosts from the dhcp list on my 
>router.  What am I doing wrong?  I know I have to be missing something, but 
>it eludes me.

Using netbios can be very risky. It is possible to setup the local network to using TCP/IP without having netbios involved at all, which is much more 
secure. If you access the intenet, I would suggest strongly that you look into and impliment another protocol with less security issues than netbios. I 
have netbios COMPLETELY disabled on all of my machines.

>
>Also, I'd like to have the Samba server start on startup.  What would I add 
>to make it do so?  Would that be an entry in the initrd.conf file?
>

If you are using RedHat, I believe there are sections in LinuxConfig, Sysv, and webadmin where you can decide which services start during the 
bootup process. There are other GUIs available to configure startup services, that other people may be able to offer more info about, and then there 
is the edit the scripts by hand with your favorite text editor method. 

One more thing, before you worry about starting the service at bootup, you really should make sure that the service is working correctly before 
configuring it to start on bootup. This is true with any service or program. In the "old days" 7 or 8 years ago, when X Windows was still a configure, then 
compile and then execute proposition, it was very unwise to have X Windows started on bootup until you were ABSOLUTELY SURE, that it actually 
worked. I learned that lesson from hours of troubleshooting (aka hairpulling aggrivation) after having made that same mistake myself. 

When I think back to things like that it just reminds me of how far Linux has come in the last several years, thanks to many programmers, beta testers, 
and users, who have been there to offer assistance to the rest of us.

 One final thought, To the Linux community, a most well deserved , Thank You !!! 

>Thanks,
>Wayne
>
>
>
>_______________________________________________
>http://www.ntlug.org/mailman/listinfo/discuss
>.
>