RE: [Samba] 2.2.7a logon script will not run
Rich Forman schrieb: I just tried upgrading from 2.2.3 to 2.2.7a on my PDC (2.2.17 kernel). The logon script that I have been using all along without any problems quits executing w/ 2.2.7a. I can manually map the netlogon share after logging in and manually run the script and everything work fine. No error messages have u checked, if the directory /usr/local/samba/netlogon has the 'x' (1) flag set in all hierachies. i had the same problema (as i posted before a view month's) - and that was the solution. The permissions on /usr/local/samba/netlogon/* are 777. sorry, - i did read your first mail again. seeme i was sleeping yesterday - u told, that u have access... u did upgrade? - maybe, the machine account went away? did u try to re-join a machine to the domain? Yes, I did upgrade w/ the tar file doing: ./configure make make install Afterwords, I booted my W2K client machine and logged on to the domain. The logon script doesn't run, but otherwise everything is fine. From the client, I can map drives manually, access files, etc. all without errors. It authenticates the user name and password throught the pdc and there aren't any error messages at all either in the server logs or the client event viewer. I put everything back w/ 'make revert' and all runs fine again w/ 2.2.3, including the logon script. I saw some previous posts on this subject, but the problem seemed to be using a %u variable in the name of the script. That isn't the case w/ me, the file is just logon.bat for everybody. Maybe one of these evenings I'll try again w/ log level 10 and try to diagnose w/ that. -- 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.7a logon script will not run
-Original Message- From: Kurt Weiss [mailto:[EMAIL PROTECTED] Sent: Sunday, February 23, 2003 11:29 PM To: Rich Forman Subject: Re: [Samba] 2.2.7a logon script will not run Rich Forman schrieb: I just tried upgrading from 2.2.3 to 2.2.7a on my PDC (2.2.17 kernel). The logon script that I have been using all along without any problems quits executing w/ 2.2.7a. I can manually map the netlogon share after logging in and manually run the script and everything work fine. No error messages have u checked, if the directory /usr/local/samba/netlogon has the 'x' (1) flag set in all hierachies. i had the same problema (as i posted before a view month's) - and that was the solution. The permissions on /usr/local/samba/netlogon/* are 777. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] 2.2.7a logon script will not run
I just tried upgrading from 2.2.3 to 2.2.7a on my PDC (2.2.17 kernel). The logon script that I have been using all along without any problems quits executing w/ 2.2.7a. I can manually map the netlogon share after logging in and manually run the script and everything work fine. No error messages appear in the log files. My smb.conf file is included. Don't know quite where to go with this one. Any suggestion would help. All client machines are NT4 or W2K. Thanks in advance. [global] #Server Parameters netbios name = SERVER server string = Samba %v #Domain Parameters workgroup = GRAY1 encrypt passwords = yes domain logons = yes os level = 65 preferred master = true domain master = true guest ok = yes domain admin group = @adm # domain admin users = rich andy add user script = /usr/sbin/adduser -n -g machines -c NTMachine -d /dev/null -s /bin/false %m$ time server = yes # Set to use local profiles logon script = scripts\logon.bat logon home = logon drive = logon path = # Name Server Support wins support = yes name resolve order = wins hosts lmhosts bcast # Security Options security = user bind interfaces only = yes interfaces = 192.168.100.1/255.255.255.0 127.0.0.1 hosts allow = 192.168.100. # Debuggin Information log level = 1 log file = /var/log/samba/%m.log max log size = 50 debug timestamp = yes # Performance Tweaks getwd cache = yes socket options = TCP_NODELAY TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192 IPTOS_LOWDELAY dead time = 15 keep alive = 60 # lpq cache = 30 # Printing printer admin = root, rich, @adm printcap name = /etc/printcap load printers = yes [homes] comment = Home Directories browsable = no writeable = yes read only = no #create mode = 0777 [netlogon] path = /usr/local/samba/netlogon browsable = no writeable = yes guest ok = no valid users = @users @adm @sec create mask = 777 directory mask = 777 inherit permissions = yes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] AutoCAD temp file error
I continue to have this problem w/ LDD and it occurred even before I switched from an NT server to Samba. I'm fairly certain it's an Autodesk problem. -Original Message- From: [EMAIL PROTECTED] [mailto:samba-admin;lists.samba.org]On Behalf Of Brock Nanson Sent: Friday, November 01, 2002 8:31 PM To: Jay Ts Cc: [EMAIL PROTECTED] Subject: Re: [Samba] AutoCAD temp file error Hi Jay, Brock Nanson wrote: I rather doubt this is a samba problem, but perhaps someone can offer a hint to solve the issue... It's very unlikely to be a Samba bug, but may very well be a Samba misconfiguration. Perhaps. But the config hasn't been touched in 2 years and the WinXX workstations have never had the problem. The win2k box fails, saying the file could not be found on the path (and dumps a listing of the paths checked). The path exists in the list, and the file has been written to the directory! When the user responds to the error and the command completes, the file is successfully deleted from the server. So, it is doing everything except finding and inserting the file (which is there!). Exactly what is the name of the file, and are you using any foreign languages in file names? If you are using anything other than English, be aware that support for internationalization in Samba 2.2 is a little complicated to set up, and may be the source of your problem. Even if your file names are in the American/English character set, there are differences between how Unix and Windows handle filenames. A common source of trouble is case sensitivity in filenames. There are parameters that can be set in the Samba configuration file (smb.conf) to help deal with this. The filename looks like this: $abc$de.dwg The letters aren't right (I can't recall them exactly right now), but the file does start with a '$' and has a second on part way through as shown. I think the key to this is hidden in the way I can 'seed' the directory with this file once and have the command work until a new drawing is opened after doing so. Note that the file is deleted as a matter of course and that the file is not there the second, third,... time the command is used and it will work. But I need the file there the first time!! The temp file on the server is being saved with rwxrw-rw- attributes, although all the other files are rw-rw-rw-. That is because Samba's default is 'map archive = yes'. When the archive bit is set on a file from MS-DOS/Windows, Samba will keep track of it using the owner's execute bit. It will look like an executable file to a Unix user. If you don't like this, then set map archive = no in smb.conf. After doing this, MS-DOS backup software may not work right, because it won't see any archive attributes set for files to incrementally back up. Yeah, can't do this as I do use a Windows based backup utility. Funny that this file is the only one saved with the execute bit toggled. The other files AutoCAD creates don't have the execute bit set. I had wondered briefly if the speed with which the file is saved, then requested could be a problem. In a word: no. In three words: I highly doubt it! That's actually four words, but I do agree ;-) Any guesses? Or even a confirmation that the problem is with Win2k and NOT the samba box? I certainly wouldn't guarantee it's not a Windows bug. ;-) If you haven't fixed the problem by now, try providing a little more information, specifically, the _exact_ name of a temporary file that is problematic -- didn't you think of including that in your question? :) I did think of it but as I'm writing these postings away from the system couldn't remember the exact file name. I'm not very familiar with win2k but found it strange that it differentiates between 'Nobody' and 'nobody'. That has me a little worried, but as I can use the work around described above, I don't think the 'N' vs. 'n' is a problem. I do think it is a win2k issue, but it is odd that the problem can't be recreated when using a local drive. Any other ideas?? Thanks, Brock -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] PANIC: share_modes_identical
When 2.2.4 was released, I updated my cvs and did ./configure and make (no special options). Since I came in somewhat early today and nobody was around I did the make install. Everything ran fine until I tried to load a particular file and I'm receiving the following error and unable to open the file on a network share. If I place the file on a local drive it loads fine. Permissions and what not are identical to when I was running 2.2.3a. Any thoughts? TIA. smbd/service.c:make_connection(651) forman (192.168.100.14) connect to service cad as user rich (uid=506, gid=100) (pid 17884) smbd/open.c:open_mode_check(631) open_mode_check: exlusive oplock left by process 17884 after break ! For fileDRV/periscope/PScope15.arx, dev = 801, inode = 1193703. Deleting it to continue... smbd/open.c:open_mode_check(635) open_mode_check: Existent process 17884 left active oplock. locking/locking.c:share_modes_identical(560) PANIC: share_modes_identical: share_mode missmatch (e1 = 32, e2 = 32800). Logic error. lib/util.c:smb_panic(1092) PANIC: PANIC: share_modes_identical logic error. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
