[Samba] Another Shot At It
After receiving no response to yesterday's message, I tried some more web scouring and more tinkering and dinking around with Samba...and I discovered what may be a major key to my problem... I have 3 PC's...2 are Windoze and 1 is Linux. Windoze machines are likely to understand how to share files across subnets using the same workgroup name...but is Samba as adept? I have a feeling that is at the heart of my problem. I enabled wins support in my smb.conf and assigned the Samba box's IP address as the primary wins server on the WFW box. I also set Samba to be the domain master browser according to the instructions in BROWSING.txt. All of this, alas, was useless as I still couldn't browse the Win-duhs shares from Linux or the Linux shares from Winduhs. I feel that I'm getting much closer to my goal (file sharing without using Windows) and would really appreciate any help any of you can offer. Thanks in advance for any help you can provide. DJ Busch Here is my latest attempt at smb.conf: [global] workgroup = LEGEND netbios name = LUKE server string = Dave's Linux Experiment Gone Wrong interfaces = eth0 bind interfaces only = Yes security = SHARE encrypt passwords = Yes null passwords = Yes log file = /var/log/samba/log.%m debug level = 5 max log size = 50 ; socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 os level = 2 lm announce = yes preferred master = yes domain master = yes dns proxy = No wins support = yes guest account = doodles hosts allow = ALL hosts deny = [homes] comment = Home Directories path = /home read only = No guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [hp] path = /var/spool/samba read only = No guest ok = Yes printable = Yes printer name = hp -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Still can't make it work (LONG)
Well gang, I'm back and still haven't figured out why Samba isn't working with my Windoze PC's. I though I was close a couple times, but now I'm back to square 1. So now I'm going to spill as much information on you guys as I can in the hope that someone will notice what I'm doing wrong and help me get this thing running. Here are the computers on my home network: A. Linux Box (luke) - AMD Athlon 750 MHz, 256 MB RAM, (2) 20 GB IDE HD's RedHat 7.3 (kernel 2.4.18-3) Samba v2.2.6pre2-1 3Com 3C509 PCI TPO Ethernet Adapter IP set by DHCP from ISP (Time Warner/RoadRunner) This machine also boots Windows 2000 Professional and can browse other Windows shares when using Windows 2000. smb.conf file for this machine is attached. I've scaled it down to make it easier/faster to read. This box has both ipchains and iptables installed. I'm not sure if these can cause the problems I'm having or not. B. Windoze Box #1 (jarjar) - Toshiba Satellite Laptop, Pentium III 750 MHz Windows 98 SE Netlink PCMCIA Ethernet Card IP set by DHCP from ISP C. Windoze Box #2 (obi-wan) - 486 DX2 66Mhz, 8 MB RAM, 400 MB HD WFW 3.11 MS TCP/IP32 3Com 3C509 ISA Ethernet Card I tried running through the DIAGNOSIS.txt file with the following results: Test 1: testparm shows all clear Test 2: (from obi-wan) ping luke: Success (had to manually supply IP address) (from luke) ping obi-wan: Success (had to manually supply IP address) Test 3: smbclient -L luke: Success (asks for password but accepts blank) Test 4: nmblookup -B LUKE __SAMBA__: Success Test 5: nmblookup -B JARJAR '*' : Failed (name_query failed to find name *) nmblookup -B OBI-WAN '*': Failed (name_query failed to find name *) Tried this one with ipchains/iptables and without - same result both times Test 6: nmblookup -d 2 '*' : Returns only the IP of the Linux box. Test 7: smbclient //luke/homes : Success Test 8: (from obi-wan) net view \\luke: Failed (couldn't find computer name on network) I've tried to telnet from one machine to the other on port 139, and each attempt fails. However, when I try to telnet into a machine from itself, it worksfrom each machine. This has led me to believe that there is a problem in the network at the hub level...but what could that be? Both Windoze machines are able to share and browse at will. If the Win machines can't connect to each other on port 139, how are they sharing? I hope someone on the list can help. This has been a problem long enough now. Thanks in advance, DJ Busch -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Doh!
I forgot to attach the smb.confso here ya's go. Thanks. DJ Busch # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Date: 2002/10/16 21:47:46 # Global parameters [global] workgroup = LEGEND netbios name = LUKE server string = Dave's Linux Experiment Gone Wrong interfaces = eth0 bind interfaces only = Yes security = SHARE encrypt passwords = Yes null passwords = Yes log file = /var/log/samba/log.%m max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 os level = 33 lm announce = True preferred master = True domain master = True dns proxy = No guest account = default hosts allow = ALL [homes] comment = Home Directories path = /home read only = No guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [hp] path = /var/spool/samba read only = No guest ok = Yes printable = Yes printer name = hp oplocks = No
RE: [Samba] Samba with a Win9x network and RoadRunner
I've tried setting the IP on the Linux machine manually, but the result was ugly - I couldn't connect to any outside Internet services. If I don't let RR(my cable ISP)'s DHCP server set my IP, I can't access the Internet at all. -Original Message- From: Mogens Kjaer [mailto:[EMAIL PROTECTED]] Sent: Sunday, September 29, 2002 1:32 AM To: DJ Busch Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Samba with a Win9x network and RoadRunner DJ Busch wrote: ... Now on to the problem: As most of you are already aware, RR uses DHCP to assign IP addresses to client machines at boot time. This seems to be causing Samba to have problems resolving the machine names. I don't know what RoadRunner is, but at home we have an ADSL router that acts as a DHCP server. But this doesn't prevent me from assigning IP numbers within the server's IP interval. The DHCP server will try and ping the IP number before giving it to a client. If the number is already taken, a new one is assigned. Mogens -- Mogens Kjaer, Carlsberg Laboratory, Dept. of Chemistry Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: [EMAIL PROTECTED] Homepage: http://www.crc.dk -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba with a Win9x network and RoadRunner
I've considered doing just that, but here's the rub...in the very rare occasion when I _do_ want/need to use W2k for something, my wife's laptop can't get to the internet. I've considered setting up ICS on the Win2k side to accomodate that, but wasn't sure how to set up ICS and was hoping to resolve the problem without going to that extreme. -Original Message- From: Gene Bomgardner [mailto:[EMAIL PROTECTED]] Sent: Sunday, September 29, 2002 8:57 AM To: DJ Busch Subject: RE: [Samba] Samba with a Win9x network and RoadRunner On 29 Sep 2002 at 8:42, DJ Busch wrote: I've tried setting the IP on the Linux machine manually, but the result was ugly - I couldn't connect to any outside Internet services. If I don't let RR(my cable ISP)'s DHCP server set my IP, I can't access the Internet at all. I've run into similar problems. MSN supplies a router that does dchp as well. Just to make life interesting, it uses an ip mask of 255.255.255.252 which allows exactly _4_ addresses. *.0 is of course unusable, *.1 is the router, *.2 is a client machine, and *.3 is a broadcast address. That means you can hook up exactly ONE pc to the darn thing. So what I did was use a unix machine as a gateway. It has two nics, one to the router addressed 192.168.129.2/30 and another for my LAN adressed as 192.168.123.8/24. The gateway runs natd and its own dhcp server (the dhcp is not really necessary) I can now assign whatever ips I want on the LAN and I still reach the Internet just fine. Hope that help a little. God's Blessings, Gene To everything there is a season, and a time to every purpose under heaven.Ecl 3:1 - and more recently, The Byrds -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba with a Win9x network and RoadRunner
Is the DHCP server running on one of your machines? My machines are assigned an IP by my ISP. BTW, ICS = Internet Connection Sharing (W98 has it, not sure about W2k) -Original Message- From: Gene Bomgardner [mailto:[EMAIL PROTECTED]] Sent: Sunday, September 29, 2002 9:35 AM To: DJ Busch Subject: RE: [Samba] Samba with a Win9x network and RoadRunner I'm not too sure just what the W2000 problem might be, but we routinely connect 4 or 5 laptops running Win98, WinXP, and unix with no problems. (they all make use of the DHCP server). O yeah... what's ICS, I'm not familiar with that. God's Blessings, Gene To everything there is a season, and a time to every purpose under heaven.Ecl 3:1 - and more recently, The Byrds -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] A new twist
Well, after a little fiddling around, I enabled wins support in my smb.conf. After that, I was able to SEE my Linux box in W98, but not browse it. In addition, after rebooting the W98 machine, I couldn't even see it. Wierd, huh? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba with a Win9x network and RoadRunner
Hi everyone...I'm at a dead stop setting up Samba, so let me jump right into the problem: First, the setup: I have a RH7.3 box and a W98 laptop. The RH box also has a W2k Pro partition. We have them on a 4-port 10base-T hub along with our RoadRunner cable modem. Now on to the problem: As most of you are already aware, RR uses DHCP to assign IP addresses to client machines at boot time. This seems to be causing Samba to have problems resolving the machine names. When I get both machines up and running and try to connect to the laptop (jarjar) with smbclient -L jarjar, I get Connection to jarjar failed. My first question is this: Is there something I have to enable in W98 to allow Samba to make connections? And my second question: Can Samba decide which hostname goes to which computer on my home network without being able to resolve it to an IP address? I would assume that when the machines hold master browser elections, each is made aware of the other(s) and the IP addresses are not necessary. Any help anyone can provide is greatly appreciated. Every time I go to work I have to reboot into W2k so my wife can get at the files on my hard drives. It's annoying. Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
