[Samba] ( Paid ) Expert Required in Sydney for Vampire process
Hi all. We're looking for a Samba expert in Sydney to come on-site and perform a Vampire from an NT4 domain controller ( which is dying ) to a new Ubuntu system which will then act as a domain controller. I've tried doing a vampire of this system before and not had much success. I don't have time to do it now, as I'm leaving this job in 5 days, and we want to get things off the NT4 server before it dies completely. Please email if you can help us out. We will of course pay. -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Domain authentication not working
: Remote machine NUS_AUST_NT pipe \NETLOGON fnum 0x980b bind request returned ok. [2007/05/21 11:40:26, 2] auth/auth.c:check_ntlm_password(319) check_ntlm_password: Authentication for user [administrator] - [administrator] FAILED with error NT_STATUS_NO_SUCH_USER [2007/05/21 11:40:26, 3] smbd/error.c:error_packet(146) error packet at smbd/sesssetup.c(99) cmd=115 (SMBsesssetupX) NT_STATUS_LOGON_FAILURE [2007/05/21 11:40:26, 3] smbd/process.c:process_smb(1110) Transaction 10 of length 43 [2007/05/21 11:40:26, 3] smbd/process.c:switch_message(914) switch message SMBulogoffX (pid 21422) conn 0x0 [2007/05/21 11:40:26, 3] smbd/sec_ctx.c:set_sec_ctx(241) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2007/05/21 11:40:26, 3] smbd/reply.c:reply_ulogoffX(1607) ulogoff, vuser id 102 does not map to user. [2007/05/21 11:40:26, 3] smbd/reply.c:reply_ulogoffX(1618) ulogoffX vuid=102 The smb.conf file: [global] security = domain workgroup = NUSAUS wins server = 10.146.0.2 domain master = no domain logons = no local master = no preferred master = no server string = Samba Server %v passdb backend = tdbsam encrypt passwords = yes log level = 3 log file = /var/log/samba/log.%m max log size = 50 name resolve order = wins lmhosts bcast socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = cups os level = 0 keep alive = 60 wins support = yes printing = cups load printers = yes [print$] comment = Printer Drivers path = /etc/samba/printer # this path holds the driver structure guest ok = yes browseable = yes read only = yes # Modify this to username,root if you don't want root to # be the only printer admin) write list = root [printers] comment = All Printers browseable = no printable = yes writable = no public = yes guest ok = yes path = /var/spool/samba # Modify this to username,root if you don't want root to # be the only printer admin) printer admin = root -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Domain authentication not working
On Mon, 2007-05-21 at 11:46 +1000, Daniel Kasak wrote: Hi all. I'm trying to share a printer out via samba, and it's suddenly stopped working. Samba says it's connecting to the DC, but then returning NT_STATUS_NO_SUCH_USER. Right. I have things 'working'. I added a 'dkasak' account on the samba server, and NOW it authenticates. Is there a way to allow clients to authenticate against DOMAIN accounts from an NT4 PDC to access services on a SAMBA server WITHOUT having a user account with a matching name on the samba server? -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Yearly attempt at 'vampire' of NT4 domain
Hi all. Since our NT4 PDC is on it's last legs, I've been motivated to once again try to use samba's vampire functionality. Unfortunately I'm actually doing worse than last year ... My smb.conf: [global] socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 interfaces = 10.146.0.254/255.255.0.0 encrypt passwords = yes printing = cups name resolve order = wins lmhosts bcast server string = Samba Server %v debug level = 9 os level = 33 bind interfaces only = true max log size = 50 log file = /var/log/samba3/log.%m password server = NUS_AUST_NT security = domain workgroup = NUSAUS netbios name = screamer wins server = 10.146.0.2 domain master = no domain logons = no local master = no preferred master = no add user script = /usr/sbin/useradd -m '%u' delete user script = /usr/sbin/userdel -r '%u' add group script = /usr/local/bin/smbgrpdadd.sh '%g delete group script = /usr/sbin/groupdel '%g' add user to group script = /usr/sbin/usermod -G '%g' '%u' add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null '%u' If I add an account for screamer ( normal account ) in the NT4 PDC, I can join the domain and people can access my shares ( not listed ). However if I run: net rpc vampire -S NUS_AUST_NT -W NUSAUS -U administrator I get: Cannot import users from NUSAUS at this time, as the current domain: SCREAMER: S-1-5-21-2979890208-4094237718-1229784985 conflicts with the remote domain NUSAUS: S-1-5-21-667748849-896033114-1233803906 Perhaps you need to set: security=user workgroup=NUSAUS in your smb.conf? Also, if I remove this server from the domain and add it as a BDC ( as some places have suggested ), and also change the line in my smb.conf: domain logons = no to: domain logons = yes I'm unable to join the domain at all ... I get a message about conflicting credentials. The *only* way I can join is as a normal workstation AND domain logins = no Who knows what's going on? -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba MS Access problems
Juan Ignacio Barbosa wrote: Hi, I'm having an odd behaviour with a samba file server (3.0.14a) on ubuntu 5.10 breezy an MS access files. When a user open an mdb file, this file can't be opened by anyone else by doubleclicking on it, (simply nothing happens), BUT if I open Ms Access and then open the file manually from there, there is no problem. I'v tried on Windows XP shares and this is not happening. I'v tried a newer version of ubuntu+samba (6.06+3.0.24) but the problem it's still there. Any idea how to solve this, if posible? While I can't help you much with the samba side of things, I can tell you that you should avoid having multiple people accessing the same Access mdb file at once. While Access is supposed to support this in theory, in practice it doesn't work that well, and I would be particularly paranoid about having it sitting on a samba server ( sorry ). Are you using Access to store the data, or just as a front-end with linked tables? If you're using linked tables, then get everyone to create a local copy of the Access mdb file and use the local copy. If you're using Access to store your data ( which is in itself asking for trouble ), then disregard what I've just said and keep looking for a solution ... and investigate moving your data to a database server and linking the tables in Access ( or even better, getting rid of Access completely ). -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Vampire and spaces
Hi all. I'm having another go at using the vampire functionality to move our NT4 domain to samba. I've hit the same problem as 3 years ago - spaces in names ( group names for us ). I believe there are some useradd scripts floating around that deal with this, but I can't find them ( spent 1/2 an hour on google, honest ). Does anyone have one handy? How about adding scripts like this to the default samba install? -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] The credentials conflict with an existing set of credentials
Hi all. Today my samba server, which has been working fine for quite some time, is not allowing me to mount shares on it. In Windows, I get the error: The credentials conflict with an existing set of credentials My log.smbd shows: [2005/03/21 14:26:14, 0] auth/auth_util.c:make_server_info_info3(1134) make_server_info_info3: pdb_init_sam failed! The above is repeated over over over over again ... Since I haven't changed anything, I'm at a bit of a loss as to what's wrong. Any clues? Dan -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] The credentials conflict with an existing set of credentials
Daniel Kasak wrote: Hi all. Today my samba server, which has been working fine for quite some time, is not allowing me to mount shares on it. In Windows, I get the error: The credentials conflict with an existing set of credentials My log.smbd shows: [2005/03/21 14:26:14, 0] auth/auth_util.c:make_server_info_info3(1134) make_server_info_info3: pdb_init_sam failed! The above is repeated over over over over again ... Since I haven't changed anything, I'm at a bit of a loss as to what's wrong. Any clues? Dan False alarm. I had deleted my user account on the linux server ( I'm authenticating against an NT4 domain, so I didn't realise I needed a user account on the linux server ). -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Access 2003 printing?
Derek Harkness wrote: Has anybody found a fix for the Access 2003 printing? I've got a couple of work arounds but neither is a good long term solution. My solution was to replace Access ( XP in our case ) with Gtk2-Perl apps - reports are rendered direct to PDFs and opened in gpdf. You'd be surprised how well it works :) If you want a quick workaround and you're using a CUPS printing backend on your Samba server, you can try using direct IPP printing ( without Samba in the middle ... sorry to anyone who is offended by this solution ... I don't mean any harm ). There are plently of instructions around on how to do this, but you basically use the 'add new printer' wizard, and on the first step ( where it asks you for the share name or to click the browse button ), you select the bottom option ( print to a printer on the internet or your intranet ). Then enter the printer's path, in the format: http://servername_or_ip_address/printers/printer_name_in_cups so my 'laserjet4500' printer in cups is: http://10.146.0.254/printers/laserjet4500 It works like a charm for us. Of course if you need to have Samba in the equation for some reason, then this option will not do at all. But if you just want to get your damned Access 2003 apps to print to your printer then it will work great. One more possibility to try before all this is to check what drivers you're using. I don't know the exact problem you're having, and this might be completely unrelated, but Access refuses to print through PCL6 drivers on any of our printers ( last time I tested this was through Samba, but now we're using direct IPP everywhere ). Downgrading to PCL5 drivers got printing working for us. -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] AD-Linux: Thoughts
Turbo Fredriksson wrote: snipped Now, the customer seems to be bitten by the must upgrade because there's newer versions bug (as opposed to the 'standard' UNIX way - only upgrade if you'r absolutly forced I'm used to :). The Linux version this time is open for discussion (SuSE have been mentioned - have no opinion there). snipped I can't comment on your Samba problem, but as for a choice for a server, Gentoo makes a very nice server. You only install packages as you need them ( security bonus ). It's also very easy to keep the box up-to-date, so your customer will be able to get what he wants in terms of continual upgrades without too much effort on your part. Gentoo's upgrade system is pretty cool. I assume you've heard about it's 'portage' system and 'emerge' script, so I'll tell you about the lesser-known 'etc-update' script... It merges in any simple changes to config files that come with the version upgrade you've just done, and notifies you of config files with large changes that it can't deal with so you can decide what to do with them. I've done everything from glibc updates to compiler updates to xfree86 updates to apache updates with no problems as all. Anyway, it's worth a thought if you will have to keep the box up-to-date. -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] net rpc vampire case sensitivity problem
Ed Ravin wrote: We just migrated a small network from a Win2K PDC to Samba, using net rpc vampire into a tdbsam backend on a Samba 3.0.2a Linux box. One of the users, let's call him Jon Harker, had the NT username JHarker. When we ran pdbedit -v jharker, we saw this: Unix username:JHarker NT username: JHarker Well, that looks wrong - the NT username can be mixed case for all I care, but shouldn't the Unix name be all lower case? We changed jharker's /etc/passwd entry to JHarker and he was subsequently able to login. Since we didn't like that as a fix, we changed /etc/passwd back to all lower case and carefully edited the passdb.tdb in emacs (the binary editor of choice on Unix systems :-) to knock the mixed-case usernames into lower case, which also fixed the problem. Both of these users already had accounts (all lower case) in /etc/passwd before we ran net rpc vampire. Other than this, the vampire process ran very smoothly. -- Ed Interesting. I remember have case sensitivity problems ( among others ) when using 'net rpc vampire' with 3.0.1-rc-something. Actually I had such a hard time that I decided to hold off until the process went a little smoother. Yeah I also remember hand-editing /etc/passwd entries ( sometimes unsucessfully - I rooted some guy's account good ! ). Have there been any bug fixes to the 'vampire' function since 3.0.1? While I understand the cause of the case sensitivity problems, I think this still needs more attention - perhaps all names should be forced to lower case? Lets just say that my previous experience didn't exactly inspire confidence in the system I was setting up - hence we are still on an NT4 domain controller. Anyway, since someone else had a 'very smooth' experience, maybe I was partly to blame. I'll give it another go when I get more time. -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] net rpc vampire case sensitivity problem
Ed Ravin wrote: Here's a thought: how about an option to the vampire to spit out commands to import the users rather than doing it itself. Then you could save the output, edit it if needed for case problems or removing users that you don't want to import, then run it. Now we're talking! How about the vampire process being a 2-step one, first exporting to a simple text file with a mapping table, eg: 'nt_user', 'samba_user', 'dKaSaK', 'dkasak', 'JSmith', 'jsmith' So you can edit the file, then continue with the 2nd step, which reads the above file and honours the mappings ( and ignores those you've deleted ). That would be swt! -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] net rpc vampire case sensitivity problem
John H Terpstra wrote: The problem you refer to is not a 'net rpc vampire' issue. This is specifically an issue pertaining to the host operating system that Samba is running on. In the Samba-HOWTO-Collection chapter on Migration I have provided a shell script that can be used to get around this OS problem. The script is in Example 12.1, called smbgrpadd.sh. You can easily craft a similar script to handle addition of user accounts. Please let me know if this is not an acceptable solution for you. - John T. Right. I read that HOWTO ( honest, a few times ), but I missed that script. When I next attempt the migration, I'll give it a go. What are the chances of getting something like this merged in with the vampire process? -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] net rpc vampire case sensitivity problem
John H Terpstra wrote: On Fri, 26 Mar 2004, Daniel Kasak wrote: John H Terpstra wrote: The problem you refer to is not a 'net rpc vampire' issue. This is specifically an issue pertaining to the host operating system that Samba is running on. In the Samba-HOWTO-Collection chapter on Migration I have provided a shell script that can be used to get around this OS problem. The script is in Example 12.1, called smbgrpadd.sh. You can easily craft a similar script to handle addition of user accounts. Please let me know if this is not an acceptable solution for you. - John T. Right. I read that HOWTO ( honest, a few times ), but I missed that script. When I next attempt the migration, I'll give it a go. What are the chances of getting something like this merged in with the vampire process? Why might we want to impose the restriction needed because of a brain-dead OS implementation on ALL OS platforms? - John T. ??? To make the product easier to use maybe? It's all very well to say Oh yeah. That doesn't work. You'll have to manually add that, and modify this script here to fit that, and wave a dead chicken over this thing here unless that over there has already done this, and ignore that error ... that's supposed to happen and claim it's all Microsoft's fault in the process. Maybe it is. But here you have an end user ( and I'm relatively motivated compared to most end users, even though I probably fall short of a Samba developer ) saying that they want a little more integration of tools to make the process easier. Merely stating that this problem is Microsoft's fault does nothing to address the issue that the vampire command in it's default configuration doesn't work in many situations. What I'm suggesting is NOT that we all plague our OSs with Microsoft's mistakes to become compatible, but that we merely integrate the loose collection of scripts and how-tos and other assorted good advice into a coherent package that you can use to achieve the outcome that end users are after: to migrate from NT to Samba - not to research and debate the finer details of the differences between Microsoft's and Linux's implementation of feature X. I'm also not clear on what restrictions would be imposed by giving the user an option to run a script that converts NT user names into Linux-friendly user names. Surely the amount of time it takes to add such scripts to the how-to collection and answer posts such as mine would be better spent in integrating the scripts into the actual product? -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] net rpc vampire case sensitivity problem
John H Terpstra wrote: snipped Wowa! Please understand that I was referring to the Linux implementation being brain-dead - NOT MS Windows. I totally agree that Samba should provide the ability to implement the same look and feel of MS Windows servers. I see. So you were referring to my distro ( Gentoo ) when talking about brain-dead OSs. My apology. snipped My question remains. Why would should we implement as part of the 'net rpc vampire' process an imposition on ALL UNIX/Linux platforms just because one platform wants to force you as the administrator to have only contiguous lower case names for users and groups? I agree that the ability to call a script would possibly be nice. My experience is that most sites will use the opportunity to re-arrange the deck chairs during the migration process. I am not convinced that the ability to call a user/group name conversion script will mitigate the overehad in doing that, so as far as I can see the value of this nice feature is not at the Must Have level. I did not state that this is Microsoft's fault. That is an invalid conclusion you drew. Sorry, but I am not guilty as charged on that one. We must question what new features really are important and what is not. For the Samba-Team, it is important to know what features to spend time on. We have limited resources. We are always happy to receive patches and to integrate them into the code tree if they make sense. At this time I am reluctant to ask one of our developers to take time away from other high priority work to add what in essence is a It would be nice to have feature. I totally agree that the features you describe would be really neat, but does it sense for the project as a whole? Not all of us cut code, I have spent the last year writing documentation. My objective is to document Samba and it's deployment to help users like you. I accept responsiblity for how I choose to use my time. Feedback we obtain does make its way into the documentation. We also use feedback to decide how best to improve Samba. We can not guarrantee to adopt every suggestion for code change. Cheers, John T. OK then. Thanks for taking note of my problem :) I do realise that time is scarce, and now that I understand the cause of the problem ( my distro ) I agree that it's best to let individuals battle with it. Sorry for being a typical whining user... Dan -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] access 2003 clients can't print to samba 3 server ( access 2000 can)
[EMAIL PROTECTED] wrote: Has anyone else heard of or had any issues printing with Access 2003 to samba servers? Other office 2003 products print fine, and Access 2000 worked, but Access 2003 will not print to a samba server here. In order to get access 2003 to print, I have to change default printer to something on a windows server, and then it works? That sounds more than a little suspicious. What sort of setup do you have? Samba == CUPS? Yes Raw print queue or the CUPS driver? Raw, w2k driver installed from print$ share. This is not a manufacturer's driver with all the bell's and whistles either, just simple default w2k minidriver. I have had some issues printing reports from Access to some of our printers that claim to be PCL6 compatible ( and have PCL6 drivers ), but only work with the PCL5 drivers. What happens when you try to print? Here's the latest. When I have some samba printers installed as the default printer, File... Print-Preview causes the window to momentarily flash light like it redrew itself, but that's it. File... Print (Ctrl-P) does not seem to do anything. No print property windows or anything. With Access 2000, everything worked. With the same printers on a windows server, File... Print-Preview causes the window (that previously just flashed light like a redraw) to display the preview in the same window. Print-Preview toggles back and forth between these views. File... Print (Ctrl-P) brings up a Print window, and here I can see the samba printers that didn't work if they were the default printer, select them, and print using them. But if those printers were previously the default printer, none of it works. Through trial and error, I've discovered that our HP LaserJet 4050 and 8100 on the samba server both fail if they are the default, but oddly enough a HP LaserJet IIISi on the same server works fine. If I install one of the same failing drivers (8100) as a local printer (even while keeping existing driver), print preview and other operations work fine. It's only when the samba printer is selected as the default printer that I have problems :(. ~ Daniel You're not going to like this, but I think it's a problem you should be taking up with M$. I can't imagine why the print preview operation would need to contact the print server. Our Access 2002 ( XP ) system works fine with: Samba-3.0.1 CUPS-1.1.20 ( raw print queues ) - HP 4050N - HP 4500N ( colour ) - Ricoh AP3200 - Ricoh AF2027 I've just tried copying one of our Access shells to my PC, creating a small local table, creating a report of the table, pulling the network cable out, and running the report, and it doesn't seem to have a problem doing a print preview for a network printer that is unavailable. Maybe Access 2003 is asking something new and M$-specific of the server? I'm suspicious that this is a) M$ being clever about not printing to a samba server b) Some other issue with Access 2003. Maybe if you were handy with a packet sniffer you could see what happens when Access 2003 wants to do a print preview. I know I'd have no idea what to do :) Sorry I can't be more help. I will keep this discussion in mind when considering our upgrade path... -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] access 2003 clients can't print to samba 3 server (access 2000 can)
[EMAIL PROTECTED] wrote: Has anyone else heard of or had any issues printing with Access 2003 to samba servers? Other office 2003 products print fine, and Access 2000 worked, but Access 2003 will not print to a samba server here. In order to get access 2003 to print, I have to change default printer to something on a windows server, and then it works? Anybody heard/seen anything? Thanks, ~ Daniel That sounds more than a little suspicious. What sort of setup do you have? Samba == CUPS? Raw print queue or the CUPS driver? I have had some issues printing reports from Access to some of our printers that claim to be PCL6 compatible ( and have PCL6 drivers ), but only work with the PCL5 drivers. What happens when you try to print? Dan -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Samba, CUPS A StarDocPrinter call was not issued.
Sundaram Ramasamy wrote: Hi all, I am using Samba -3.0.2a with cups on SuSe 9.0. Samba PDC works fine, but I have some problem with CUPS PDF Printer printing. From Linux I was able print the test page. From 2000 workstation I was able add and print the document as root user. If I login as ordinary user, not able to print anything (not even testing) I received the following errors: From NotePad: A StarDocPrinter call was not issued. From OpenOffice: Could not start printer. Please check your printer configuration Any tips to fix this problem. Note: Same setup and configuration works at my home. I was able to print the document from Windows 2000 Client. -Sundaram Maybe a permissions problem on the destination directory? -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] trustrelation ship
Aniruddh Singh wrote: hi i have successfully established trust relation ship with samba 3.x domain and NT4 with service pack 6 but when i try to logon into NT machine with user created in samba it says make sure your domain and user name is correct and when i try to logon into samba machine with user created in NT it says login failure can any body help me ? You need to add the user in the User Manager on the NT4 domain controller. -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] A few issues with samba cups
Hi all. I have Samba-3.0.1 sharing 2 printers via the 'share all printers' feature - the printers are an HP 4500 colour laser, and a Ricoh Aficio AP3200 ( accepting jobs like a network HP does ). I followed the instructions on the CUPS website for sharing printers with the CUPS windows driver, using their 'cupsaddsmb' script, which basically takes your existing ppd file, and adds a couple of dlls ( the cups driver bit ) and chucks them in the printer$ share for Windows clients to download when they connect. This all appeared to work flawlessly. I can right-click in the shared printers in the network neighbourhood and click 'connect' and the printer driver is downloaded. The first issue ( which is probably more of a CUPS issue than a Samba issue ) is that the margins are wrong. The margins are perfect via Linux. Margin settings are taken from the foomatic-generated ppd file, and I've checked them against the manufacturer-issued ones. I've also checked the Windows clients, and they are in fact using the same ppd file that gets downloaded upon connecting. So something is going wrong somewhere, and the left-hand margin is too big on both printers, and the top margin is too big on the HP 4500. If anyone know the the problem is, I'd be oh-so-grateful to hear from you :) The next issue is that I can't update the printer config now that it's set up. If I log into a Windows machine as root, samba will let me upload new drivers ( manufactured-issed ones to replace the CUPS Windows drivers ) to the printer$ share via the 'advanced' tab of the printer config dialog, when I click on 'apply' to select the uploaded driver, I get an error: 'Printer settings could not be saved. Access is denied'. The drivers are being uploaded to the printer$ share, and I can select them for use in a single print 'session' and everything works OK, but I can't make them the default drivers! One strange thing is that while I'm continually pressing on the 'apply' button, there is no logging being generated in /var/log/samba. So this looks like a permissions problem on the Windows client??? At any rate, it is preventing me from sharing the printers via samba, so if anyone knows what this issue is caused by, I'd also be very grateful to hear from you. Thanks! Dan smb.conf: # #=== Global Settings = [global] dns proxy = no load printers = yes netbios name = screamer printing = cups server string = Samba Server %v socket options = TCP_NODELAY password server = NUS_AUST_NT workgroup = NUSAUS debug level = 1 bind interfaces only = true interfaces = 10.146.0.254/255.255.0.0 null passwords = yes encrypt passwords = yes security = domain preferred master = no max log size = 50 use client driver = yes [install] writable = yes printable = no path = /mnt/stuff/smb_shares/install force directory mode = 777 force group = nobody force create mode = 777 comment = Installation Stuff create mode = 777 public = yes directory mode = 777 [htdocs] path = /var/www/localhost/htdocs writable = yes printable = no public = yes [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writeable = no printable = yes printer admin = root [print$] browseable = yes comment = Printer Drivers writeable = yes write list = root path = /etc/samba/drivers -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] net rpc vampire problems
[EMAIL PROTECTED] wrote: But if I user lowercase, it works. I wasn't aware of a restriction on creating uppercase usernames. Is this supposed to happen? Anyone else know why my machine accounts aren't getting migrated? Pretty please? Dan, What flavor of Linux are you using. I'm running Gentoo ( current ). I just did a migration using Samba 3.0 and RedHat ES 3.0. I ran into the same problem. That is because RedHat does not allow you to create user names with uppercase letters. I tried the script below. I had to edit out an extra '_' at the end of the sed bit. The command works great if I run it myself from a console, but when I point the add user script at it, I still get the same problem, but only about 50% of the time ... some accounts are getting created. However NONE of the machine accounts created let me log into the new domain from a PC that was already on the old network - I still get the 'this machine's account is missing or the password is wrong' error. Maybe someone can satisfy my curiosity here... WTF is supposed to be going on in the machine account creation? The adduser script is called ( which in my case doesn't work ). So say I have created these machine accounts by hand already. What's next? The password bit, right? Can I do this myself too? Where does the machine account's password go ... in /etc/shadow? Can I get it from somewhere and add it myself? On a side note, the not-being-able-to-create-uppercase-usernames issues needs to be fixed... Anyway, thanks to those that have helped so far. The other problem I had was with group names. The way I got around it was to write my own scripts that change the machine name from upper to lower case. I put the reference in the smb.conf: add machine script = xx.sh This is the script:** #!/bin/sh # Script to add machines # Checks to see if a command line argument was passwd if [ $# -eq 0 ] then echo . echo Did not pass an argument on the command line echo usage: conv.sh \THIS is a TEST\ echo . exit 0 fi # Passes the command line argument. Reduces the string length and converts to lower case lower=`echo $1 | sed y/[ABCDEFGHIJKLMNOPQRSTUVWXYZ\ ]/[abcdefghijklmnopqrstuvwxyz\_]/` #This is the section in which you call the useradd and pass the Unix compliant name /usr/sbin/useradd -g machines -s /sbin/nologin -d /dev/null $lower exit 0 It doesn't make any difference if I run the above script or not. The creation of the machine trust account still fails. Interestingly, if I run manually: useradd DKASAK$ I get the error: useradd: invalid user name 'DKASAK$' But if I user lowercase, it works. I wasn't aware of a restriction on creating uppercase usernames. Is this supposed to happen? Anyone else know why my machine accounts aren't getting migrated? Pretty please? Dan -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Failing to store a SAM_ACCOUNT for [root] without a primary group RID
OK. I've given up on using the 'net vampire' feature to suck our NT4 info. Now I want to start afresh. I've set the smb.conf file up, and run the script I found in the HTML docs to map common Windows Domain groups to unix groups. This worked OK. Now I want to create a root account so I can actually join the domain from a Windows 2000 client. When I run: /usr/local/samba/bin/smbpasswd -a root and enter the password I get: tdb_update_sam: Failing to store a SAM_ACCOUNT for [root] without a primary group RID I never used to get this under older ( 3.0+ ) versions. Something changed? Dan -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] net rpc vampire problems
Hi all.
I'm trying to migrate our NT4 domain to Samba-3.0.1-rc3.
My smb.conf:
[global]
netbios name = vp
workgroup = NUSAUS
server string = Samba Server %v
bind interfaces only = true
#interfaces = 192.168.0.1/24
interfaces = 10.146.1.100/24
passdb backend = tdbsam
log level = 5
log file = /var/log/samba3/log.%m
max log size = 50
name resolve order = wins lmhosts bcast
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = cups
add user script = /usr/sbin/useradd -s /bin/false '%u'
delete user script = /usr/sbin/userdel '%s'
add group script = /usr/sbin/groupadd %g getent group '%g'|awk
-F: '{print $3}'
delete group script = /usr/sbin/groupdel '%g'
add user to group script = /usr/bin/gpasswd -a '%u' '%g'
delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
set primary group script = /usr/sbin/usermod -g '%g' '%u'
domain logons = Yes
os level = 33
preferred master = Yes
domain master = No
wins support = Yes
printer admin = @adm
printing = cups
preserve case = No
logon drive =
logon home =
logon script = drives.bat
[netlogon]
comment = Network Logon Service
I can join the domain ( as long as I specify the IP address with the -I
flag ).
When I run the 'vampire' command, I get the following errors for each
machine / user:
Creating account: DKASAK$
Could not create posix account info for 'DKASAK$'
Creating account: dkasak
[2003/12/15 13:44:00, 0] utils/net_rpc_samsync.c:fetch_account_info(497)
Could not find unix group 4294967295 for user dkasak (group
SID=S-1-5-21-667748849-896033114-1233803906-513)
Each user already has an account set up on the computer ( I'm already
running a mail server ), but the machine trust account creation
shouldn't be failing.
The users are imported into samba, and I can see them with 'pdbedit -L',
however when I move the samba server a test PC off onto another
network ( and set 'Domain Master' to 'Yes' and change the 'interfaces'
line ) and try to log on to the domain, I get an error that the machine
trust account doesn't exist, or the password for the account is incorrect.
The trust account doesn't seem to be created at all. Any idea why?
--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: [EMAIL PROTECTED]
website: http://www.nusconsulting.com.au
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] 'Account disabled due to email bouncing' madness
We have a mail filter ( CanIt, by Roaring Penguin, see http://www.roaringpenguin.com ) that is doing a very good job indeed of blocking spam and viruses. And I certainly get a lot from this list ... so much that without the use of CanIt, I would have already had to retire my email address, and possibly even our entire domain, to avoid the constant march of crap. But ... the list server keeps locking my account, because messages are bouncing. That's how CanIt works - it bounces spam and viruses. So, I'd either like: 1) The virus and spam problem solved permanently ;) or 2) The rules on the list server relaxed a little so I don't have to keep re-activating my account. Dan -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cannot locate roaming profile
Hi all.
I've just installed samba-3.0.1-rc1 as a PDC and I can add computers (
win2k ) to the domain, but when users log on, they get an error:
... windows cannot locate your roaming profile ...
or words to that effect.
My smb.conf is:
# Global parameters
[global]
workgroup = NUS
server string = Samba Server %v
bind interfaces only = true
interfaces = 192.168.0.10/24
passdb backend = tdbsam
pam password change = Yes
unix password sync = Yes
log level = 3
log file = /var/log/samba3/log.%m
max log size = 50
name resolve order = wins lmhosts bcast
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = cups
add user script = /usr/sbin/useradd -s /bin/false '%u'
delete user script = /usr/sbin/userdel '%s'
add group script = /usr/sbin/groupadd %g getent group
'%g'|awk -F: '{print $3}'
delete group script = /usr/sbin/groupdel '%g'
add user to group script = /usr/bin/gpasswd -a '%u' '%g'
delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
set primary group script = /usr/sbin/usermod -g '%g' '%u'
domain logons = Yes
os level = 33
preferred master = Yes
domain master = Yes
wins support = Yes
printer admin = @adm
printing = cups
preserve case = No
[homes]
comment = Home Directories
read only = No
browseable = No
[netlogon]
comment = Network Logon Service
path = /usr/local/smb_shares/netlogon
guest ok = Yes
I've read the docs that state that it is not recommended to use roaming
profiles, and I agree. How do I stop windows from trying to locate one?
Thanks!
Dan
--
Daniel Kasak
IT Developer
* NUS Consulting Group*
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: [EMAIL PROTECTED]
website: http://www.nusconsulting.com.au
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Migrating a samba setup to another server
Hi all. We're doing a major network upgrade, and I'm considering setting up Samba-3 as a PDC. The computer I want to install it onto already has Samba-2 running ( just a member of an NT4 domain ), and I *need* to keep it up 24/7 until I finish the upgrade. Therefore, I'd like to do the install on a temporary system, set up the PCs in the new domain, and then migrate everything to the real server. I'd like to use Gentoo's portage to do the compilation. It gives me the directories: /etc/samba /var/lib/samba as well as the binaries of course. If I set up all the computers into the Samba-3 domain on the temporary sytem, can I just compile samba on the other computer ( also Gentoo ), copy the /etc/samba and /var/lib/samba directories, and then copy the entries from /etc/passwd onto the real server? Is there an easier way to migrate the setup? Thanks in advance! Dan -- Daniel Kasak IT Developer * NUS Consulting Group* Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
