Re: [Samba] virtual server configuration issues
Jerry, You are the king! This WAS the issue (that I have been struggling with for over a year and always giving up on). Now when I do a 'smbclient -L ' the %L gets the correct value always: So, I suppose that all the examples and documentation I've found on the net are not entirely correct in that they also need to specify 'smb port = 139' for it to work correctly with Win2K and later: * http://us1.samba.org/samba/docs/using_samba/ch06.html * http://nic.phys.ethz.ch/readme/69#Distribution%20of%20the%20virtual%20Samba%20servers This is one of those obscure things that if you don't understand all the inner workings of samba and its configuration options (and Win2K and beyond) I don't see how you would get it working. Is there any reason why 'smb ports = 139' should be the default? After all, samba is primarilly for interaction between unix and windows from what I understand. Thank you so much for your response! Tim --- "Gerald (Jerry) Carter" <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Tim Harvey wrote: > > I assume you mean 'smb port = 139'? I believe this is > > the default, however this made no difference. > > No. I mean 'smb ports = 139' The default is to bind to > ports 139 adn 445. Windows 2000 and later will use port 445 > which bypasses any netbios operations (such as the session > request that contains the netbios called name which we use > for %L). > > > > > > cheers, jerry > = > Alleviating the pain of Windows(tm) --- http://www.samba.org > GnuPG Key- http://www.plainjoe.org/gpg_public.asc > "I never saved anything for the swim back." Ethan Hawk in Gattaca > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.0 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFCwUQLIR7qMdg1EfYRAlaTAKCsiTYic9ljnkIJqhL3jkjrOoVazwCdG6dB > tg5UDeQpg8zrnS5vcsFbt/8= > =HMSt > -END PGP SIGNATURE- > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] virtual server configuration issues
I assume you mean 'smb port = 139'? I believe this is the default, however this made no difference. Tim --- "Gerald (Jerry) Carter" <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Tim Harvey wrote: > > > > > The problem I've been having is that the virtual servers seem to get their > > names/shares mixed up. Here are my configuration details: > > > > Server OS: Linux Fedora Core 3 > > Samba: samba-3.0.10-1.fc3 > > Network Environment: Workgroup: 'MSHOME' > > Other Systems on network: Linux (samba), WinXP > > set "smb ports = 139" in [global] of smb.conf > > > > > cheers, jerry > = > Alleviating the pain of Windows(tm) --- http://www.samba.org > GnuPG Key- http://www.plainjoe.org/gpg_public.asc > "I never saved anything for the swim back." Ethan Hawk in Gattaca > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.0 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFCwBcLIR7qMdg1EfYRAjO/AJ9xlC6pfdTD5PkHMUghSiALZvbD0gCg0xHS > 5ToHMwut2//nalWcBELxvaY= > =qZ3G > -END PGP SIGNATURE- > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] virtual server configuration issues
Greetings, I've used samba for many years now on various platforms and its worked very well. I'm now trying to use 'virtual servers' to combine several smb servers on one machine and have been following the clear and simple instructions here: http://www.oreilly.com/catalog/samba/chapter/book/ch04_07.html (I've also cross-referenced these instructions with various posts to this list and it seems like I'm configuring things correctly with the combination of the 'netbios aliases' and 'include' statements). The problem I've been having is that the virtual servers seem to get their names/shares mixed up. Here are my configuration details: Server OS: Linux Fedora Core 3 Samba: samba-3.0.10-1.fc3 Network Environment: Workgroup: 'MSHOME' Other Systems on network: Linux (samba), WinXP /etc/samba/smb.conf: [global] workgroup = MSHOME server string = Samba %v on %h as %L netbios name = server netbios aliases = video music log file = /var/log/samba/%m.log max log size = 50 security = share socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 disable spoolss = yes include = /etc/samba/smb.conf.%L /etc/samba/smb.conf.server: [homes] comment = Home Directories browseable = no writable = yes [data] comment = RAID Array path = /data force user = nobody force group = nobody read only = No guest ok = Yes /etc/samba/smb.conf.music: [Music] comment = Video Files browseable = yes path = /data/Video force user = nobody force group = nobody read only = No guest ok = Yes /etc/samba/smb.conf.video: [Video] comment = Video Files browseable = yes path = /data/Video force user = nobody force group = nobody read only = No guest ok = Yes With this configuration and the smb/nmb services running I do the following commands on my linux server (the one running samba): [EMAIL PROTECTED] samba]# smbclient -L music Password: Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.10-1.fc3] Sharename Type Comment - --- dataDisk RAID Array IPC$IPC IPC Service (Samba 3.0.10-1.fc3 on server as server) ADMIN$ IPC IPC Service (Samba 3.0.10-1.fc3 on server as server) Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.10-1.fc3] Server Comment ---- MUSICSamba 3.0.10-1.fc3 on server as server SERVER Samba 3.0.10-1.fc3 on server as server VIDEOSamba 3.0.10-1.fc3 on server as server WorkgroupMaster ---- MSHOME [EMAIL PROTECTED] samba]# smbclient -L video Password: Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.10-1.fc3] Sharename Type Comment - --- dataDisk RAID Array IPC$IPC IPC Service (Samba 3.0.10-1.fc3 on server as server) ADMIN$ IPC IPC Service (Samba 3.0.10-1.fc3 on server as server) Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.10-1.fc3] Server Comment ---- MUSICSamba 3.0.10-1.fc3 on server as server SERVER Samba 3.0.10-1.fc3 on server as server VIDEOSamba 3.0.10-1.fc3 on server as server WorkgroupMaster ---- MSHOME [EMAIL PROTECTED] samba]# smbclient -L server Password: Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.10-1.fc3] Sharename Type Comment - --- dataDisk RAID Array IPC$IPC IPC Service (Samba 3.0.10-1.fc3 on server as server) ADMIN$ IPC IPC Service (Samba 3.0.10-1.fc3 on server as server) Domain=[MSHOME] OS=[Unix] Server=[Samba 3.0.10-1.fc3] Server Comment ---- MUSICSamba 3.0.10-1.fc3 on server as server SERVER Samba 3.0.10-1.fc3 on server as server VIDEOSamba 3.0.10-1.fc3 on server as server WorkgroupMaster ---- MSHOME As you can see no matter what server I specify with 'smbclient -L' samba appears to act as if the request was for the netbios name 'server' (notice I configured 'server string = Samba %v on %h as %L' to test this out and I see 'server as server' for each test. On the winxp system I get random results: C:\>net view video Shared resources at video Samba 3.0.10-1.fc3 on server as video Share name Type Used as Comment --- Video Disk Video files The command com
[Samba] Trouble with virtual server configuration
Greetings, I've been trying to use Samba in a virtual server configuration on one of my linux boxes and am running into trouble. My intention is to get a single samba server to act as 3 seperate servers (netbios names 'Audio', 'Video', 'Pictures') so that later they can be migrated to different machines with little effort. In reading the docs, lists, and available books I've come to configure it in the following way: linux server /etc/samba/smb.conf: #Global parameters [global] workgroup = mshome netbios aliases = audio video pictures security = share server string = Samba Server log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 encrypt passwords = yes # disable printer and faxes disable spoolss = yes # include shares from actual NETBIOS name include = /etc/samba/%L.conf /etc/samba/video.conf: [Video] comment = Video browseable = yes path = /data/Video force user = nobody force group = nobody read only = No guest ok = Yes /etc/conf/audio.conf [Audio] comment = Audio browseable = yes path = /data/Audio force user = nobody force group = nobody read only = No guest ok = Yes /etc/conf/pictures.conf [Pictures] comment = Pictures browseable = yes path = /data/Pictures force user = nobody force group = nobody read only = No guest ok = Yes The trouble I'm having is that eventually each virtual server shows the shares from all the others. When I first startup samba on the server and connect to the servers 'audio', 'video', 'pictures' from a WinXP system all is well (each server only shows its single share). Then after a short period of time (minutes?) each of those servers shows all three shares (Audio, Video, Pictures). Any ideas what is going on or how I can fix this? Thanks, Tim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Performance of samba in linux vs windows
> -Original Message- > From: Holger Krull [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 30, 2004 11:56 PM > To: Tim Harvey > Cc: [EMAIL PROTECTED] > Subject: Re: [Samba] Performance of samba in linux vs windows > > > > For windows I'm low-tech: stopwatch plus drag-n-drop of a large file > (any > > recommendations on a 'simple' windows program that will tell you how > long it > > took to copy a file, or even calc the BW for you?) > > timethis from the windows resource kit Perfect... exactly what I was looking for. Thanks! > > > > - why would I be getting half the performance via nfs vs smb? Is > there a > > lot more overhead with smb vs nfs? > > Give your smb.conf for comparison I didn't include it because it didn't change across my comparisons, but here it is: --/etc/samba/smb.conf-- #Global parameters [global] workgroup = MSHOME netbios name = NAS3 security = SHARE server string = Samba Server log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 encrypt passwords = yes [data] comment = RAID5 Share browseable = yes path = /data force user = nobody force group = nobody read only = No guest ok = Yes -- I haven't tried playing with the socket_options. Tweaking those would perhaps change my performance of the smb tests, however it still wouldn't explain why smb over linux is much slower than smb over windows. Tim -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Performance of samba in linux vs windows
I'm doing some performance tests on a samba NAS server and I've found some interesting statistics: I'm doing my performance tests in linux using: # time dd if=somelargefileovershare of=/dev/null bs=1M count=100 Then calculating the bandwidth For windows I'm low-tech: stopwatch plus drag-n-drop of a large file (any recommendations on a 'simple' windows program that will tell you how long it took to copy a file, or even calc the BW for you?) Here are my bandwidth results: nfs via linux: 10MB/s smb via linux: 5MB/s smb via win: 8MB/s Questions: - why would I be getting half the performance via nfs vs smb? Is there a lot more overhead with smb vs nfs? - why the large difference between using smb from a linux box vs smb from windows? The windows transfers are much faster... almost 2X I'm just trying to understand my results better. The samba server I'm mounting to is running on a 1.2GHz Celeron, 256MB SDRAM, using a raid5 array with an XFS filesystem on ATA drives with a 100mbps nic. The bottleneck here is the 100mbps nic, which theoretically will give me a max throughput from the server of 12.5MB/sec, so I'm fairly satisfied to see 10MB/sec from the nfs test. Thanks for any assistance in understanding these results, Tim -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] name resolution between windows and samba
I've got a simple anonymous read/write samba server with the following configuration: # Global parameters [global] workgroup = MSHOME netbios name = FILESERVER security = SHARE server string = NAS Server log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 [data] comment = RAID5 Share path = /data force user = nobody force group = nobody read only = No guest ok = Yes On the same network I have a WinXP system (named 'WINXP') and a Win98 system (named 'WIN98') all connected through a Linksys firewall/gateway using DHCP from the Linksys. Everything seems to work fine via windows 'network neighborhood', however I'm having some difficulties understanding what I need for proper name resolution outside of network neighborhood. For example, I wish to be able to drop to a dos box on a windows machine and do a 'telnet fileserver', however 'fileserver' is not resolved. I realize I can edit the hosts file on each windows system but if fileserver has DHCP address this doesn't work. Additionally I wish to be able to 'ping winxp' from the fileserver, but there is no name resolution. Basically, what I do not understand is how to implement netbios to tcp/ip name mapping. Can anyone give me some suggestions or point me to the relevant docs. I've read through a lot of the samba docs, but I do still not understand this aspect. Thanks, Tim -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] RE: Trouble setting up an Anonymous read/write samba server for WinXP Pro users
Just thought I would follow-up on this as I finally found a solution. Using the exact same configuration, I simply upgraded to samba 3.0.7 and the problem went away! Tim > -Original Message- > From: Tim Harvey [mailto:[EMAIL PROTECTED] > Sent: Friday, September 24, 2004 12:47 PM > To: '[EMAIL PROTECTED]' > Subject: Trouble setting up an Anonymous read/write samba server for WinXP > Pro users > > Greetings, > > I'm having difficulty setting up an 'Anonymous Read-Write' SAMBA server on > a new system with a stock FC2 installation for use with WinXP Pro systems. > > I'm using the following software on the 'fileserver': > - Linux FC2 installed from the FC2 iso's: kernel 2.6.5-1.358 > - samba-common-3.0.3-5 > - samba-3.0.3-5 > - samba-client-3.0.3-5 > - samba-swat-3.0.3-5 > - system-config-samba-1.2.9-2 > > Following the instructions and examples in the official SAMBA howto, I'm > under the impression that I want a smb.conf file such as: > > # Global parameters > [global] > workgroup = MSHOME > netbios name = FILESERVER > security = SHARE > > [data] > comment = Data > path = /export > force user = nobody > force group = nobody > read only = No > guest ok = Yes > > The problem I'm running into is that when I attempt to connect to the > share from a WinXP Pro system by simply using the address \\fileserver in > an explorer window, I immediately get a 'Connect to fileserver' window > from WinXP with a greyed out username set to 'fileserver\Guest' and asking > for a password. I'm confused - the whole point of setting up an anonymous > read/write server was to avoid having to put user accounts on the samba > server. > > I've found that if I open up the address \\fileserver\data I can connect > with no user/pass request. I've also found that if I'm logged into the > WinXP system as user 'Tim' and I create a user 'tim' on the samba server, > I am not prompted for a user/pass. Both of these solutions are > unacceptable for what I'm trying to accomplish. All the howto's and > examples I've found regarding anonymous samba servers mention nothing > about this problem. > > Any explanation / advice would be greatly appreciated > > Thanks, > > Tim -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Trouble setting up an Anonymous read/write samba server for WinXP Pro users
Greetings, I'm having difficulty setting up an 'Anonymous Read-Write' SAMBA server on a new system with a stock FC2 installation for use with WinXP Pro systems. I'm using the following software on the 'fileserver': - Linux FC2 installed from the FC2 iso's: kernel 2.6.5-1.358 - samba-common-3.0.3-5 - samba-3.0.3-5 - samba-client-3.0.3-5 - samba-swat-3.0.3-5 - system-config-samba-1.2.9-2 Following the instructions and examples in the official SAMBA howto, I'm under the impression that I want a smb.conf file such as: # Global parameters [global] workgroup = MSHOME netbios name = FILESERVER security = SHARE [data] comment = Data path = /export force user = nobody force group = nobody read only = No guest ok = Yes The problem I'm running into is that when I attempt to connect to the share from a WinXP Pro system by simply using the address \\fileserver in an explorer window, I immediately get a 'Connect to fileserver' window from WinXP with a greyed out username set to 'fileserver\Guest' and asking for a password. I'm confused - the whole point of setting up an anonymous read/write server was to avoid having to put user accounts on the samba server. I've found that if I open up the address \\fileserver\data I can connect with no user/pass request. I've also found that if I'm logged into the WinXP system as user 'Tim' and I create a user 'tim' on the samba server, I am not prompted for a user/pass. Both of these solutions are unacceptable for what I'm trying to accomplish. All the howto's and examples I've found regarding anonymous samba servers mention nothing about this problem. Any explanation / advice would be greatly appreciated Thanks, Tim -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
