[Samba] Net command address resolution

[Martin Thomas]

Running samba3.4.3, I notice the net command has address resolution problems but
not for all sub-commands.

Bad:
bin/net -s /home/martin/smb.conf  -I172.21.0.156 -Ulab/dev%dev rpc share list
Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED)

Good:
bin/net -s /home/martin/smb.conf  -I172.21.0.156 -Ulab/dev%dev rpc group
None
boinc_admins
boinc_projects
boinc_users
Debugger Users
...


If I repeat the first command after changing -I (explicit IP address) to -S
(servername) then I get success:

bin/net -s /home/martin/smb.conf  -S172.21.0.156 -Ulab/dev%dev rpc share list
IPC$
D$
ADMIN$
H$
C$


Should I go ahead and submit a bug?

Thanks // Martin



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

RE:[Samba] Question on Samba 2.2.1a

[Martin Thomas]

>Message: 23
>Date: Mon, 18 Aug 2003 09:24:59 +0200
>From: "Jurzitza, Dieter" <[EMAIL PROTECTED]>
>Subject: [Samba] Question on Samba 2.2.1a
>To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>Message-ID:
><[EMAIL PROTECTED]>
>Content-Type: text/plain; charset="iso-8859-1"
>
>Dear listmembers,
>we have a medium size network (~50 people) using samba for mainly fileserver
>purposes on a Sparc linux (SuSE linux 7.3, kernel 2.4.20) system.
>Every other time people face difficulties when copying files from the Novell
>or Windows network onto the samba shares. Let's say you want to copy a file
>called "dummy.doc" onto the samba drive. Then a file with that name is
>created at the target location, having 0 bytes. Then you are told (i. e. by
>explorer) that the file already exists (even though it did not before) and
>you are asked whether or not you would like to overwrite. If you say yes
>(overwrite), an errormessage appears that says that the file cannot be
>overwritten.
>You can delete the 0 - byte file a hundred times, you can check permissions,
>everything seems to be correct - apart from not being able to copy really.
>Anybody out there having an idea how to fix this? I do not have a clue what
>could cause the trouble.
>Many many thanks for your efforts in advance,
>take care
>
>
>
>Dieter Jurzitza

If I remember this correctly, there where some problems with file
creation and overwriting/replacement in older versions of the 
Samba 2.2 branch. You could try to reproduce this problem
with Samba 2.2.8a. There are SuSE rpms of Samba 2.2.8a
for SuSE 7.3 on the SuSE ftp-server. I never looked for a
Sparc package but i386 is availabe. There is an instruction to 
build a rpm for SuSE somewhere in the packageing tree of 
the Samba source disrtibution.

Did you check the log-files - any "strange" entries?
Is enough space left on the destination disk?

Hope this helps, good luck
Martin


---
Martin THOMAS
University of Kaiserslautern, Institute of Environmental Engineering,
Kaiserslautern (ZIP 67663), Germany


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] logon script won't start anymore after update 2.2.3a

[Martin Thomas]

>Message: 26
>Date: Mon, 18 Aug 2003 10:18:24 +0200
>From: Carsten Springenberg <[EMAIL PROTECTED]>
>Subject: [Samba] logon script won't start anymore after update 2.2.3a
>-> 2.2.8.a
>To: [EMAIL PROTECTED]
>Message-ID: <[EMAIL PROTECTED]>
>Content-Type: text/plain; charset=us-ascii; format=flowed

>Dear list,
>
>last friday I had a frustrating experience during the update of my samba 
>server. I've been running samba since 1998, now there are 50 users with 
>win2k-boxes attached - the samba server acting as PDC. Becauce of a swap 
>of the old server I finally decided to update to 2.2.8a. What I did (in 
>general):

>- installed the new server with suse 8.2 prof
>- Installed the suse-rpms for 2.2.8a on the new server.
>- shut down smdb/nmdb on the old server and changed ip and name
>- copied smb.conf, smbpasswd, secrets.tdb to the new server
>- added all the unix users
>- changed ip and name on the new server to the values of the old server
>- started smdb/nmdb on the new server
>
>Everything seemed to work. I could logon and got my samba-shares - but 
>as I found out I got my samba-shares because they have been mapped 
>previously and not because of my logon script. Further experiments 
>brought up that the logon scripts didn't run at all at logon-time.
>
>I tried a lot concerning "logon script" (%u instead %U, changed it to a 
>f. e. to "logon.bat") but without success. The logon script just sets 
>the time and maps the shars. The [netlogon]-share doesn't seem to be the 
>problem either. I read all in the archives concerning this point (and 
>also googled) but couldn't find something usefull.
>
>I am not that new to samba but am at a loss anyway.
>
>So I reversed the changes and fired up my old samba server and am 
>looking for ideas now.

>...

It seems that you forgot the transfer the Machine and Domain SID to
the new configuration. The domain logon does not work correctly
if the Server SID is not the one that is cached in the clients registry
during domain join.

There are several possibilities:
* use smbpasswd to get the SIDs from a running Domain controller,
  see the documentation of smbpasswd, the options where added
  in 2.2.8 (or 2.2.7). Although this is the recommended method it did not 
  work for me,  I could transfer the Domain SID with smbpasswd but 
  somehow the Machine-SID seems to be importat to but did not
  transfer correctly
* get the SID from the file MACHINE.SID (only available in older
  Samba versions, I think your 2.2.3a used this file) on your old server, 
  transfer the SID to the new server and  import the SID using smbpasswd.
* since you used an "old" Samba the SID should be in the file MACHINE.SID,
  copy this file to your new box in the directory where secrets.tbd
  is located, stop Samba, move the file secrets.tdb away (backup),
  restart Samba. On startup Samba can not find secrets.tbd which
  you moved away and should look for the file MACHINE.SID,
  import its contents (the SID) into a newly created secrets.tdb and
  delete MACHINE.SID (I'm not shure but you can grep the
  Samba source code for MACHINE.SID and see how this is
  implemented)
* The method that worked me, since I already had a secrets.tdb
  on the old server:
  - copy the file secrets.tdb on your new server to another directory
  - stop Samba
  - replace the file secrets.tdb on your new machine with the
file secrets.tdb from your old server (the SIDs are in this file)
  - start Samba

Another reason for your problem might be that the the startup scripts 
are not accessable for the user that logs in.

Hope this helps, good luck
Martin


---
Martin THOMAS
University of Kaiserslautern, Institute of Environmental Engineering,
Kaiserslautern (ZIP 67663), Germany
 

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re:Replacing Samba PDC with new hardware

[Martin Thomas]

>From: "Alex" <[EMAIL PROTECTED]>
>Subject: [Samba] Replacing Samba PDC with new hardware
>To: "SambaList" <[EMAIL PROTECTED]>
>
>Hi,
>I'm currently running a Samba PDC (2.2.3a) on RedHat 7.3 supporting 10 or so
>win2k users with roaming profiles.  Just got a new Dell box and would like
>to replace the current PDC machine.  My question is this :
>
>What is the best way to make the switch without making the current user
>accounts obsolete.  I've duplicated the most of the environment already, my
>users accounts have already been added to /etc/passwd, /etc/group.  I set up
>smb.conf, the homes and netlogon share. I copied the logon.bat file I've
>been using from the old box, and added all my users and machine accounts to
>the smbpasswd file as usual.  Now as far as the SID I'm a little fuzzy.  I
>would ideally like the replacement server to have the same netbios name
>(SERVER) as the de-commissioned machine.  For the moment I 've given the new
>box the name (NEW_SERVER) so that I can copy files over.  I ran smbpasswd -S
>(domain) to suck the SID to the new server already.  Now when I shut down
>the old box for good, and change the netbios name will the SID for the
>domain be re-written making my user accounts useless/ unable to logon?  Is
>there any way to avoid this?  Also is there a "better" way to move the users
>home directories to new box? I was planning on tar-ing up the /home dir and
>just expanding it on the new machine?  Does anyone know if I have all the
>users logged in, swap out the servers, and log the users out will that send
>the profile back to the home directory on the new server?

Try to replace the secrets.tdb on the new PDC with the one from the old
PDC. I had some trouble too, the domain SID can be extracted from
the old machines secrets.tdb and set one the new one with smbpasswd, but it 
seems that the server-SID is important too. The output of 
smbpasswd -X  and smbpasswd -X  was 
different on my new installation and identical on the old PDC. I did not find a 
way to set the Server SID using smbpasswd. After overwriting
the secrets.tdb on the new server with the one from the old PDC the client-
login worked without rejoining. Make shure that the password in the smbpasswd-file
for users and machines are the same as one the old server. If you keep the same uids 
for machines and users one the new server as they where on the old one just copy 
smbpasswd or edit the uids in the copied smbpasswd-file to match those in 
/etc/passwd on your new PDC. If you have a file MACHINE.SID copy this 
file too (some older versions of Samba used this file but its now obsolete, 
the data is now in secrets.tdb).
Hope this helps
--
Martin Thomas
University of Kaiserslautern, Institute of Environmental Engineering,
Kaiserslautern (ZIP 67663), Germany


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: Starting a process from a windows client

[Martin Thomas]

>Date: Tue, 25 Feb 2003 11:23:34 -
>From: "Scattergood, Ivan" <[EMAIL PROTECTED]>
>To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>Subject: [Samba] Starting a process from a windows client 
>Message-ID: <[EMAIL PROTECTED]>
>Content-Type: text/plain
>MIME-Version: 1.0
>Precedence: list
>Message: 60
>
>I am hoping to run a Unix process from code running on a windows client, I
>am told this can be done using Samba, does any one have any example code to
>do this? 
>
>Regards 
>Ivan Scattergood 
>London  Software Development
>Internal 8-727-4929 (Lovat Lane)
>Internal 8-727-4756 (Cannon Street)
>External +44 (0) 20 7961 4929 
>Fax +44 (0) 20 7961 4860 
> 

The preexec option might help, for
example:

[procstrater]
path = /tmp
preexec = /usr/local/scripts/test.sh &
preexec close = yes   # ?
... other options (path etc.) ...

Now everytime a user accesses the procstrater share
the program gets startet with the users unix-access-rights
You may use root preexec = /...  and pass the Users
name as an option (root preexec = /test.sh %U).
Then the script is startet with root privileges (...warning...)
an the script can manage the user rights internaly with
the username passed in the command line.

I'm not sure about preexec close. If "test.sh"
returns a non-zero value the share gets closed according 
to the Samba-Documentation if this option is set.
This might prevent the share from staying open
and not executing preexec during the next connection
from the client. I never used the preexec close option.

Another option might be to "abuse" the print command,
for example:

[procstarter]
printable = yes
print command = /usr/local/scripts/test.sh &; rm %s
# or 
# print command = /usr/local/scripts/test.sh %s 
# print command = /usr/local/scripts/test.sh %U %s 
... other options (path etc.) ...

Now everytime a user "prints" something to the
procstarter-"printer" test.sh is startet with the users 
accessrights. You can set the script SUID root 
(...usual warnings about this) and can manage the 
access rights internaly by passing the users name with %U.
Don't forget to remove the print-file (%s), to clean up
Or even more "tricky" bind a postscipt-printer-driver or
"text-only-driver" to the print-share. You can parse the 
print-file (Name in %s) for input to your process (and 
remove it afterwards). 
I'm not sure about the syntax but "man smb.conf"
should help you.
Both "share-access" and "printing" can be done 
from within a Windows-programm, when this is
what you mean by "code running on the client".

There may be better methods than using Samba
to start/control processes an a server (rpc, rmi).

Martin





-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: logon script to adjust time on workstation

[Martin Thomas]

>Okay, I just found it.  For future reference, Go to: Start->Run->gpedit.msc
>
>Once the Group Policy editor opens, find:
>
>Computer Configuration -> Windows Settings -> Security Settings -> Local 
>Policies -> User Rights Assignments
>
>Then select the Policy "Change the System Time" and add Everyone to the 
>list.
>
>Thanks for the help Khanh.
>
>-Gabriel
>
>Khanh Tran wrote:
>
>>You'd have to set the policy for the "Everyone" group to change the time on
>>the workstation.  I don't remember exactly where it is in Win2k, but I know
>>it was possible in NT.
>>
>>Khanh Tran
>>Network Operations
>>Sarah Lawrence College
>>

You might also use the Windows-Time-Service. So you don't need to 
give "Everyone" the right to change the time.

- Install, config and start an ntpd on a server (e.g. your Samba-Server)
- login to the Workstation as Admin and set the "Windows-Time-Service"
to start "automatic" (Control-Panel-Configuration-Services)
- go to the windows-command-line and type: 
  net time /setsntp: 

With this setting you don't have to sync the time in the login-script,
it's done by the Windows-Service.

Martin


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: PDF Printer issue

[Martin Thomas]

: 
: Hello Everyone,
: 
: I have a slight issue with configuring a PDF printer on my Samba
: servers. I have input the following into my smb.conf file and it does
: create the printer as well as work to create PDF files, except that it
: only functions when "printing" to that printer via Excel 2002. If I
: attempt it with anything else, even the Windows Test print, it fails.
: 
: Now, in the Windows Printers folder, if I select the PDF printer
: the status box states that the printer is inactive and not ready.
: However, if I browse to the printer through the Windows Explorer Network
: Neighborhood, the printer shows up as active and ready.
: 
: I am unsure quite what the problem is, which means it is likely
: something very easy. There is one thing to note, I have not a single
: Linux Printing Subsystem running on the machine as this server is not
: being used for regular printing of any sort. 
: 
: Here is my smb.conf section:
: 
: 
: [purchpdf]
: comment = PDF Generator for Purchasing
: path = /var/spool/samba
: valid users = *UserNames Removed*
: write list = *UserNames Removed*
: printable = yes
: print command = gs -dNOPAUSE -dbatch -q -sDEVICE=pdfwrite
: -sOutputFile=/share/purchasing/pdf/%J.pdf <%J 1>/dev/null 2>&1; rm -f %J
: 
: Thanks for any assistance that can be rendered.
: 
: Regards,
: Robert Adkins II
: IT Manager/Buyer
: Impel Industries, Inc.
: 586-254-5800


Robert,

Do you serve the printer-drivers for the workstations from
you Samba-Server? - Of not, set "use client driver" to "yes" for the
"pruchpdf"-printershare (see man smb.conf for details). Consider
serving the driver from Samba (upload it and don't use the 
client driver option, see the howto-collection.pdf).
Here we use the driver "Apple Color Laserwriter 12/600"
served from Samba to Windows 2000(sp2,sp3) clients without
problems.

I also had to override the lpq-command. Try to set 
"lpq command = /var/samba/lpqdummy.txt" Where lpqdummy.txt 
only has one line with the text "no entries". Windows now always 
shows "ready".

Take a look into the Mandrake-packaging-dir in the Samba distribution.
(or http://cvs.samba.org/cgi-bin/cvsweb/samba/packaging/Mandrake )
Using their method (see smb.conf and samba-print-pdf.sh) works
better than directly calling gs with "print command". I had some
blocking issues with the direct call and large documents before using
this method.

Martin





-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Re: New Debian Packages?

[Martin Thomas]

: > tried it a few minutes ago. apt-get update shows:
: > 
: looks good to me now too...
: > I'm using the german mirror. Perhaps you can try another one. 
: i just tried the us mirrors but 
: ncftp ftp://us2.samba.org/samba.org/Binary_Packages/Debian/
: says that those files don't exist...
: 
: maybe it's only on the german mirror?
: 
: > Perhaps Simo can give more information. The information should be
: > reliable before it will be submited to apt-get.org.
: I agree - Whomever set it up should submit it to apt-get.org.
: 

The directory structure is a little different. To use the mirror us2.samba.org the 
line in /etc/apt/sources.list should be:

deb ftp://us2.samba.org/pub/samba/Binary_Packages/Debian stable main

I did not test it with apt-get, but Samba 2.2.7a for "Debian stable" is there.

Martin



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Re: New Debian Packages?

[Martin Thomas]

: > You can try this: 
: > add the line
: > 
: > deb ftp://de.samba.org/samba.org/Binary_Packages/Debian/ stable main
: > 
: > to your /etc/apt/sources.list then apt-get update, apt-get dist-upgrade. 
: > This should update Samba to 2.2.7a.
: 
: this appears to be offline...
: 
: once it's working again it might be nice to submit it to www.apt-get.org
: 
: brad
: -- 
: Bradley W. Langhorst <[EMAIL PROTECTED]>
: 
: 

Brad,

tried it a few minutes ago. apt-get update shows:

...
Hit http://non-us.debian.org stable/non-US/non-free Release
Hit ftp://de.samba.org stable/main Packages
Get:2 ftp://de.samba.org stable/main Release
Hit ftp://ftp.de.debian.org stable/main Packages
Ign ftp://de.samba.org stable/main Release
...

I don't know much about Debian but I got the same messages right before
updating 2.2.3 from the "standard" Debian stable to Version 2.2.7a published 
by the Samba-team on their mirrors. I don't know why the output shows 
"Get 2" and "Ign" for de.samba.org but it did work.
I'm using the german mirror. Perhaps you can try another one. 

# dpkg -s samba
shows: 

Package: samba
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 5820
Maintainer: Simo Sorce <[EMAIL PROTECTED]>
Version: 2.2.7a-0.1
...

Perhaps Simo can give more information. The information should be
reliable before it will be submited to apt-get.org.

Martin




-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: New Debian Packages?

[Martin Thomas]

> Hi there,
> does anyone know where I can get new samba packages for debian, because
> woody is at 2.2.3a-12 and this version has definitev a problem with
> Access 97 databases... *arg* And I'm not able to produce new debian
> packages myself.
>
> Any help is appreciated...
>
> Thanks
> Nicki
>
>

You can try this: 
add the line

deb ftp://de.samba.org/samba.org/Binary_Packages/Debian/ stable main

to your /etc/apt/sources.list then apt-get update, apt-get dist-upgrade. 
This should update Samba to 2.2.7a.

Martin



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] (no subject)

[Martin Thomas]

>From: [EMAIL PROTECTED] (TE)
>
>Bare with me as I am pretty new to Linux and everything that goes with it. My problem 
>consists
>of copying large files from my w2k client to my samba server. Files larger than ca 
>700 MB will,
>when moving ore copying to a samba share, stop in a error message that the network 
>path is no
>longer accessible. The â?oserverâ?, which samba is running on, starts to write to 
>the disk but
>there is no network activity and after a while the error message appears. I have 
>looked through
>all the forums and so on to see if I could find an answer, but no. I have however 
>found other
>users posting messages about the same problem, but never an answer that solved the 
>problem.
>Is there anyone who knows how to solve this problem?

Is the error message "network path is longer accessible" or "the network path is no 
longer
available"? If it's "no longer available" try this:
Check your Network, maybe dulpex-mode or transfer-rate are not correctly 
autonegotiated.
Try to set those to a fixed value for a client and the server and every managable 
device
(switch) between them.
Try to replace the network-interface-cards (NICs) in the server and the your 
test-client. Try
different hubs/switchs or use a crossover-cable to connect server and client directly 
if possible.

I'm one of those "other users" who posted about this problem. Later we found a wrong
transfer-speed setting in one of the managable switches. I had contact with around 10 
others
during the last year who had the same error message. All of them who wrote feedback had
bad network-hardware or wrong network-settings. I dont' think that this is a Samba 
problem.

Martin



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

RE: [Samba] Anyone using antivirus software?

[Martin Thomas]

>Hello list,
>   I was just wondering if anyone is using anti-virus software on
>their Samba server. I have protection on my clients, but I want to run
>software on the server too. I've looked at McAfee's Virus Scan, but as
>far as I can tell, it only uses "on-demand" scanning, meaning I have to
>trigger it from the command line, or run a cron job. I would like to have
>something that is real-time, and detects an infected immediately, without
>my interaction. This is how the McAfee AV software works on the client
>PC's running Windows. Anyone know of a similar product?

Take a look at http://sourceforge.net/projects/openantivirus/.
Subprojekt: samba-vscan.

Hope this helps
Martin




-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba-Docu. suggestion

[Martin Thomas]

Suggestion for an addition to the Samba-Documentation:

Some people (10?) mailed me about a message I've sent to
the list back in the 2.2.1 days. My problems where 
not caused by Samba but it seems that profile-handling
for W2k clients with a samba server reveals network
problems (hardware or router/switch settings) which
are never noticed with *nix alone (reports came from 
Linux, HPUX and AIX users). I suggested to check
the network and at least 6 people found broken
NICs, Switches or wrong router configurations.
http://lists.samba.org/pipermail/samba-technical/2001-July/030366.html

Suggestion: "If you see error messages like
'The specified network name is no longer available' or 'error during transfer
of a memory page' check your network-hardware and settings"

I don't know the right translations, in german the messages are:
"Der Netzwerkname is nicht laenger verfuegbar" and
"Fehler beim Einlagern einer Speicherseite"


- Martin



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] RE: printer admin problems with 2.2.4

[Martin Thomas]

>We upgraded from 2.2.3a to 2.2.4 on a SuSE 7.2 server. We compiled Samba just 
>default. The new version seems to work ok with the exception of printer 
>administration.
>
>Printer admins are not able to see the properties of the printers (right click on 
>printer 
>gives on error). Our workstations are W2k SP2. But users that are not printer admin 
>are able to see the properties of a printer, but they are not allowed to change the 
>settings or to upload drivers. I don't think it is important, but we use the latest 
>lprng-
>version as printserver. 
>
>*   We tried the patch on the file rpc_parse/parse_spoolss.c
>*   We tried the current CVS version
>*   We installed the whole samba from scratch (new tdb-files)
>All no difference.
>
>With a lot of debugging on we can't see what is the problem. 
>
>Any ideas? 
>
>Met vriendelijke groet/Regards,
>Prompt
>R.J. Baart

Had the same problems here too. It seems that Windows 2K stores 
a lot of  information about the printers in the registry (~=user-profile). 
Esp. if the printers where connected via local ports and with local drivers
before, this seems to be stored in the registry and is not always removed if the
printer gets disconnected/removed. Try to find you printer-names in the registry and
delete entries around it (...registry, hacking, backup, warning etc.etc.). 
You may also clean up /winnt/system32/spool/drivers.

Perhaps you can just take another W2K client (clean installation) and fire
the Server APW from there and use a 'clean' clients to test it.

With one Printer (a HP Deskjet 1120 connected via a JetDirect 300x Box,
served via 'latest' LPRNG and Samba 2.2.4 using the W2K standard drivers
from /winnt/inf/ntprint.inf) I had exactly the same problem that you've 
described. The printer properties could be edited by a print-admin as 
long as none of the clients was connected to the samba-queue.
It seems to work now after heavy registry-editing, client file-removal,
new tdb and latest CVS-Code (but with only two clients connected so far).

Please send me your findings, I'm fighting with this problem too and
would like to have more information on it.

"cheers", 
Martin





-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] 2.2.4/spools/HP DJ 1120 driver problem

[Martin Thomas]

Gerald, Thomas, List-Members

>> mt:
>> I suppose Gerald Carter and the other maintainers of the printing-code
>> use postscript-printers for the testing. But the HP Deskjet 1120 has no
>> build-in postscript interpreter. Its just the 'bigger brother' in the DJ
>> 8xx-series of printers that can handle A3 papersize. It's not the newest
>> machine but the quality is still good enough. So

>gc:
>I test with PCL and PS drivers.  It's just that PS are generally 
>smaller and better behaved.

I had success with PCL Drivers for a HP Laserjet 4 (without Postscript).
But with the DJ1120 PCL Drivers it won't work. Perhaps my setup is not
o.k. put since all other printer-drivers work I don't think so.

Gerald, if you have some time: download the HP Deskjet 1120 Driver for
Windows 2000 from your employers Web-Server and try to upload
it to a Samba 2.2.4 box via APW. You may see some difficulities (at least I did).
I've used the Drivers from the W2K-CD giving /winnt/inf/ntprint.inf when asked
for 'have disk', which uploaded without error message.
Than 'bind' the printer to a W2k Client and try to view the properties on the client
or in the Servers APW - as soon as one client was connected to the printer
the properties-Dialog failed. Printing did not work either (most of the time).

: >ts: 
: > how to remove a serverdriver without dropping all $LOCKDIR/nt*.tdb?

:gc: 
: Connect as a printer admin to the samba box froma Win2k client 
: and browse through the network neighboprhood to the Printers 
: folder on the Samba server.  Then goto File->Server Properties
: and select the "Drivers" tab in the dialog window that appears.
: 
Does not work here, not for 'root' or other printer admins.
The button [remove] is disabled. I can detach the driver from the printer
be selecting 'delete' from the drivers context-menu. But rpcclient
enumdrivers still lists [HP DeskJet 1120C] deldriver "HP Deskjet 1120C"
failed while deldriver "HP DeskJet 1120C Printer" succeded. Deskjet 1120C
is still listet. enumprinters does not show the driver after deleting it from
the context menu.

Suggestions?

Martin


---
Martin THOMAS
University of Kaiserslautern, Institute of Environmental Engineering,
Kaiserslautern (ZIP 67663), Germany


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] 2.2.4/spools/HP DJ 1120 driver problem

[Martin Thomas]

: 
: Hello Samba-Team and List-Members,
: i had a similar problem with an hp deskjet 2500cm printer.
: 
: the 2500 series printer driver get uploaded, i can connect, but when
: printing: nothing happens on the samba and cups server.
: 
: after changing the printer driver to 2500 pcl5e driver. i was able to
: print. but the quality was pretty poor.
: 
: after installing the 2500postscript driver, we was able to print, beside
: it took about 5min, until the printer began to work. but the ps driver
: wont work on w2k only on win nt?

Thanks for your answer.

I have not seen any problems with the Printer-Drivers from Postscript
Printers. Even with W2K Samba-managed Postscript-based drivers work.
I do not have any NT-clients here.

I suppose Gerald Carter and the other maintainers of the printing-code
use postscript-printers for the testing. But the HP Deskjet 1120 has 
no build-in postscript interpreter. Its just the 'bigger brother' in the
DJ 8xx-series of printers that can handle A3 papersize. It's not the
newest machine but the quality is still good enough. So 

There is 
(a) Problem/error in the Samba-Code with this Driver (and probably all
  drivers of this series of HP printers)
or
(b) the Drivers can not be used as 'server based' drivers. Perhaps someone
  can test them with a W2K-Server (don't have one here)

'use client driver = yes' works as expected but is just a 'workaround'

Again, thank you.
Martin



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] 2.2.4/spools/HP DJ 1120 driver problem

[Martin Thomas]

Hello Samba-Team and List-Members,

Having the new Samba 2.2.4 installed I tried to upload
all printer drivers for Windows 2000 to the server.
For most of the printers (16) everything seems to work
(after hacking some inf-files for older Texas-Instruments
Postscript printers).

With a HP Deskjet 1120 there are still problems. What I've done
so far:

(1) added a print share for the DJ 1120 in smb.conf
(2) installed driver locally on a W2k client for testing
(3) printed a testpage - everything ok

(4) uploaded the printer-driver from the Windows 2000
  Server CD to the server (the printer driver from the
  HP-Web-Site could not be uploaded because of one
  file - ecp*.sys? -> PROBLEM)
(5) tried to change the printer properties in the Server APW, 
  changes are persistent - well
(6) connected a W2k SP2 client to the printer via the
  local Add-Printer-Wizard and printed a testpage -> o.k.

(7) tried to view the printer properties on the client 
  results in a message-box saying: "The printer properties 
  can not be showed. The procedure could not be finished"
  (translated from german) -> ERROR
  I'm member of the printer admin group and the upload
  worked - so this might not be an access-rights problem.
(8) tried to view the printer properties in the servers
  APW and got the same message box -> ERROR
(9) detached the printer from all clients 
(10) went to the Servers APW and tried to show
  the printer properties. This works on _some_ clients
  on another client the message box 
  "...properties can not be showed..." comes up
  again -> ERROR
(11) reattached the printer to some clients, again
  no access to the properties on _all_ clients and
  the APW for the Samba server

There seems to be some kind of locking with this
driver that is not noticed with other drivers (mostly
HP Laserjets und Xerox/Tektronix Phasers using Postscript 
Drivers). With this locking printer-admins loose control
over the printe since properties can not be viewed/changed
as long as there is a clients attached - and there will always be
some clients attached because the printer is "mounted"
through the startup-script. And even worse, applications
which use the properties wont be able to read them and might
reject printing to this printer, although MS Word 97 seems to
work with the DJ 1120, one can change the paper size.

Any solution for this, beside of 'use client driver'?
I can send level 10 logs if someone is interested.

Thanks, 
Martin
---
Martin THOMAS
University of Kaiserslautern, Institute of Environmental Engineering,






-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] 2.2.4pre/cvs kills PDC SID - still problems

[Martin Thomas]

Jerry,

Did a cvs checkout, 'make distclean' etc. At least for
the 3 larger test-profiles I do not see the error anymore.
I switched the main production server to 2.2.4pre now, so my
colleagues will do some "testing" tomorrow morning.
I will send you an e-mail if there are still problems.


Before the release of 2.2.4: could you please add some
topics to the documentation - excuse me if this is
already mentioned, but I did not find it.

(a) some people (10?) asked me about a mail I've send to
the list back in the 2.2.1 days. My problems where 
not caused by Samba but it seems that profile-handling
for W2k clients with a samba server reveals network
problems (hardware or router/switch settings) which
are never noticed with *nix alone (reports came from 
Linux, HPUX and AIX users). I suggested to check
the network and at least 6 people found broken
NICs, Switches or wrong router configurations.
http://lists.samba.org/pipermail/samba-technical/2001-July/030366.html

Suggestion: "If you see error messages like
'network name is no longer available' or 'error during transfer
of a memory page' check your network-hardware and settings"
I don't know the right translations, in german the messages are:
"Der Netzwerkname is nicht laenger verfuegbar" and
"Fehler beim Einlagern einer Speicherseite"

(b) Is 'File- and Printsharing' required on the W2K clients?
I had strange errors here, Word 2000 crashed with data loss,
when my colleagues tried to print on a Samba-managed printer.
The smbd.log showed something like 'not listening for calling name'
as last line before the client crash. Printer Drivers are installed
locally, no drivers on the server, no 'use client driver' or
'disable spools support' in smb.conf. The document was
opened from a samba share, after the crash, the document
was completely broken, an the first characters where entries
that normally occur in log.smbd files.

Suggestion: "Be shure not to disable File- and Printsharing
on W2K clients or there is a risk of windows application crashes"

... ok, this is an exaggeration, but since File- and Printsharing
is enabled again, there where no more problems with 
applications here. But now the administrator (me) worries about
security. I would like to give you level 10 logs, but I can
not reproduce the error in a test-environment, and waiting
until a colleague has problems again would cause trouble.
I never had problems with Win9X clients although File- and
Printersharing is disabled on all of them. Since printer
handling is still 'old-style' with Win9X as far as I understand,
the reason might have been the new printer-code for W2K/NT.

(c) what is the right mask to "veto dot-files", 
"hide dot files" is ok, but some file-managing-tools have the
'show hidden files' option switched on by default.
This confused the 'non-unix' people and made
directory listings longer than necessary. I tried
veto files = .* which worked with versions before 2.2.2 (?)
but does not work anymore, maybe because "." and ".." are
handled different since then.
[homes]
veto files =/.enl*/.x*/.X*/.s*/.n*/.m*/.k*/.h*/.g*/.z*/.w*/.u*/.s*/.p*/.b*/[...]
...
works but is "ugly".

Suggestion: "To completely hide dot files form the windows
users add ??? to you smb.conf. Clients will not see this
files although options like 'show hidden files' in the gui
or 'dir /ah' in the shell are used"

(d) Is there any influence between 'nt acl support' in the profile 
share and the locally cached profiles. Will a profile that
was downloaded form the Samba-server with acl support
enabled be synced if the acl support is disabled lateron and
vice versa. Is it recommended to delete all cached profiles
after changing the acl support option? I switched off
acl-support during the tests, can I go back to default
(on) without problems. Profiles are stored on the 
samba-machine not on a NT-Server.


Good luck for the release.
Thanks to you and the team for the great work.

Martin


- Original Message - 
From: "Gerald Carter" <[EMAIL PROTECTED]>
To: "Martin Thomas" <[EMAIL PROTECTED]>
Cc: "Jeremy Allison" <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Sent: Thursday, April 25, 2002 8:57 PM
Subject: Re: [Samba] 2.2.4pre/cvs kills PDC SID - still problems


: On Mon, 8 Apr 2002, Martin Thomas wrote:
: 
: > Just did a CVS update and tried the new code. It seems that the pdc-sid
: > is now handled correctly, login and login-script work, Loginserver is
: > the samba-PDC. But profiles can not be downloaded - Errormessage on the
: > W2Ksp2-client is something like 'Network name no longer existing'.  
: > 2.2.3a works, 2.2.4-CVS not. Did not change anything else t

Re: [Samba] 2.2.4pre/cvs kills PDC SID - still problems

[Martin Thomas]

: On Fri, Mar 22, 2002 at 07:21:21PM +0100, Martin Thomas wrote:
: > Hello,
: > 
: > just tried Samba 2.2.4pre (checkout 22.March 02, around 17:00 CET) 
: > from the cvs and could track down many problems we had here 
: > today to some error with the PDC SID (ok, I know, using cvs-code on
: > a production server is bad)
: > 
: > The CVS code seems to add the PDC SID from MACHINE.SID
: > to the secrets.tdb and after this deletes the file MACHINE.SID.
: > During this procedure the 'right' SID gets lost. One can see
: > this during login of a Windows 2000 client into a Samba 2.2.4-pre
: > managed domain: the profile download stops with 'access denied' and
: > the login-script does not run.
: > Doing echo %LOGONSERVER% from the Windows command shell 
: > gives the name of the client machine, not the PDC.
: > 
: > After deleting the locally cached profiles and setting nt acl support = no
: > in the smb.conf for the profile share the login works and the profile
: > downloads - but still no logon-script.
: > 
: > Did an installation of 2.2.4-pre/cvs on another Server, created another
: > domain, and rejoined one client to this new domain - this works
: > perfect, so it seems that only the SID-transfer ist broken.
: > 
: > I reinstalled 2.2.3a from the source-tar archive and restored the MACHINE.SID
: > from the backup. After this login, profile dowload and login-scripts
: > work. echo %LOGONSERVER% gives the netbios-name of the
: > Samba-Server - but now I lost the CVS improvements of the printing-subsystem 
: > and the MS-Database locking.
: > 
: > Since it will be quite a lot of work to rejoin all clients to a Samba 2.2.4-release
: > controlled domain, someone should fix this issue before release.
: > - I'm willing to test the cvs-code - just drop me a mail if something changed.
: 
: This was just fixed by a patch gone into CVS.
: 
: CVS update and it should be fine. Sorry for the problem.
: 
: Jeremy.
: 

Just did a CVS update and tried the new code. It seems that the pdc-sid is
now handled correctly, login and login-script work, Loginserver is
the samba-PDC. But profiles can not be downloaded - Errormessage 
on the W2Ksp2-client is something like 'Network name no longer existing'. 
2.2.3a works, 2.2.4-CVS not. Did not change anything else than restoring
the old MACHINE.SID and a 'make revert'.
I can give more information, later this week, don't have
the time for further analyses right now.
Thanks for the fix, but somethink still is wrong with the CVS-code
(or my configuration - any changes needed in the smb.conf for 2.2.4?).

Martin






-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba