RE: [Samba] Shares all empty after upgrade to 3.0.14a-fc4
Daniel, did you check max_protocol is it the same ? After I did an upgrade and the max_protocol was changed I had the same behaviour. Daniel I checked the smb.conf, and it did get changed. I don't know what changed it as the install scripts in the samba rpm don't do so. The following items were added: client ntlmv2 auth = yes restrict anonymous = no client lanman auth = no max protocol = NT server signing = Auto As you see it added max protocol and a few other lines which may well have messed things up. I already had max protocol=NT. I didn't expect this to happen and it's rather annoying that it did so without notice... Before your note arrived, I had decided to reinstall samba - save smb.conf, smbpasswd, delete RPMs [1], reinstall from scratch, use SWAT to get basic smb.conf running again. It worked fine, which suggests it was some configuration thing. Thanks for the suggestion, though Ruth [1] rpm --erase didn't delete the manual pages... -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Shares all empty after upgrade to 3.0.14a-fc4
/util_sock.c:write_socket(449) write_socket(5,268) [2005/07/16 00:57:12, 6] lib/util_sock.c:write_socket(452) write_socket(5,268) wrote 268 [2005/07/16 00:57:12, 4] smbd/trans2.c:call_trans2findfirst(1518) SMBtrans2 mask=* directory=./ dirtype=22 numentries=2 -- Ruth Ivimey-Cook [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Help! Settings in roaming profile are not sticking
I'm reinstalling my Windows XP box. It has been on my home domain with a roaming profile for some time. I had earlier problems with the roaming user not able to log in at all but I can now log in using that account thanks to deleting the samba cache. The problem now is that settings in the roaming profile are not sticking. For example, the old profile has the Coffee bean background and the XP Themed appearance. Now, as it loads, it starts to set coffee bean, then before fully loaded replaces it with windows-blue, and the windows style is classic. Moreover, I can't change the desktop or theme at all, and icons refuse to stay put if I move them. In the old setup, I had Outlook all set up nicely. Now, although it starts up it says it can't load, and exits. Can anyone give me a hint as to what has gone wrong? Is there some registry or policy setting or machine-SID-related thing that would cause this? Yours hopefully, Ruth System info: PDC is Samba 3.0 on Fedora Linux. I have 2 other XP machines that have been using the profile ok, along with the former install on the problem machine. Problem machine is a P4 3GHz, 1.5GB RAM. XP SP2 plus latest patches. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Loading new profile: reverts to classic and cant change...
Please help! I'm really confused. I've been reinstalling windows on my windows xp box. The problems I had earlier with the roaming user not able to log in at all are sorted: I figured it must be samba caching the old sid of the old PC, and by forcing samba to recreate it (move /var/cache/samba to samba.old) I found I could log in with the roaming profile again. The problem now is that settings on the login have been changed. For example, before this I had Coffee bean background and the XP Themed appearance. Now, as it loads, it starts to set coffee bean, then replaces it with windows-blue, and the windows style is classic. Moreover, I can't change the desktop or theme at all, and icons refuse to stay put if I move them. In the old setup, I had Outlook all set up nicely. Now, although it starts up it says it can't load, and exits. What's gone wrong? Regards, Ruth -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Roaming profile blues.
Folks, I have a samba 3 (Fedora 3) PDC which has been working fine for some time now with a roaming profile. I've just reinstalled Windows XP SP2 on my main work machine. I remembered to set the three *seal* registry flags to 0, and joined the computer (which has the same textual name as before) to the domain. All well so far. Trying to log in as local user works. That user can access samba shares also. I also managed to join the domain ok. The problem is that something prevents me from logging in to roaming profile user defined on the PDC. The only diagnostic samba messages I get are: [2005/06/03 14:56:39, 1] rpc_server/srv_netlog_nt.c:_net_sam_logon(766) _net_sam_logon: user HOME\rivimey has user sid S-1-5-21-117080783-426460007-1280929931-2002 but group sid S-1-5-32-547. The conflicting domain portions are not supported for NETLOGON calls I eventually found a note on the net about using gpedit.msc not checking for ownership of files, and set the policy: Local Configuration/Administrative Templates/System/User Profiles/Do not check for user ownership of Roaming Profile Folders = Enabled. Having done that I took the computer out of the domain, rebooted twice, logged in as admin and tried to take the machine back into the domain. Now it doesn't want to play: it says a domain controller for the domain HOME could not be contacted. Well, I restart samba and it agrees to join the domain. Now, however, it complains that I can't log in to the roaming user because a device has failed. There is no problem logging into the local accounts and I can't see any warning or errors in the event log, nor can I see Devices listed in device manager that aren't working, nor Services set to automatic that aren't running (except Security Center, which stopped successfully when I started it by hand). What is going wrong? Thanks -- Ruth Ivimey-Cook Software engineer and technical writer. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Bug report
Hi, Shortly after removing the wins.dat files as John T suggested, the nmb process died with the following backtrace. I restarted it, and all seems well. The Samba version is that from latest FC3 (samba-3.0.10-1.fc3). I can post config info if required: [2005/01/28 00:34:51, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(295) become_domain_master_browser_bcast: querying subnet 192.168.0.7 for domain master browser on workgroup HOME [2005/01/28 00:34:55, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup HOME on subnet 192.168.0.7 [2005/01/28 00:34:59, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113) * Samba server FILESTORE is now a domain master browser for workgroup HOME on subnet 192.168.0.7 * [2005/01/28 00:35:14, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) * Samba name server FILESTORE is now a local master browser for workgroup HOME on subnet 192.168.0.7 * [2005/01/28 00:38:53, 0] lib/fault.c:fault_report(36) === [2005/01/28 00:38:53, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 16184 (3.0.10-1.fc3) Please read the appendix Bugs of the Samba HOWTO collection [2005/01/28 00:38:53, 0] lib/fault.c:fault_report(39) === [2005/01/28 00:38:53, 0] lib/util.c:smb_panic2(1504) PANIC: internal error [2005/01/28 00:38:53, 0] lib/util.c:smb_panic2(1512) BACKTRACE: 8 stack frames: #0 nmbd(smb_panic2+0x8a) [0x6df1bd] #1 nmbd(smb_panic+0x19) [0x6df3e9] #2 nmbd [0x6ca929] #3 /lib/tls/libc.so.6 [0x153a48] #4 nmbd(refresh_my_names+0x45) [0x675421] #5 nmbd(main+0x4da) [0x66be97] #6 /lib/tls/libc.so.6(__libc_start_main+0xe3) [0x140e33] #7 nmbd [0x66a661] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Phanton domain controller problem...
On Fri, 28 Jan 2005, John H Terpstra wrote: For example: [snip] I hope that helps to clarify things. John, Yes, I am a lot clearer now :-) Ruth -- Ruth Ivimey-Cook Software engineer and technical writer. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Phanton domain controller problem...
Hi, Recently I reinstalled the OS on my Samba PDC, letting Linux FC3 installer do it's thing then overwriting the smb.conf with my old one. Now I find that although it tries but can't become Domain master browser again, although it is happy to become a local master, a login server and to serve files. The reason given in the log files is that there is another PDC on the submet at 192.168.0.145 (see below). That IP is the IP address that this (the only) samba server had for a short period during the reinstall. There is no machine at that IP now. What is going on? Is there some file that stores PDC IP addresses? Note in the winbind dump below, the 192.168.0.145 address for HOME and for FILESTORE, both of which are bogus. Regards, Ruth [2005/01/27 23:17:39, 4] nmbd/nmbd_winsserver.c:wins_write_database(1825) wins_write_database: Dump of WINS name list. *00 TTL = PERMANENT 192.168.0.7 64 *20 TTL = PERMANENT 192.168.0.7 64 FILESTORE00 TTL = Sun Jan 30 23:03:56 2005192.168.0.145 192.168.0.7 66 FILESTORE03 TTL = Sun Jan 30 23:03:56 2005192.168.0.145 192.168.0.7 66 FILESTORE20 TTL = Sun Jan 30 23:03:56 2005192.168.0.145 192.168.0.7 66 GANDALF00 TTL = Mon Jan 31 09:56:17 2005 192.168.0.8 44 GANDALF20 TTL = Mon Jan 31 09:56:17 2005 192.168.0.8 44 HOME00TTL = Sun Jan 30 23:03:56 2005 255.255.255.255 e4 HOME1bTTL = Fri Jan 28 15:11:24 2005192.168.0.145 64 HOME1cTTL = Sun Jan 30 23:03:56 2005192.168.0.145 192.168.0.7 e4 HOME1eTTL = Sun Jan 30 23:03:56 2005 255.255.255.255 e4 __SAMBA__00 TTL = PERMANENT 192.168.0.7 64 __SAMBA__20 TTL = PERMANENT 192.168.0.7 64 [2005/01/27 23:17:39, 4] nmbd/nmbd_packets.c:initiate_name_release_packet(410) initiate_name_release_packet: sending release for name FILESTORE00 (bcast=No) to IP 127.0.0.1 snip [2005/01/27 23:17:39, 4] nmbd/nmbd_packets.c:debug_browse_data(100) debug_browse_data(): 0 char ..FILESTORE. hex 01 05 00 00 00 00 46 49 4c 45 53 54 4f 52 45 00 10 char ..U. hex 00 00 00 00 00 00 04 09 00 00 00 00 0f 01 55 aa 20 char Samba Fileserver hex 53 61 6d 62 61 20 46 69 6c 65 73 65 72 76 65 72 30 char .hex 00 [2005/01/27 23:17:39, 5] libsmb/nmblib.c:send_udp(776) Sending a packet of len 217 to (192.168.0.255) on port 138 [2005/01/27 23:17:39, 0] nmbd/nmbd.c:main(669) Netbios nameserver version 3.0.10-1.fc3 started. Copyright Andrew Tridgell and the Samba Team 1994-2004 [2005/01/27 23:17:39, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) add_domain_logon_names: Attempting to become logon server for workgroup HOME on subnet 192.168.0.7 [2005/01/27 23:17:39, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) add_domain_logon_names: Attempting to become logon server for workgroup HOME on subnet UNICAST_SUBNET [2005/01/27 23:17:39, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(327) become_domain_master_browser_wins: Attempting to become domain master browser on workgroup HOME, subnet UNICAST_SUBNET. [2005/01/27 23:17:39, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(341) become_domain_master_browser_wins: querying WINS server from IP 192.168.0.7 for domain master browser name HOME1b on workgroup H OME [2005/01/27 23:17:39, 0] nmbd/nmbd_become_dmb.c:become_domain_master_query_success(225) become_domain_master_query_success: There is already a domain master browser at IP 192.168.0.145 for workgroup HOME registered on subnet UNICAST_SUBNET. [2005/01/27 23:17:39, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup HOME on subnet UNICAST_SUBNET [2005/01/27 23:17:43, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup HOME on subnet 192.168.0.7 [2005/01/27 23:18:02, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) * Samba name server FILESTORE is now a local master browser for workgroup HOME on subnet 192.168.0.7 * [2005/01/27 23:18:23, 0] nmbd/nmbd_browsesync.c:domain_master_node_status_fail(250) domain_master_node_status_fail: Doing a node status request to the domain master browser for workgroup HOME at IP 192.168.0.145 failed. Cannot sync browser lists. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Where are Windows file permissions stored and how to changethem?
Florian, where are the Windows file permissions (i.e. ACL) stored when using Samba? The answer is it depends! If you have a Linux filesystem that can store ACLs - such as ext3 with the appropriate kernel build option - and you have told Samba that it should use it, then the permissions are stored in the ACL, and you can access them using the appropriate Linux utilities. If you haven't done the above, then Samba tries to map the permissions to the standard Unix permissions, with obviously limited success in some cases. Hope this helps, Ruth -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Problem updating roaming profile
Hi, I have been trying for the last couple of days to sort out a roaming profile configuration of Samba. The network is a Linux Samba PDC server (Samba 3.0.6, Kernel 2.0.7 plain) with several Windows XP Pro clients. The filesystem is ext3 with extended attributes enabled ( acls compiled in, but I'm not sure if samba is using it). I am getting an error when logging out of a client that it can't update the profile because it Cannot create a file when that file already exists. How do I sort it out? Secondly, I've just discovered that some (but not all) of the server's file shares are responding with the contents of one of the other shares; e.g. if I look at my home share (rivimey) I see the contents of the tmp share; however, if I navigate via the Users share to my home share things are where they should be. Thanks, Ruth P.S. smb.conf config file available on request. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
