[Samba] Samba domain groups
When I do a net groupmap list I get Domain Admins (S-1-5-21-1760016482-394088656-2614712563-512) - root Domain Admins (S-1-5-21-1941513877-1053742263-1100610399-512) - -1 Domain Admins (S-1-5-21-57081839-3644741509-3819056003-512) - -1 Domain Guests (S-1-5-21-1760016482-394088656-2614712563-514) - nogroup Domain Guests (S-1-5-21-1941513877-1053742263-1100610399-514) - -1 Domain Guests (S-1-5-21-57081839-3644741509-3819056003-514) - -1 Domain Users (S-1-5-21-1760016482-394088656-2614712563-513) - users Domain Users (S-1-5-21-1941513877-1053742263-1100610399-513) - -1 Domain Users (S-1-5-21-57081839-3644741509-3819056003-513) - -1 Why is there 3 groups of every kind? I have not done anything to get them. Can I delete the groups that is not mapped to unixgroups with Webmin? Or shall I let them exist and not bother about them? Bjørn Fahnøe -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re[2]: [Samba] Samba domain groups
Den 23-02-2006 kl 10:53 skrev Chris: On Thursday 23 February 2006 10:33, Bjørn Fahnøe wrote: Is it wrong? What can I do to correct? I've used net groupmap cleanup in the past with success. Chris So what is the correct procedure? 1 Install the server 2 install Samba 3 do a net groupmap list 4 if there are several instances of the same groups do af net groupmap cleanup 5 hope it did the trick 6 do: net groupmap modify ntgroup=Domain Admins unixgroup=root net groupmap modify ntgroup=Domain Users unixgroup=users 7 hope it works I have installed the trial server several times bow before I will try to install to the production server It's an educational process, but I think I am usíng a lot of time getting it to work. Earlier I have only used simple servers without domainregistration of machines, logonscripts etc I am used to a Novell server so its really hard work to have the Samba server provide the same. I am helping a small primary school to set up a network, as their earlier tries have been without much succes. Bjørn -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba domain groups
When I do a net groupmap list I get Domain Admins (S-1-5-21-1760016482-394088656-2614712563-512) - root Domain Admins (S-1-5-21-1941513877-1053742263-1100610399-512) - -1 Domain Admins (S-1-5-21-57081839-3644741509-3819056003-512) - -1 Domain Guests (S-1-5-21-1760016482-394088656-2614712563-514) - nogroup Domain Guests (S-1-5-21-1941513877-1053742263-1100610399-514) - -1 Domain Guests (S-1-5-21-57081839-3644741509-3819056003-514) - -1 Domain Users (S-1-5-21-1760016482-394088656-2614712563-513) - users Domain Users (S-1-5-21-1941513877-1053742263-1100610399-513) - -1 Domain Users (S-1-5-21-57081839-3644741509-3819056003-513) - -1 Why is there 3 groups of every kind? I have not done anything to get them. Can I delete the groups that is not mapped to unixgroups with Webmin? Or shall I let them exist and not bother about them? Bjørn Fahnøe -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Xp-pc's disappear in Network Neighborhood
I have this problem. Window Xp machines show up in Network neighborhood when they are started but after some time (20 minutes or more) they disappear. I can find them with search computer. Mapped network drives still work. They reappear if I restart the pc They reappear if I restart Samba Its only a small home network so I do not log in to a domain. Whats going on? My samba.conf # Global parameters [global] log file = /var/log/samba/log.%m ldap ssl = no socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printer name = Epson domain master = Yes map to guest = Bad User printer admin = @adm wins support = true dns proxy = No netbios name = BF-SERVER server string = Samba Server %v workgroup = BFHJEMME os level = 35 unix charset = ISO8859-1 max log size = 50 [homes] comment = Home Directories read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes use client driver = Yes browseable = No [print$] path = /var/lib/samba/printers write list = @adm, root inherit permissions = Yes guest ok = Yes [Alle] path = /var/Alle read only = No create mask = 0777 directory mask = 0777 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Win XPPro not connecting to samba domain
Off_Kilter wrote: Steps to replicate: 1. Select 'To rename this computer or join a domain, click Change' 2. Select 'Domain' and enter the domain name. Click OK 3. When asked to enter credentials, enter admin user and password. Click OK This error comes up: The following error occurred attempting to join the domain foobar: The specified domain either does not exist or could not be contacted. NOTES: a. If I enter a fake domain in #2 above, it is a different error, it only asks for user/pass when the correct domain is supplied. b. Nothing is showing up in the /var/log/samba/log.smbd file when this happens. Have you created a sambauser named root and given a password? You must use this user to join the domain Bjørn Fahnøe -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smb log error-Transport end point/getpeername
Den 11-02-2005 kl 12:09 skrev David Rankin: From: Josh Kelley [EMAIL PROTECTED] david rankin wrote: Well, no, I'm not positive, but when whatever hangs, I get a big slowdown in file access, file open, etc.. from XP. When I then go and check the logs the transport end point and getpeername is the only thing that shows up in the log. I admit I haven't had time to put up a console and check in the past few days. It is definately an XP issue. It occurs on both Suse 9.0 and Mandrake 7.2 with 3.0.7. It occurred with all the 2.0 and 2.2 sambas as well. I'll keep an eye on it and report back. This is a bit of a shot in the dark, but do you have port 80 firewalled off on your Samba server? It's my understanding that by default, XP will try to access network drives via WebDAV before trying SMB, and a firewall that drops attempted connections to port 80 or that doesn't respond with a TCP reset can cause noticeable slowdowns in connections from XP. Thanks for the 'shot', but in my case, port 80 is wide open I have followed this thead because I have had the same troubles. On the Primary server I have used socket = IP-addres of server and I have both the lmhost og the hosts files up to date When I now set up a second server on another workgroup but same subnet and disable port 443 in Samba and only uses port 139, it seems that it all works ok. I am still worried though, I have really had a lot of trouble and lost many hours trying to solve this problem. Its was not only slowing the system when the errors occured, I experienced database errors if a program was writing to a database when it happended. And the database has to be repaired. If anyone knows more of this problem do write, I ko not know why these correction to the smb.cfg helps and why they ar necessary. Bjørn Fahnøe -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smb log error-Transport end point/getpeername
Den 10-02-2005 kl 13:06 skrev david rankin: From: Gerald (Jerry) Carter [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 david rankin wrote: | |I'm trying to solve some log errors I getting. I | have samba 3.0.7 installed on Suse 9.0. It has been | happening intermittently for several months. I don't know | if this is XP client related or what. Any thoughts: | The errors are: | | Feb 9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] | lib/util_sock.c:get_peer_addr(1000) | Feb 9 20:00:33 skyline smbd[14408]: getpeername failed. Error was | Transport endpoint is not connected I know that Windows XP clients try to connect to port 139 and 445 in parallel and drop the connection to port 139 if the connect to 445 is successful. This is probably what you are seeing. Thanks Jerry, That makes sense. No doubt an intentional feature from M$. Is there any way to get around it? When it occurs, there is a real slowdown in the connection. It is intermittent so it doesn't last that long, but it is sure annoying when it does. -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba *** Citat slut *** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba network errors
Samba seems to work OK but I have the following problem: In the log I get the following Jan 27 10:33:53 test smbd[5055]: [2005/01/27 10:33:53, 0] lib/util_sock.c:get_peer_addr(1000) Jan 27 10:33:53 test smbd[5055]: getpeername failed. Error was Transport endpoint is not connected Jan 27 10:33:53 test smbd[5055]: [2005/01/27 10:33:53, 0] lib/util_sock.c:get_peer_addr(1000) Jan 27 10:33:53 test smbd[5055]: getpeername failed. Error was Transport endpoint is not connected Jan 27 10:33:53 test smbd[5055]: [2005/01/27 10:33:53, 0] lib/util_sock.c:write_socket_data(430) Jan 27 10:33:53 test smbd[5055]: write_socket_data: write failure. Error = Connection reset by peer Jan 27 10:33:53 test smbd[5055]: [2005/01/27 10:33:53, 0] lib/util_sock.c:write_socket(455) Jan 27 10:33:53 test smbd[5055]: write_socket: Error writing 4 bytes to socket 23: ERRNO = Connection reset by peer Jan 27 10:33:53 test smbd[5055]: [2005/01/27 10:33:53, 0] lib/util_sock.c:send_smb(647) Jan 27 10:33:53 test smbd[5055]: Error writing 4 bytes to client. -1. (Connection reset by peer) It means at least that I temporarily looses the connection and if writing to a database it becomes corrupted. I cannnot se i have made somthing wrong. Samba 2.x worked fine but Samba 3 is giving this problem. What can be done? Is it a bug? Is Samba misconfigured? Or is the network misconfigured? I have checked network configuration with webmin. It now has a box in Routing and Gateways which says the folowing: Destination Gateway Netmask Interface 10.0.0.0 0.0.0.0 255.255.255.0 eth0 Default Route 10.0.0.10.0.0.0 eth0 My configuration is IP: 10.0.0.10 Netmask 255.255.255.0 Gateway 10.0.0.1 Broaddcast 10.0.0.255 So what does the box mean? Have I misconfigured something in the network? I have reconfigured my eth0 with MDK Controlecenter, and nothing changes. It is really frustrating as it is the basic configuration I am loosing my time with and not the network for the benefits of the users. I have another thing. In the Microsoft Network the Xp-workstations disappear after a time (5-20 minutes) I can find them via Find computer. If I close down the Samba service it does not happen. Bjørn -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: getpeername failed. Error was Transport endpoint is not connected, don't solve?
Fernando Ribeiro [EMAIL PROTECTED] wrote in news:20041019173654.GJ3108 @musb.nerdgroup.org: getpeername I get the same error, on a very basic Samba configuration. Have you got any solutions or answers? I did not have the same problems in Samba 2.x Bjørn Fahnøe -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Error: getpeername failed
I have samba-server-3.3.10-0.1.101mdk installed and I get the following errors Jan 27 22:12:13 test smbd[5268]: [2005/01/27 22:12:13, 0] lib/util_sock.c:get_peer_addr(1000) Jan 27 22:12:13 test smbd[5268]: getpeername failed. Error was Transport endpoint is not connected Jan 27 22:12:13 test smbd[5268]: [2005/01/27 22:12:13, 0] lib/util_sock.c:write_socket_data(430) Jan 27 22:12:13 test smbd[5268]: write_socket_data: write failure. Error = Connection reset by peer Jan 27 22:12:13 test smbd[5268]: [2005/01/27 22:12:13, 0] lib/util_sock.c:write_socket(455) Jan 27 22:12:13 test smbd[5268]: write_socket: Error writing 4 bytes to socket 23: ERRNO = Connection reset by peer Jan 27 22:12:13 test smbd[5268]: [2005/01/27 22:12:13, 0] lib/util_sock.c:send_smb(647) Jan 27 22:12:13 test smbd[5268]: Error writing 4 bytes to client. -1. (Connection reset by peer) I have installed a second server to test and I get the same errors Samba seems to work OK, but if I am writing to af database at the same time as the error occurs the database gets corrupted. So the connection seems to be broken for a short time. I don't like this behavior, I had not something like it with Samba ver. 2.x Is it a bug in Samba? Have I misconfigured Samba or the network? What can I do? Bjrn Fahne [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
