search for: reghacks

I have a handful of machines with all of the latest windows updates, and the WinXP reghack wont stay. If I enter the EnablePlainTextPassword reghack, and reboot, all is fine, until the machine is logged off or rebooted, then it reverts back to EnablePlainTextPassword=no Seems to be only affected on machines using Novell 4.83.6 SP1 client... although something else could be the cause. Machines

I run a NT-Domain with samba 3.0.28a and WinXP-Clients (SP3) Everything is fine. But now I created a new user and this new user can logon to all machines in the Domain but one. On this machine the user gets the message "user cannot login. check username/password/domain and be aware that username/password are casesensitive" (I translated this from german) Other users can login fine. I

...e statements in usenet, but I wonder if there is a kind of XP-FAQ out there. (The one at samba-page is very outdated) Especially I need to know how well XP integrates in a existing NT4-domain (samba as PDC). Then I need to know if there are any problems with fileservers (I remember rumours about reghacks one has to apply on XP to make things work) And finally - if a machine is not part of the domain (guest-laptop): if a local XP-user with user/pass similar than on samba-server is sufficient for auth on the sambaserver ? thnx, peter -- mag. peter pilsl IT-Consulting tel: +43-699-1-3574035 fax:...

Hi all, After some config changes and reboots, I got the Samba server running properly for my client computers running Windows 7. My issue now is with Windows 10. I see threads relating to setting "max protocol = NT1", but this seems to break the Windows 7 clients (which are finally working again). Below is my smb.conf file (which works for Windows 7): [global] workgroup = JMC

OK, then here's the weird part. I have another server, hosting other files, lets my Windows 10 system connect. The main server won't though. They are both running Debian Jessie 8.3, and Samba 4.1.17-debian. Below is the /etc/samba/smb.conf file *that works with Windows 7 and 10*: [global] workgroup = SD57 netbios name = SAMBA server string = sss interfaces

On 02/04/16 20:02, Luke Barone wrote: > Also, when I run testparm -svv | less I can find these four lines on > both the working and non-working servers: > > server max protocol = SMB3 > server min protocol = LANMAN1 > client max protocol = NT1 > client min protocol = CORE > > > On Sat, Apr 2, 2016 at 11:57 AM, Luke Barone

On 02/04/16 19:17, Luke Barone wrote: > Hi all, > > After some config changes and reboots, I got the Samba server running > properly for my client computers running Windows 7. My issue now is with > Windows 10. > > I see threads relating to setting "max protocol = NT1", but this seems to > break the Windows 7 clients (which are finally working again). Below is my

"This error can occur if the drive letter you are mapping with a net use command is already mapped in the user's properties." part of the JSI FAQ at http://www.jsifaq.com/reghack.htm TO fix it, try disconnecting the drives before mapping new ones. This may or may not be the best way to fix it, but in my scripts, I use this: NET USE M: /delete /yes >nul NET USE M:

I have a Redhat 7.3 server running Samba-3.0.0 installed from the binary RPM's. It's acting as a PDC with Roaming profiles. I'm not certain if what I'm seeing is actually an error or not, but perhaps someone can shed a little light on what exactly it is that I'm seeing here. I have a WinXP Pro machine that I will log into with my domain username and password. My roaming

Hi, I keep coming across this problem. Samba is samba 2.2.5 Go to join a winxp box to the domain and it all appears to work fine. When you restart you can not login because it wasn't done properly. Here are my obversations from samba. A) In the logs there is always this [2002/10/24 07:12:43.415583, 1] smbd/password.c:pass_check_smb(545) Couldn't find user 'nobody' in

Also, when I run testparm -svv | less I can find these four lines on both the working and non-working servers: server max protocol = SMB3 server min protocol = LANMAN1 client max protocol = NT1 client min protocol = CORE On Sat, Apr 2, 2016 at 11:57 AM, Luke Barone <lukebarone at gmail.com> wrote: > OK, then here's the weird part. I have another

No one had any other offerings here? I can't find anything that clears this up. And this machine can get to a Linux based Samba server just fine. Paul -----Original Message----- From: Paul Harlow [mailto:PHarlow@skld.com] Sent: Thursday, May 09, 2002 3:29 PM To: Samba List (E-mail) Subject: RE: [Samba] Windows 2000 and Samba Sam: It wasn't pointing at the WINS server at first (the

I have a Samba server running on an AIX 4.4.3 RS6000 that has been serving up files without problem. Recently, a pair of machines, both Windows 2000 Pro, haven't been able to gain access to any of the Samba resources on the AIX server though they were both able to previously. Other WinNT and Win2k machines can get to these shared resources fine, just not these two. I haven't found anything