similar to: password expires in 10 days no matter what Win2k Sp2 (All critical updates)

Greetz all, I am setting up a comain controller for a windows 2000 network and I think I have everything squared away. The problem that I am having right now is that all of the documentation/howtos that I have thusfar seen assume that a user wishes to implement roaming profiles in Samba. We want to preserve local profiles (local on the client.) I had seen a posting suggesting to set the

At 4:00 every morning the 2 WinXP machines on my network generate a slew of queries to bad printer names. These names are variations on the name of a valid printer exported by Samba. Samba v3.0.10 is running on a RHEL4 system. It exports several shared drives and a single printer. The printer is named "lj4500", is managed by CUPS v1.1.22, and works correctly via Samba from both

I have a samba server version 2.2.7a-8.9.0 running on RedHat 9.0. It is acting as a domain controller. I have some win2k clients logging in to this domain and mapping home shares, shared drives, etc. The network the servers are on is 1000Mb and the client networks are all 100Mb. The client networks are linked via 1000Mb uplink. The problem I'm having is that when a user copies a fair

I am running smbd version 2.0.9 and cannot map to a samba share from a Windows 2000 SP2 Server. I can however map from the samba server to the win2k Server. I can also map from the Windows Server to a windows 2000 Pro laptop on the same network, so I know that the server can map shares outside of itself. I can also map from a Win2K pro client and from other unix boxes to the samba server. I can

Hi everyone, Our system is a Debian GNU/Linux box running Linux kernel 2.4.17-xfs and Samba 2.2.3 (from the 2.2.3-5 package from Sid), built using gcc-3.0.3. With Samba 2.2.2 we hit certain tdb errors where make_connection would reject connections arbitrarily. Supposedly this was fixed using 2.2.3 so we upgraded right away (thankfully we do only have Windows 95, 98 and ME clients so we

For those who have been helping me or following the problem I've had of printing from Win2k (SP2) system to a printer on a Linux (Mandrake 8.1) server through Samba 2.2.1a, I have some good news and information that I hope helps other people. At this point I have established the problem is NOT a printing problem. It's a user/access problem that's connected with using my server

I'm getting frequent errors on Samba 3.0.10 about failing to access a share, where the name is missing its last character: Jan 13 20:55:42 pyloric smbd[18322]: [2005/01/13 20:55:42, 0] smbd/service.c:make_connection(800) Jan 13 20:55:42 pyloric smbd[18322]: vomit (192.168.23.143) couldn't find service music-ri vomit is a win2k (fully patched) machine. This error occurs when

I keep getting "Windows cannot copy file \\ssp1\profiles ... to C:\Documents And Settings\..." when trying to log into a Samba PDC using a Windows 2000 SP2 client. Does anybody have any ideas on how to fix this? I am including my smb.conf file, below: # Global parameters [global] workgroup = DC1 netbios name = SSP1 server string = Samba Server encrypt passwords = Yes update

Hi, I'm trying to get Samba on a Linux box to work. Authentication via user level worked fine, but what I really want is it to take user authentication from a win2k box, which is our "primary local server". The win2k box is not a pdc, (the real pdc is 2000km away, close to the polar circle), but according to the docs it doesn't have to be. So in smb.conf I put: security =

Suddenly, today, my wife's Windows 95 machine can't print to the network printer on my Linux machine. It complains that "there was an error printing to \\posh\lp ... There was a problem printing to the port." The error 1st occurred (coincidentally?) after I had upgraded the kernel from 2.4.18 to 2.4.19. But rebooting to 2.4.18 has made no difference. We're running smbd

I am running Samba 2.2.3a-12.3 as a PDC on Debian 3 (kernel 2.2). All seems to be working with 2 exceptions. The worst problem is when I logout of my Windows 2000 desktop. While the Win2k machine says it is "Saving Settings..." it will come up with an error box giving me a fatal exception in application unknown. The message box title says something like: "SAS Window:

I've looked through the archives and the only information I can find regarding Windows XP SP2 is RC2. Has anyone out there had ANY experience with XP SP2 Official and a Samba 3 domain? -- Bert Rapp North Trail RV Center p 239.693.8200 f 239.693.8115

I have been fighting this problem for months now. My performance under Samba and XP has ben umbearable. The scenario is running Samba 2.2.7a under SuSE 8.0 as a PDC. The XP machine logs onto Samba and the roaming profiles are downloaded then stops for 15 minutes or so. The network is verified 100Meg full-duplex, FTP transfers between the machines are robust and so no problems in connectivity. Any

In Windows explorer the computer (Penguin) and share (Ring) show up, but when I try to access the share, I get the following message: \\Penguin\Ring is not accessible The share name was not found. Be shure you typed it correctly. I have Samba set up on another Linux machine (OldPenguin) in the same network, and it works fine. Both computers run Red Hat 7.1 and Samba 2.0.7 (which came

Hai All, Can Anyone guide me what this log message mean Jan 3 18:17:34 smbserver smbd[19781]: 3ds09 (172.16.10.9) couldn't find service images Jan 3 18:17:34 smbserver smbd[19781]: [2006/01/03 18:17:34, 0] smbd/service.c:make_connection(798) Jan 3 18:17:34 smbserver smbd[19781]: 3ds09 (172.16.10.9) couldn't find service images Jan 3 18:17:34 smbserver smbd[19781]: [2006/01/03

SMB.conf, smbpasswd, log files attached to this message. I have several W2k Workstations, with a SAMBA 2.2.3 PDC. Looking at the logs it seems that stevedallas (W2K client) is getting validation errors as "visitor" (which DOES exist...) I am not sure what happened, but I must have removed all of the important parts of the server validation. OUTLAND is domain, W2k/ clients are

Hello everybody, I have a strange failure in my samba environment ( samba 2.2.3a ), when users try to open files on a samba share via the windows explorer. I see the following messages in the samba log file : hcnch049 (10.12.48.103) connect to service homedir as user pa015276 (uid=8065, gid=8048) (pid 19565) [2002/08/01 08:54:09, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb

Hello everybody, I have a strange failure in my samba environment ( samba 2.2.3a ), when users try to open files on a samba share via the windows explorer. I see the following messages in the samba log file : hcnch049 (10.12.48.103) connect to service homedir as user pa015276 (uid=8065, gid=8048) (pid 19565) [2002/08/01 08:54:09, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb

Hello all. A couple of days back I posted a question about how I could get a Win2K client to mount a share from my linux Samba server. I was getting the familiar "account is not authorized to log in from this station" error on the Win2K box, despite a set-up that supposedly allowed guest logins *and* implemented the registry hack for clear-text passwords on the Win2k box. While I

Running a samba server version 3.0.7 on a FreeBSD box Life has been fine with XP and so forth I added a new vista workstation to my small network Vista found my shares and I am able to access them with no jerking around with authentication types or such as I use appropriate pw and user name to log into the vista box. Problem is vista is spamming my server, taking up >50% cpu