similar to: No XP machines in browse list with 3.0.22

Our domain controller is running Samba 2.2.8a on Solaris 8. We have XP laptops. We swap between a builtin network card, docking port and wireless card. All of these have separate IP addresses. If I say, boot up with the wireless card, then remove it and use the builtin network card, the IP address in wins.dat on the server doesn't change. It still has the IP address of the wireless card.

We have a Sun E450 running Solaris 8 and Samba 2.2.8a as our domain controller. We have had no problems with Samba until earlier this week when we have started to get lots of these errors in log.smbd: [2003/08/08 16:29:14, 0] lib/debug.c:(348) Unable to open new log file /home/samba_pearl/var/log.smbd: Too many open file s This has been happening once a day, at the same time some users are not

We have a Windows 2003 server that is a member of a Samba 2.2.8a domain. We can browse to this Samba server through "My Network Places" and map a drive to a share on this server. We also have a number of Samba 3.0.1 servers (running Solaris 8 and Red Hat 7.0). These are member servers of the Samba 2.2.8a domain. Using "My Network Places" on the Windows 2003 server, double

Upgraded our Solaris 8 and 9 servers from 3.0.2a to 3.0.3. After upgrading any user that was in more than 16 Unix groups wasn't able to map any drives. I get this error in the log file: [2004/05/04 12:23:30, 0] auth/auth_util.c:get_user_groups(695) get_user_groups: failed to get the unix group list [2004/05/04 12:23:30, 0] auth/auth_sam.c:check_sam_security(260) check_sam_security:

Tried to upgrade our Samba 2.2.8a domain controller (Solaris 8) to Samba 3.0.2a. Compiled using gcc 3.3.2, linked to libiconv-1.8, popt-1.7 and cups-1.1.20. I shut down the Samba 2.2.8a. Removed everything in var/locks. Did a "make install" to install 3.0.2a, then restarted Samba. My smb.conf is basically the same as 2.2.8a with "domain admin group" removed. When I stared

Have just upgraded from 3.0.13 to 3.0.20 on our Solaris domain controller. Machine is also print server running CUPS-1.1.23. We have a RICOH network printer that we print to via Samba (the printer seems to have a builtin Windows PC). smbspool is linked to /usr/lib/cups/backend/smb and the appropriate DeviceURI is in /etc/cups/printers.conf. This works fine with 3.0.13, but with 3.0.20 I get this

We've got a Windows 2003 server which won't join our Samba domain, it just sits their forever after I give the root password to join. It doesn't give an \ error message or "Welcome to domainxyz" message. It also won't join a workgroup, which is strange. Has anyone else seen this problem? No problems with XPSP2 clients. Not got 2003 SP1 on yet, might try that next.

Just setup a new domain controller running Samba-3.0.20b. Using smbpasswd file (no LDAP). How do I setup a group of users so they become domain administrators? I thought I just typed this: % net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmin I am in group unix ntadmin, but I'm it doesn't seem to work. Michael -- Michael Keightley

Just swapped our Solaris SAMBA PDC for a SuSE Linux machine. It's the domain controller as well as print server (via CUPS). It's running SuSE 9.3 with Samba-3.0.20b. The setup is identical to the old Solaris machine, had to re-add all machines to the domain. Has been working OK for 2 days then suddenly some people couldn't print and I can no longer add printers to any XP machine.

We're using Cups and Samba with Adobe Postscript Drivers to print from XP SP2 machines via our Solaris and Linux Domain Controllers. Everything has been working OK, but when I setup an a new printer (identical ppd file to another one), it doesn't download the drivers on XP when I add the printer. This is happening on two domain controllers in different offices. It gives the error when

Hi folks, I have updated samba to 3.0.20, on SLES9. I had a configuration earlier, where SLES9 was a domain member 2003 Server (samba 3.0.14a), everything used to work well earlier. After updating.. I rejoined it to AD there was no errors. However, Clients from windows were unable to access the shares. #>getent passwd [2005/08/22 15:41:41, 0] lib/fault.c:fault_report(36)

Greetings. I'm running samba 2.2.1a on a network that consists mostly of linux servers and win2k clients. There are N subnets here (roughly 18 or 20; I lost track :) and cross subnet browsing is no issue. What is an issue is that machines which go offline tend to remain in the browse lists -- forever. Gack. There are two main samba servers here: one which is used for file/print

Hello, we are using "samba-2.0.6" (running on linux-2.2.14 machine). On our client machines we use "Windows 9x". There are 2 network segments: Segment 1 (192.168.1.0): - 13 Win95 client machines - 1 samba-2.0.6 server ("fsa01") which is WINS, DMB and LMB in its network segment (192.168.1.0). This samba is also the login server for our Win9x clients. Segment 2

I've exactly the same problem. My config looks similar to yours: 1 samba as wins server (wins support=yes" on one segment, 1 samba as "wins server client" (wins server = xxx). The "wins server client" never discards machines from segment 1. I looked at the browse.dat and the wins.dat on the server on segment 1. There are no entries of the shutdowned maschines. Only in

I used to be able to browse the windows shares on the network through Nautilus. I can see them as computers, but when I click on them, it fails. (I'm on Ubuntu 6 LTS, AMD64) About 3 months ago, this failed. But, the windows boxes can all still access my shares on my Linux box. I was going through the trouble shooting, and found this out, but I'm not sure what to do next. I am

Server - Samba 3.0.14 on AMD64 running Gentoo Client - XP professional Can log in, see, browse, and write TO shares according to permissions assigned on server. Just can't read or copy any files FROM server to XP client. Disabled XP firewall to see if it was interfering, no change. Lots of google searching, found a post from 17/11/98 posing a similar question but no answer...

Hello folks. I need to migrate from an old server still running Debian Woody to a new server running Dapper Drake. The big challenge is turning out to be who to plan out the Samba LDAP migration. The current server version is 3.0.20 compiled form source and the Dapper package is 3.0.22 and appears to include ldap support. So I don't think I need to compile or worry about version

I'm trying to decide on a linux distro to use for our enterprise Samba server. I like that there is a deb repo for Debian from samba.org, but I'm more comfortable with CentOS (Redhat). I just want to be sure I have a well supported Samba server and I need at least the 3.0.20 version so I can use the "inherit owner" property. I also want automatic updates for bugfixes and

Hello, I have samba-3.0.10-1.4E.6 bundled with CentOS 4.3 x86_64 and I can't browse it with Win98. I have a very simple setup, Share type, with access to everyone. If I double-click on the server name from Win98, I have this message: "\\server is not accessible. This device does not exist on the network." If I type the whole path to the share(ex: \\server\transfer), in Win98, it

I have created a domain controller using samba 3.0.20. I following howto's from a couple of books and the samba.org site. I was able to use net rpc vampire to migrate the old nt4 domain user accounts, machine accounts, and trusts. However, now when I attempt to use add a new machine to the domain I receive and error. From windows I get: "The user name could not be found" When I