[Samba] Samba 4 RPMs for RHEL 6
My apologies if this is something of a FAQ, but I would be grateful of some assistance. I am evaluating Samba 4 and would like to be able to create packages for installation on RHEL and CentOS 6.x servers. I've cloned the git repository and checked out tag 4.0.9, then used the "./packaging/RHEL-CTDB/makerpms.sh" script to build the RPMs. The process succeeds but the packages, while labelled 4.0.9, are not Samba 4 packages. Closer inspection of the spec file indicates that this is only geared towards Samba 3 builds. Have I missed something in the process of creating these packages? Is there a better way for me to proceed? For the moment, I'm just using make && make install on the servers but would like to move away from this mode. Regards, Malcolm. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Startup issue with Samba
DP, Many thanks as this seems to have sorted the issue for me. Are there any side affects of not including the "bind interfaces only = true" option, Cheers, Malcolm. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Startup issue with Samba
Hi Folks, I am looking to try and find a solution to the following problem and hope someone can help. I have just installed Samba on an HP Proliant Microserver at home to share disk with my Windows 7 PC and Vista laptop. I have managed to get everything set up but I have an issue where on a reboot the Windows 7 PC looses the share. If I restart samba (using /etc/ini.d/samba restart) then everything works ok and the Share re-appears over the network. It looks like a startup issue where Samba is not binding to port 139 and 445 using the IP address of the server only the loopback. It is similar to the issue in this post: http://ubuntuforums.org/showthread.php?t=1576293 but the solution does not fit as I can't find an smbd.conf file in /etc/init. I have the following errors in the smbd log at startup: [2011/07/03 15:29:23.569090, 0] lib/util_sock.c:880(open_socket_in) bind failed on port 445 socket_addr = fe80::9a4b:e1ff:fe06:c899%eth0. Error = Cannot assign requested address [2011/07/03 15:29:23.569346, 0] smbd/server.c:500(smbd_open_one_socket) smbd_open_once_socket: open_socket_in: Cannot assign requested address [2011/07/03 15:29:23.569378, 0] lib/util_sock.c:880(open_socket_in) bind failed on port 139 socket_addr = fe80::9a4b:e1ff:fe06:c899%eth0. Error = Cannot assign requested address [2011/07/03 15:29:23.569427, 0] smbd/server.c:500(smbd_open_one_socket) smbd_open_once_socket: open_socket_in: Cannot assign requested address and have startup orders: root@debian:/var/log/samba# ls -l /etc/rcS.d/*net* lrwxrwxrwx 1 root root 20 Jul 2 09:58 /etc/rcS.d/S13networking -> ../init.d/networking root@debian:/var/log/samba# ls -l /etc/rc2.d/*samba* lrwxrwxrwx 1 root root 15 Jul 2 10:09 /etc/rc2.d/S01samba -> ../init.d/samba root@debian:/var/log/samba# I think I need to try and change samba to start up after the netork interfaces have started but am not totally sure. Any help would be gratefully received, Cheers, Malcolm. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba printing --- why bother
Printing from a Windoze box to a linux printer has alway been incredibly slow via Samba. After I purchased a new printer it was so slow that most Window clients gave up. The solution is to avoid Samba alltogether and set up the printer on Windows as an internet printer, i.e.: http://mylinux:631/printers/raw. Then printing is subjectively as fast remote as it is local (instead of maybe 200 - 300 times slower via Samba). My question: since I cannot be the only one to encounter such behaviour (google verifies that I am not alone), why don't the samba developers either fix this bug, or disable printing over samba and recommend the internet solution? Malcolm Agnew -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing from Windows over samba
I have the following problem printing from Windoze with the Brother DCP 7010. The printer is local on a Linux box running under SuSE 10.0. The printer is running under CUPS with the drivers downloaded from Brother. For Windows I have set up a raw device which is accessed over samba. When I print from windows, which I can from various situations --- i.e. Firefox, Excel, etc, printing is very slow (up to 2 minutes). But I cannot print at all from WinWord. A message box appears saying that the printer is not available, and suggests I should see whether the printer is switched on. Anybody there with a suggestion? Malcolm Malcolm Agnew eMail: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba 3 performance issues
On Monday 01 May 2006 13:25, you wrote:
> malcolm wrote:
> > What dows this mean in /var/log/samba/
> > (apart from everything to do with printing from Windoze to a Linux
> > printer taking such a long time)?
> >
> >
> > error packet at smbd/ipc.c(97) cmd=37 (SMBtrans) STATUS_BUFFER_OVERFLOW
>
> You don't give a lot of background so I'll just respond in
> the general case. The STATUS_BUFFER_OVERFLOW error is used
> to indicate to a client that the RPC reply PDU will be fragmented
> across multiple read requests.
When I "print" from Windows, I get 8 messages with STATUS_BUFFER_OVERFLOW, and
when I put the cursor over my printer icon, I see the balloon message "access
denyed, no connection possible". All of this takes up to 30 seconds.
If I ignore the the warning that the printer is not accessible, I get another
3 warnings of STATUS_BUFFER_OVERFLOW, but then after about a minute, the
output appears at the printer.
My smb.conf is as follows:
[global]
workgroup = MALCOLM.NET
kernel oplocks = no
os level = 2
time server = Yes
unix extensions = Yes
encrypt passwords = yes
map to guest = Bad User
printing = CUPS
printcap name = CUPS
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
wins support = No
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
# character set = ISO8859-15
log level = 3
log file = /var/log/samba/%m
interfaces = eth1 192.168.15.1/255.255.255.0
server string = Samba Server
add user script =
domain logons = no
local master = no
preferred master = auto
[printers]
comment = All Printers
path = /var/tmp
printable = yes
create mask = 0600
browseable = no
guest ok = no
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775
browseable = yes
guest ok = no
printable = no
>
>
>
>
>
> cheers, jerry
> =
> I live in a Reply-to-All world. ---
> Samba--- http://www.samba.org
> Centeris --- http://www.centeris.com
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba 3 performance issues
What dows this mean in /var/log/samba/ (apart from everything to do with printing from Windoze to a Linux printer taking such a long time)? error packet at smbd/ipc.c(97) cmd=37 (SMBtrans) STATUS_BUFFER_OVERFLOW Malcolm -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Permission denied
I have a Windows 2003 server with a share I try and mount a drive as follows : cd ~ mkdir testsmb smbmount //servername/sharename /home/myname/testsmb -o "credentials=/home/myname/smbpassword" and everything seems OK but a ls of testsmb gives ?- ? ? ? ? smbtest you can cd to the directory but ls gives permission denied If I use the Gnome GUI it works OK This is RH FC4 thanks mal -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba extremely slow on XP
On Monday 17 October 2005 15:16, Felipe Augusto van de Wiel wrote: > malcolm escreveu: > > I have a linux machine (1.4GHz) which shares filesystems > > to two Windows machines, (a) Windows 2000 (300MHz) and > > (b) Windows XP (2.4GHz). > > > > The XP machine, which should be faster, is about 10 times > > slower than the 2000 machine. > > Hmmm... I know that the processor speed is really > different (eight times faster), but there are other things > that you should consider on this, NIC, RAM memory, network > infra structure and specially configuration. =) Yes but it's the machine which has a processor eight times faster that is six times slower, i.e. 48 times slower than expected. > > > Anybody any ideas. > > [...] > > > socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY > > What about add: "SO_RCVBUF=8192 SO_SNDBUF=8192" to > socket options, in GNU/Linux systems it should bring better > results to you. ;) That makes perhaps a 3% improvement. > > Also came to my mind things like DNS and WINS, which > should affect w2k and xp in different ways. > > Kind regards, > > -- > // > // Felipe Augusto van de Wiel <[EMAIL PROTECTED]> > // CTI/Suporte - SEDU/PARANACIDADE > // http://www.paranacidade.org.br/ > // -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba extremely slow on XP
I have a linux machine (1.4GHz) which shares filesystems to two Windows
machines, (a) Windows 2000 (300MHz) and (b) Windows XP (2.4GHz).
The XP machine, which should be faster, is about 10 times slower than the 2000
machine.
Anybody any ideas.
Malcolm
% cat /etc/samba/smb.conf
[global]
workgroup = MALCOLM.NET
server string = Samba Server
cups options = raw
interfaces = eth1, 192.168.15.1/255.255.255.0
map to guest = Bad User
log level = 3
log file = /var/log/samba/%m
time server = Yes
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
printcap name = CUPS
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody
-s /bin/false %m$
domain logons = Yes
os level = 65
preferred master = Yes
domain master = Yes
locking = Yes
posix locking = Yes
strict locking = No
oplocks = No
kernel oplocks = No
blocking locks = No
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
local master = Yes
security = user
wins support = yes
name resolve order = wins lmhosts hosts bcast
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Printing Extremely Slow from Windows XP
On Tuesday 06 September 2005 17:16, david rankin wrote: > - Original Message - > From: "Cabbar Duzayak" <[EMAIL PROTECTED]> > I also have a very similar, but perhaps not identical problem. The samba server is on SuSE 9.3 (but the same thing has happened on all SuSEes since 7.0). I have one printer, viz hp psc950 and four DOS boxes in the net. 1 Windows 98 2 Windows 2000 3 Windows XP (home) 4 Windows XP (professional) With the exception of 2, all boxes print almost immediately. But the Windows 2000 takes up to 30 min (minutes not seconds) to print ten pages of a simple Word document. Starting to print the first page can take up to 3 minutes. Needless to say, all boxes are configured in a very similar way. Malcoln Agnew > > Hi, > > > > I have setup samba server on my linux box (Fedora Core 4 with latest > > samba, just updated via RHN) and has configured file sharing via samba > > for this server and connecting to it from my windows xp box. So far, > > everything works fine and it is very fast. > > > > Then, I configured a printer, and shared it via samba. And, I can > > see+connect to it from Windows XP and can even print. But, everything > > related to printing is extreemeeely slow on Windows XP, i.e. open > > notepad -> File Menu->Print, and at that point notepad just freezes > > for couple of minutes, and then brings the printer dialog... Send a > > print out, it just freezes for a while, then prints out fine. > > > > Below is the log file I am getting from Samba, and for some reason it > > tries to connect to the samba server on Windows XP??? Have no idea > > what this means, and how I can fix this. Can you please provide any > > suggestions? > > Cabbar, > > I am seeing the exact same problem. It first started seeing the problem > after moving to 3.0.20a. I have 3.0.20a running on SuSE 9.0 and I have the > exact printer problems you describe. I am also running 3.0.13 on Mdk 2005LE > and I have *no* problems at all. That pretty much eliminates the problem > being the latest xp patch since I connect with a laptop on both systems and > I can print fine under 3.0.13, but I have major slowness with printing > under 3.0.20. Ethereal shows some looping that seems to be caused by DCERPC > error in the communicatons. Since Bartlett did his thesis on DCERPC, maybe > he can shed some light on the issue. > > > -- > David C. Rankin, J.D., P.E. > RANKIN LAW FIRM, PLLC > 510 Ochiltree Street > Nacogdoches, Texas 75961 > (936) 715-9333 > (936) 715-9339 fax > www.rankinlawfirm.com > -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Serious Slowness Issues with Printing
On Friday 17 June 2005 01:59, Kazsuk, Tim wrote: > Samba Guru's: If have a similar problem, so just wondering if you have exactly my problem. I have a linux/samba server (1) Win 2000, (2) Win XP. On the 2000 machine printing takes anything up to 2 minutes befor the first page is printed and a minute gap before each successive page starts to print. On the XP machines printing is almost immediate. The set up for the machines is identical. Malcolm > > I need whatever help you all can provide. I'm at my wits end here with > this problem, I've checked forums and the Samba docs and can't find > anything. Sorry if this email is long and drawn out. > > We just put in a new Solaris 9 server running Samba 3.0.11 to replace a > Solaris 8 server running Samba 2.0.7. All the client desktops are > running Windows 2000 joined to a Domain (there are a handful of XP > machines). > > Within the last 6 months or so associates have been experiencing > slowness printing from Office applications like Word or Excel (it's > sporadic too). It takes an extremely long time to go into the printing > preferences or switch between printers when wanting to print to a > different printer then the default (sometimes 2 min). There have also > been SSL issues within Oracle Forms while trying to print, but that may > or may not be related. This server running Samba is and always will be > just a Print Server, nothing else. > > We're running the following software on the backend for printer > management: JetDirect Printer Installer for UNIX Version E.10.34. > > There are no error messages in /var/adm/messages for the server, all > signs on the server show it's just humming away. > > Has anyone seen this? Am I missing something simple? Are there any > changes you would suggest making to improve printing performance and > times? Is there anything I'm leaving out that you might need to see or > know? > > Full copy of current smb.conf file: > > # Samba config file created using SWAT > # from 207.11.81.253 (207.11.81.253) > # Date: 2005/06/16 16:50:24 > > # Global parameters > [global] > dos charset = ASCII > unix charset = UTF8 > display charset = LOCALE > workgroup = IS > netbios name = PRINTSERVER > netbios aliases = > netbios scope = > server string = Sparc Sun Fire V240 ((%v,%h)) > interfaces = > bind interfaces only = No > security = SHARE > auth methods = > encrypt passwords = Yes > update encrypted = Yes > client schannel = Auto > server schannel = Auto > allow trusted domains = Yes > hosts equiv = > min password length = 5 > map to guest = Never > null passwords = Yes > obey pam restrictions = No > password server = > smb passwd file = /opt/samba/private/smbpasswd > private dir = /opt/samba/private > passdb backend = smbpasswd > algorithmic rid base = 1000 > root directory = > guest account = nobody > enable privileges = No > pam password change = No > passwd program = > passwd chat = *new*password* %n\n *new*password* %n\n *changed* > passwd chat debug = No > passwd chat timeout = 2 > check password script = > username map = > password level = 0 > username level = 0 > unix password sync = Yes > restrict anonymous = 0 > lanman auth = Yes > ntlm auth = Yes > client NTLMv2 auth = No > client lanman auth = Yes > client plaintext auth = Yes > preload modules = > use kerberos keytab = No > log level = 1 > syslog = 1 > syslog only = No > log file = /opt/samba/var/log.%m > max log size = 50 > debug timestamp = Yes > debug hires timestamp = No > debug pid = No > debug uid = No > smb ports = 445 139 > large readwrite = Yes > max protocol = NT1 > min protocol = CORE > read bmpx = No > read raw = Yes > write raw = Yes > disable netbios = No > acl compatibility = > defer sharing violations = Yes > nt pipe support = Yes > nt status support = Yes > announce version = 4.9 > announce as = NT > max mux = 50 > max xmit = 16644 > name resolve order = lmhosts wins host bcast > max ttl = 259200 > max wins ttl = 518400 > min wins ttl = 21600 > time server = No > unix extensions = Yes > use spnego = Yes > client signing = auto > server signing = No > client use spnego = Yes > change notify timeout = 60 > deadtime = 0 > getwd cache = Yes > keepalive = 300 > kernel change notify = Yes > lpq cache time = 30 > max smbd processes = 0 > paranoid server security = Yes > max disk size = 0 > max open files = 1 > socket options = TCP_NODELAY > use mmap = Yes > hostname lookups = Yes > name cache timeout = 660 > load printers = Yes > printcap cache time = 90 > printcap name = /opt/samba/etc/printcap
[Samba] File locking problems
I have been writing some code to perform portable file locking between Linux and Windows. On Windows I use UnlockFileEx() and Linux fcntl(). To get over the incompatibilites between these calls, I use the calls to lock the first two bytes of the file with a read lock. The first byte is regarded as meaning that the file is read locked and the second byte that the file is write locked. The Linux side is routine but the Windows side is somewhat more difficult. If I want a read lock I test if I can get a write lock on the second byte. If successful then I release the lock obtained and set a read lock on the first byte. To obtain a write lock, I test whether I can set a write lock on both bytes, release this write lock and set a read lock on the second byte. This works correctly for a samba share for the cases when client 1 and client 2 are either both Linux or both Windows, or client 1 is Linux and client 2 is Windows. But if the order is changed and client 1 is Windows and client 2 is Linux, the open() call on Linux fails with EAGAIN. So I tried putting the open() call in a "for ( tries = 0 ; tries < 100 : tries++ )" loop with a wait of usleep( 100 ) after each open() attempt. And bingo, this works with about 4 or 5 loops. Untill I discovered that when the delay between starting client 1 (Windows) and client 2 (Linux) is more than a couple of minutes (rather than seconds) then the open loop usually fails even after 1000 iterations. In smb.conf I have: locking = Yes posix locking = Yes strict locking = No kernel oplocks = Yes blocking locks = No Changing any of these means that nothing works. The version of SAMBA is: Version 3.0.13-1.1-SUSE Windows is XP Proffesional Any help gratefully received. Malcolm Agnew -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] How can Windows 2000 mount a share as a service?
I've asked every M$ expert I know, trolled through M$ TechNet, experimented with SRVANY/INSTSRV login scripts which hard-code username/passwords to login to a Samba 2.2.8a SMB server. I've experiment with and without the "Allow service to interact with Desktop" switch turned on. I am stuck. :( I can find no way to mount a share as a service, so that IIS can serve web-pages from a shared content directed located on a network drive. When I run my login script when I'm logged in as the Administrator or another user, the script works fine. The share's mounted and available as the specified drive letter specified in the script. I'm using just the standard "net use" as follows: net use z: \\192.168.0.1\Web mypassword /user:webuser I've fiddled with adding a domain name to the user, to no avail. I've experimented with using the samba server's "Netbios" name as well as DNS name, to no avail. The script only seems to work when SOMEONE is logged into the machine. When it's run as a service, no dice. It just fails with a single digit error code (5, I think). The error is opaque and non-descriptive. It's as if SMB mounting was specifically prohibited by the OS at some internal bowel juncture. This is insane. Surely, people running web-server clusters behind load balancers don't manually synchronise their content! My web application accepts user-uploaded files, so I can't use the "manual resync" method anyway. The upload area needs to be shared by all web-server members. There must be a solution for this very common requirement. I don't want or need a "SAN" block-device-level solution, I want a file-level solution. If anyone can share some ideas or experise, I would be very grateful. This must be a solved problem somewhere. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] best filesystem choice for samba (was: new user cannotlogon)
Quoting Mark Lidstone <[EMAIL PROTECTED]>: > ARGH! I'm wondering if airing thoughts about VFAT performance publicly > was a good idea. I doubt VFAT's case insensitivity would be worth dealing with its terrible linear-search-time directory lookup methods. The reason I suggested reiserfs (or ext3 with directory hashing) is to reduce the high costs of locating a directory entry within a directory of many (> 10,000) files. msdos/vfat does not offer superior directory lookup times, and from my limited testing, neither does NTFS. ext2/ext3 in stock configuration is also slow, though it appears very recent kernels/ext2fsutils offer an FFS-like "directory hashing" option which needs a format-time decision to be made upon setting up the filesystem. I have no knowledge about XFS or JFS and how they compare. I know both are "industrial" filesystems brought down from the Ivory Towers onto the pipsqueak platforms. As for "horror stories", well, each filesystem has had their respective tales of misery and woe... ext3 had shocking and fatal dataloss bugs in the adolescent versions of 2.4.x., and some RAID + reiserfs configs saw some real wowsers as well. From bug reports/changelogs, I've seen similar tales of woe for XFS and JFS if you trigger just the right combination of things. >From my own experiences, things have matured and stabilised with reiserfs and ext3 to the point where using either is fine for my purposes. The decision comes down to: 1) Do you need quotas? If yes, you cannot use reiserfs. 2) Do you need ACLs? If yes, only ext2/ext3 has well-tested seamless support, though I think there are wildcat patches to bring this to XFS (and maybe others) as well. I'm not sure about the stability of this. ext3 used with -O dir_index *MAY* provide better performance for large directory list lookups, but I've never tested it. It requires Linux 2.6 for starters for the kernel-side stuff to actually support it properly. grepping the linux 2.4 source shows no mention of hashing b-trees or dir_index options for ext[23]. This is a RECENT addition to ext3, and I don't think the support actually exists within 2.4 yet. I've seen mention of "special backported patches" but this smells scarier to me than using filesystems which have been seamlessly integrated for over a year or so now. So in terms of viable performance-driven alternatives, I see it being reiserfs, xfs, or jfs. vfat/dos isn't faster, even with case insensitive semantics, for directory sizes of 20,000 or more. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: Re: [Samba] Windows 2K outperform Linux/Samba very much?
Jacky Kim <[EMAIL PROTECTED]> wrote: > I trid 20,000 files in a directory too, and found the same result: > Windows's share is about 10 times faster than Linux/samba's one > when get small file's property(NOT content). Jacky, Not all Linux filesystems are created equally, especially for this kind of file access method. Ext2/Ext3 is probably the slowest filesytem for this kind of thing. I have seen some glimpses of directory hashing being retrofitted into ext2/ext3, but this requires a format-time option with very new tools, with new mount/kernels, etc. You'd be MUCH better off with reiserfs. I've had 500,000 files in a single directory without a significant decrease in performance. I've never managed to get Windows 2000 to manage this without really tanking in performance [I've given up the test harness long before it got that far]. I don't think you'll ever see samba outperforming Windows in this though, because of the case-insensitivity issue, though it should at least match the performance. Reiserfs may provide other benefits (superior access locality) which MIGHT boost performance a bit towards Linux/Samba, but I'd not hold my breath. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: want to ban XP Home Edition
> That's an interesting way to go and I think it *would* work but my > original question was if it is possible for *samba* to distinguish OS > releases and allow/disallow computers then. Or rather I'm sure it is > possible to distuingish them but I just don't know if such config was > ever implemented. Sounds like an excellent excuse to fire up the smb-aware tcpdump tool and look at the initial exchanges between client and server. I would doubt there's an smb.conf option to let you control this, however with the source at your disposal, you can make a patch easily enough. Is your main goal to avoid "weak" operating systems like XP Home, or are you targetting specific users with this requirement? It's a bit unusual. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] want to ban XP Home Edition
> Just for sake of curiosity: > > Is that possible ? > I'd like to support XP Pro *only* and to ban any other Windows OS There are some very advanced networking stacks which allow you to specify filtering based on TCP fingerprints. OpenBSD does, for example. I don't know if XP Home and XP Pro have different enough fingerprints to allow a reliable discrimination between them. This is a puzzling request, though. I am assuming that these unwanted hosts can change their ip#, thus evading firewall/smb.conf based access lists. It's easier to distinguish between XP versus 2000 versus 95, 98, Me, and NT4, etc. Those have rather different fingerprints. If you don't use OpenBSD, I suppose you could make use of nmap to perform a quick on-the-fly OS fingerprint and then pull up a firewall against that ip#, thus blocking the unwanted user(s). It seems to me that it'd be simpler to just allow access only from certain domains, etc. Malcolm -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] conflict between Realtek 8139 (client) and 3c2000T(server) NIC's with Samba?
> I *might* be a Realtek issue... I have heard that Sage (the accounts > software folk) say that their software will not work properly over a > network which uses these Realtek cards. Save yourself far more than the few dollars of false economy and throw away your Realtek junk. I had so many "strange" and "seemingly application level" problems just vanish when I put real 3Com/Intel/etc network cards into my servers and workstations. The 8139, 8169, et al... all of them are junk. I just spent a week diagnosing a strange packet loss issue with the 8169 (GigE) interface which only manifested itself under pretty heavy loads in a difficult to reproduce manner. It occurred often enough to break my application at least twice a day, but I couldn't get it to fail predictably so I could easily debug it. After the usual wasted DAYS of swapping NICs, cables, switches, and even machines... I changed to an Intel network card, and all of my problems were solved. Do yourself a favour: get rid of that junk. The math just doesn't work. Cost delta of NIC? Maybe $15-20 tops. Cost your wasted time? HUNDREDS of $$$, at least. =Malcom= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba - Oplocks = no
> In order to deal with bizarre MS Office junk, it looks like I may have > to disable oplocks on my samba server. I feel your pain. You *CAN* just oplock veto all M$ Office files instead. > What kinds of problems, if any could arise from my having disabled > the oplocks? Just lower performance. Oplocks are "OPportunistic LOCKS", which provide for client-side caching to be performed safely. No oplocks, no caching. What I always wonder though is whether or not these oplock problems plague Windows NT/2000 file servers as well, or if it's just an achilles heel within Samba. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Time server
> This will not automatically work against Samba, as we mimic NT4, which > didn't know about NTP. > > But you can manually configure the NTP server on the client, and run an > NTP server on your PDC if you wish. The Microsoft time services are substandard and do not implement a full NTP time management protocol. It's best to leave that to a real implementation like the xntpd-4 (or equivalent commercialised NT/2000 products built on similar technology). If you want to use the W32Time services, use them as clients. The default (under 2000) is to resync the time periodically in increasing intervals, settling in at about 3 syncs/day, I believe. Simple recipe to configure Windows servers to use it: net stop w32time net time /setsntp: dns-name-of-real-ntp-server (or it's ip#) w32time -s (hit Control-C if it doesn't return after 4 or 5 seconds) w32time -s (yes, sometimes it takes a couple of tries to get the time locked down) net start w32time Then make sure in the Services control panel that the Windows Time Service is configured to auto-start. Thereafter, it will resync every 45 minutes until the error is under 1 second, and then resync every 8 hours from that point forward. No clock-skew adjustments or other time conditioning is attempted, unlike a real NTP implementation. The MS W32time service seems to only care about one-second accuracy. Be aware of this if you "chain" time services as this jitter will accumulate. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: Re[2]: [Samba] NUA + MYSQL?
> why don't you map your users to the nobody or guest account ?? > (is this possible ??) Sure, but you can kiss away all pretenses of file security between "users". > so all users are guests... > dunno how to do it, but would be a nice work around.. It's easy. But very unwise. I highly doubt the original poster wants all of his users to have the same security contexts with respect to file ownership/access. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NUA + MYSQL?
> Re: the release of Samba3 and NUA capabilities I have found this: > > [...] > Late in the > development cycle, the team doing this work hit upon some obstacles that > prevents this solution from being used. > > > Can anyone tell me what sort of progress has been made in the NUA areas? > Specifically I want something like "passdb backend = mysql_nua". I would imagine the passwords would be the least of the problems. I don't know of any way you could completely do away with "user accounts" or at least, entries in /etc/passwd, given that most UNIX systems lookup passwd/NIS for UID/GID on file ownerships and whatnot. You might have all "locked" passwords in /etc/shadow [or equiv], with authentication for samba being all SQL driven, but at the end of the day, the smbd needs some EUID/EGID's for the file permissions stuff. I imagine there's quite a bit of funk to get through. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] why "xcopy /d" doesn't work
Quoting [EMAIL PROTECTED]: > Curious. I wonder if this is related to problems me and others have been > having when trying to keep linux / windows shares in sync using rsync? Hrm... I assume this isn't a dos filetime resolution time sort of issue? There are also differences in date semantics between DOS/Windows and POSIX. A careful perusal of the smb.conf documentation will clarify the issues involved. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] How to share WIN partitions from SAMBA (Dual boot) Srvrto WIN clients?
> There _is_ a write-read ntfs driver available for Linux. It's > called Captive. I've not tested it myself. So I can only inform. Yes, I know. But it's dangerous to actually use, and can only be safely used to overwrite files of exactly the same size, which has been used by various Windows 2000/NT "Administrator Password Reset" tools. It's *NOT* safe to use for writing/creating files the way you would normally expect read/write support to work. YOU WILL CORRUPT YOUR NTFS VOLUME! =R= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] How to share WIN partitions from SAMBA (Dual boot) Srvr to WIN clients?
> Malcolm > Perhaps I am getting near the end ...)of this process, of my rope, or > both) Uh-oh. > I ensured the fstab reeferenced the NTFS partitions as ro (read only) Please zip up your /etc/fstab file and email this to me. > I ensured my smb.conF to declare the WIN shares as browseable=yes, and > read only = yes. You've restarted smbd since changing the smb.conf file? > Paths are /mnt/hd/c and d, respectively, corresponding to > two DOS/WIN partitions C: and D: (/dev/hda2 and /dev/hda5) Both of these are mounted? Paste the output of cat /etc/mtab in an email to me. > I chmod the actual /mnt directory to Octal 555 (r_x), and the > sub-directories also. > Both Linux Server and WIN client can access the shares, but there are no > files there ...ls command returns nothing. That is my problem. The ls command under which environment? The local Samba server's? (logged in via SSH or console?) Firstly, please verify you can see the files from the SAMBA server locally, i.e., login to its console or via SSH, and perform an ls /mnt/hd/c and make sure you see the files there. It's also possible that the file permissions the ntfs driver is passing back are too restrictive. Aha. This is your problem. I just peeked at the ntfs section of mount: Mount options for ntfs: [...] uid=value, gid=value and umask=value Set the file permission on the filesystem. The umask value is given in octal. By default, the files are owned by root and not readable by ^^^ somebody else. ^^ In the options section of /etc/fstab for the two NTFS volumes, you will want the following options: uid=desired-uid-to-own-the-files,gid=desired-group-number,umask=770 So something like: /dev/hda2 /mnt/hd/cntfs ro,uid=1000,gid=100,umask=770 0 0 /dev/hda5 /mnt/hd/dntfs ro,uid=1000,gid=100,umask=770 0 0 Should do the trick. Replace uid/gid with whatever values you deem pertinent. Keep in mind that ntfs permissions will be disregarded for the most part [from a user/group perspective]. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] How to share WIN partitions from SAMBA (Dual boot) Srvr to WIN clients?
[Replying to list] Quoting George Peters <[EMAIL PROTECTED]>: > Malcolm - thanks for the prompt reply. > I don't think I am trying to share a remote smbmounted file. Rather, I > AM trying to share a LOCAL (and presumably MOUNTed) WIN partition. OK. > Why am I doing this? On my home network, the WIN client runs WIN apps > like MS OUTLOOK that share one common OUTLOOK data file (one user at a > time) with my "server" WINXP machine. I want to have this box in Linux > mode (not WIN). You don't have many options then. 1) If you're stuck with using NTFS, you can only use read-only mode. Make your smb.conf share those as read-only [you can enable fake oplocks on the read-only shares for extra speed w/o risks]. You will need to mount the share as ro. Make sure you change the /mnt directory permissions to allow browsing (+rx). 2) If you can reformat the partition to use FAT32 (note: despite Win2k's protestations at FORMATTING a FAT32 larger than 32GB, the format DOES support up to 127GB. There are replacement tools for Win32 (which are essentially ports of the Linux mkdosfs) to format FAT32's > 32GB. Google for them. > How can I make it available? Is it even possible? I am prepared to > forget about the Read-only constraint. Sure it's possible. It's very simple and straightforward. Samba will cheerfully share that read-only NTFS volume for you. Cheers, =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] How to share WIN partitions from SAMBA (Dual boot) Srvr to WIN clients?
> Finally , booting LINUX mounts the NTFS file systems (from fstab file), > with a warning "W2K+, Read Only". Correct. The ntfs filesystem on linux is still very early, and writing to an NTFS volume will cause it to be damaged unless what+how you write is carefully restricted. For your purposes, it's useless for writing. > I thought write to NTFS was possible thru SAMBA. No. All Samba does is allow remote clients to mount UNIX-accessible volumes via SMB/CIFS. These may be Windows, UNIX, or even MacOS (X|Classic) clients. > Again, I must be missing something. SMB.CONF file appears to be > correct, defining the shares as writeable, etc Samba can't even exceed the capabilities of the native operating system under which it's running. With or without samba, you cannot get Linux to (safely) write to NTFS volumes on its local filesystems. If what you're trying to do is re-export a mounted share via the samba server, that will probably work, but you will cause a great deal of redundant network traffic, and the performance will tank. (In other words, you mount some remote WinXP share via smbmount, and then use samba to share that volume...) Good luck, =R= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] One samba, two interfaces
> Is it possible to have a samba listen on different interfaces for > different NETBIOS names specific to that interface? > > I have a samba listening to eth0 and eth1, which are two interfaces on > the same network. Even when I use smbclient to the ip address of eth1, > smb.conf's %h gives me the eth0 hostname, so it doesn't seem I can do > any include trickery to make this work. Is it even possible? I'd look at the code to see if the expansion for %h takes into account the destination IP# address connected to. If you can't patch it to do what you want, you might need to run two sambas, each with its own smb.conf file bound to a single interface. If you're using an OS with "real" oplock support and reasonable locking, then things should be fine, since cross-smbd locking will just work. =R= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Win viruses
> We have had our server blocked as it is probing port 25 Port 25 is the SMTP (mail delivery) port. Maybe your Samba server is trying to issue emails out for some reason. Odd that this would be considered a "probe" though. Does the Samba server run any kind of SOCKS proxying software, or even web-proxying software? > My question: Is it actually possible for a Samba system to be infected > with Win viruses such as MyDoom or Blaster? I'll answer your question with another question: is it possible for a UNIX-based mail host to "be infected" with MyDoom or Blaster emails? In both the Samba and the Mailhost case, you have three parties, one of whom doesn't really "parse" data content, but to the other two parties [the source and destination parties, really], the payload has a great deal more "meaning". Clear now? :) Cheers, =Rob= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Re: Purpose of param. "time server" ?
> Yes, ntp is the solution, but my original question was what is purpose > of that fucking option ?! I would say, have you tried reading the fucking documentation? :) >> from smb.conf << time server (G) This parameter determines if nmbd(8) advertises itself as a time server to Windows clients. Default: time server = no <<< There. It looks like an *NMBD* option more than an *SMBD* option. =R= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Purpose of param. "time server" ?
> a) Ability to set clock by "net time ..." don't depend on value of this > parameter on SAMBA server. I don't know if Samba supports the call if you don't specify that. > b) Ability to set clock by net time on NT and subsequent Windows is based > on system rights of current user, and so it is not sure to work. Correct. Consumer Windows [95/98/Me] let you do it unconditionally. > c) Setting clock during execution of login script is dependent on user > logging and then accurancy of clock depends on frequency of logging in. Correct. And it's not very precise either. I think +/- 0.5 second is the best you can expect, and it's probably not even that good. It's not NTP, nor does it condition the system's clocks. You're better off using W32Time for NTP, which comes built-in with Windows 2000, and is an easily obtained download for Windows NT. > Is somebody able to explain me it more thoroughly ? You'd sprinkle "net time \\sambaserver /set" into the login scripts of your various users. This is easier to do for Windows 95/98/Me of course. =R= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Automount from Windows w/o logging in first?
> let's stay on the list. No worries. > DFS is windows version of nfs exports/mounts I got that far... but... but... looking at the M$ doccos for DFS, I don't see where "clients" of the DFS servers are setup. > Samba 3 supports dfs. I don't think 2.2.x does. > > Microsoft offers Services for Unix for free - you can mount nfs shares > on Windows. Hrm I'd prefer to mount SMB shares, because my experience with Windows mounting NFS isn't entirely pleasant. I don't think locking is consistently designed or implemented. I remember alot of headache with this the last time I tried using NFS under Windows NT. > Windows share mounts in user space don't work because someone has to log > in to Windows machine - it's something that has to run as a service as > you have discovered. Hrm. Surely I can't be the first person to want to serve IIS pages out of a network share?! > In my mind it's either nfs mounts or dfs or you have to 're-think' your > options (i.e. rsync files on each windows server from 'master') rsync, blech. Are there good rsync implementations for Windows? OK, then, I'll bite. Just how DO load-balanced webservers serve up content from a central content repository? I can't believe people rely on out-of-band file/directory sync tools. It seems like having a "system mounted" share which is activated at service start time prior to the invocation of IIS would be a straight-forward matter. What do servers which rely on SANs for centralised storage make use of? Surely not "normal" SMB, then. If these were UNIX webservers, yes, NFS would be the natural choice. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Automount from Windows w/o logging in first?
I am trying to do something which should seem very straightforward, not to mention, not unusual for load-balanced web servers, namely: providing a faceless/login-less mounting of SMB shares from NT4 and Win2K servers. Yes, I accept that I will need to stash a plaintext login key in some script or registry key. The security impacts are acceptable. I have the latest Samba 2.2.x server, and a bunch of NT4 (soon to be Windows 2000 Server) web-servers from which I'd like to serve IISROOT directories residing on a samba share. I've tried NTResKit srvany.exe'ing a "net use" command and lots of other hacks to wire in a "service" which provides a complete "net use W: \\server\WEB\ webpassword /user:weblogin" sort of thing. No dice. Soo how DO you automatically mount shares without having to login at the console, so that IIS/Cold-Fusion can serve content out of the Samba share? Thanks! M.B. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Lots of automount help for Linux clients, but how about FROM Windows?
I am trying to do something which should seem very straightforward, not to mention, not unusual for load-balanced web servers, namely: providing a faceless/login-less mounting of SMB shares from NT4 and Win2K servers. Yes, I accept that I will need to stash a plaintext login key in some script or registry key. The security impacts are acceptable. I have the latest Samba 2.2.x server, and a bunch of NT4 (soon to be Windows 2000 Server) web-servers from which I'd like to serve IISROOT directories residing on a samba share. I've tried NTResKit srvany.exe'ing a "net use" command and lots of other hacks to wire in a "service" which provides a complete "net use W: \\server\WEB\ webpassword /user:weblogin" sort of thing. No dice. Soo how DO you automatically mount shares without having to login at the console, so that IIS/Cold-Fusion can serve content out of the Samba share? Thanks! M.B. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Printing Slow
Did you get any response to your question Thu Jul 17 00:38:40. My printing from Win2K to Linux (SuSE 9.0) is very very slow - up to 5 minutes for 10 pages. Malcolm -- Malcolm Agnew <[EMAIL PROTECTED]> Lersnerstr.38 60322 Frankfurt/Main Tel: **49 69 598612 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] LDAP Supplementary Groups not recognised
Thanks for the response, Bas Goes wrote: Hi, What does id tell you and wat da's the ldapsearch on a group say? it works just like the groups file only now usernames are stored as attributes to a group ldap entry I can access the group protected directory fine when logged in as the same user in a Solaris shell. 'id -a' shows the supplementary group correctly, as does ldaplist and ldapsearch. 2 things you need to check are" 1 is the group in ldap and is the user a part in this ldapgroup ldif? ldapsearch -x -D -W -b "uid=" i myself use ldapexplorer to browse the ldapdatabase Unfortunately I do not have access to the LDAP directory at the moment. However ldapsearch's do show the group in question and the user being a memberUid attribute. I also have confirmed this with a GUI browser. 2 check if nss looks in the (right) ldapbase if 1 isn't the case and id doesn't work this is probably the problem in debian it is in nsswitch.conf in /etc/ if it uses ldap /etc/libnss-ldap.conf if ldap is configured correctly /etc/ldap/slapd.conf if nss has rights to browse these ldap directories Yes what is fustrating is that supplementary LDAP groups are working fine from the Solaris shell, it is only SAMBA that appears to be ignoring them. Do posixGroup entries have to have any additional attributes or be in a particular base to be recognised by SAMBA, Solaris 9 by default puts them in ou=group,dc=xx,dc=com. Good luck regards Bas Thanks Malcolm Gibbs -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] LDAP Supplementary Groups not recognised
We are implementing the following: Solaris 9 iPlanet Directory Server 5.1 (bundled with Solaris 9) openldap 2.1.16 Only used for ldap libaries (samba will not compile without. Is this other people's experience?) samba 2.2.8 compiled with ./configure --with-ldapsam --with-acl-support We have the samba server acting as a PDC with all user and machine accounts in LDAP as sambaAccounts. We are successfully adding Windows XP workstations to the PDC and authenticating users. However supplementary groups for users are not being recognised (i.e posixGroup entries with the user as a memberUid attribute). Only the primary group (from sambaAccount) is being recognised as shown in the log. This results in a permission denied when accessing a directory with only group permissions. [2003/04/04 09:53:59, 3] smbd/sec_ctx.c:set_sec_ctx(334) 1 user groups: 1000 Interestingly supplementary groups from /etc/group are being recognised. If the same user logs into Solaris (the users have posixAccount entries as well) they can see and use all their supplementary groups (using Solaris 9 nss built in support). Is this a bug or something we are doing wrong. Any help would be appreciated. Thanks -- Malcolm Gibbs, Sun Microsystems (NZ) Ltd -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Help - Moutning XP Drives on Linux box using.
Hey all. I've got four computers in a small network (Actually more, but keeping it simple to get to the point) 1> Linux Server (RH7.3) Running Samba (Default version with RH7.3) 2> Windows 2000 Workstation 3> Windows XP Pro. 4> Windows 98SE All of the windows boxes can connect, without problems, to the SAMBA server, and all the shares. No problems whatsoever. All boxes (with the exception of the 98 Box) have user accounts that match in user name and password, making everything work pretty smoothly. The 2000 and the XP box also have shares on them. All of the windows boxes can see each other, connect to the shares, no problem. Here is where it gets interesting; The Linux box can mount a share on the Windows 2000 box without problem. ( i.e. I can mount the \\\c$ to \mnt\net1 on the Linux box) However, I can't mount to the XP box in the same manner. It seems like M$ has built in some kind of noncompatability for Samba (Wouldn't surprise me there), or at least noncompatability with SMBMount (or 'mount -t smbfs' ) Here is a screenshot of what I am getting; [root@hoc etc]# mount -t smbfs -o username=malc,password=*** //bytelair/c$ /mnt/net1 5356: tree connect failed: ERRDOS - ERRnoaccess (Access denied.) SMB connection failed [root@hoc etc]# Note: The XP box does have an account malc that is an administrator, and I can connect using the same account and password to the c$ share from the windows 2000 box. Any help would be appreciated! Malcolm Jack Manager Systems Infrastructure / Telecom "Let's Roll. . ."
[Samba] SMBMOUNT to C$ Share on Windows XP. HELP!
Hey all! Ok, here's the deal. It's a little off topic as it centers more around mount and XP issues then actual Samba, but they all seem to tie together, sooo . . . I have a RH 6.2 Box running a Samba (2.0.10) server with no problems. I have a mixed network of Windows NT4, Win 98/95 Boxes, and Windows 2000 WS and Server. Everything was talking just fine. Not only could the M$ boxes see the Samba server, I could go the other way using mount -t smbfs. I use the format ' mount -t smbfs -o username=foo,password=bar //server/share /mnt ' It has worked just fine provided 2 things; 1> The share existed (This includes the NT/200 Administrative Shares (C$ D$) 2> I used a valid username/password on the box I was connecting TO (i.e. Local account on the NT box) Everything has been fine with NT, and 2000. Problem: I just upgraded a box to XP-Pro. Everything is fine going from XP to SAMBA, no problems at all. But SAMBA to XP is no longer working. Example below [root@hoc samba]# mount -t smbfs -o username=administrator,password= //bytelair/C$ /mnt/net1 tree connect failed: ERRDOS - ERRnoaccess SMB connection failed [root@hoc samba]# It seems to me to be an access problem, that XP dosen't like the authentication token given, but Windows 2000 likes it fine. Any ideas? TIA! Malcolm
[Samba] SMBMOUNT to C$ Share on Windows XP. HELP!
Hey all! Ok, here's the deal. It's a little off topic as it centers more around mount and XP issues then actual Samba, but they all seem to tie together, sooo . . . I have a RH 6.2 Box running a Samba (2.0.10) server with no problems. I have a mixed network of Windows NT4, Win 98/95 Boxes, and Windows 2000 WS and Server. Everything was talking just fine. Not only could the M$ boxes see the Samba server, I could go the other way using mount -t smbfs. I use the format ' mount -t smbfs -o username=foo,password=bar //server/share /mnt ' It has worked just fine provided 2 things; 1> The share existed (This includes the NT/200 Administrative Shares (C$ D$) 2> I used a valid username/password on the box I was connecting TO (i.e. Local account on the NT box) Everything has been fine with NT, and 2000. Problem: I just upgraded a box to XP-Pro. Everything is fine going from XP to SAMBA, no problems at all. But SAMBA to XP is no longer working. Example below [root@hoc samba]# mount -t smbfs -o username=administrator,password= //bytelair/C$ /mnt/net1 tree connect failed: ERRDOS - ERRnoaccess SMB connection failed [root@hoc samba]# It seems to me to be an access problem, that XP dosen't like the authentication token given, but Windows 2000 likes it fine. Any ideas? TIA! Malcolm
