similar to: issue with win7 access samba server running on AIX

On Fri, 2012-04-13 at 19:41 +0000, Chu, Ronald wrote: > hey all. we are running samba 3.5.4 on AIX but when client upgrade to > Win 7.. none of the client on window can see the share drive on AIX. > > the error said "window cannot access "servername" .. i know it is > group policy causing the problem and > > once i took out "computer configuration

flight 21993 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/21993/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 7 redhat-install fail REGR. vs. 20054 Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-qemuu-win7-amd64 8

flight 21930 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/21930/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 7 redhat-install fail REGR. vs. 20054 Tests which are failing intermittently (not blocking): test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 7

flight 21952 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/21952/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 7 redhat-install fail REGR. vs. 20054 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop

Hi, I've compiled Samba 3.0.25b on an AIX 5.2 machine without any hassle (also without ADS / Kerberos Support!) but getting it to join our AD domain is a true PITA. The AIX machine is called NLXDRZ05, the domain D-REIZEN.INTRA (could also be D-REIZEN, I'm a Unix guy, not an NT guy and I usually leave that stuff to the people that know what they're doing) I've had a machine

Timo Altun skrev den 2015-05-19 08:12: > Hi Davor, > > thanks for the answer. They were actually part of a NT4 domain called > mayweg.net <http://mayweg.net> (the new realm name). But I did join > workgroup "WORKGROUP" before I tried to join the new domain. > If it's possible that they're sending the information the wrong way > because they were part

I have been trying for 3 weeks to get 3.0.21b to work on AIX 5.2. I am currently running 3.0.4, which has no problems. I am getting very frustrated, and am about to give up entirely on Samba. Here are some of the errors I am getting: [<root> mcom4:/opt/Samba/3.0.21b/bin] > ./smbclient -L ccasemcom4 -d 3 -N -Ub06reg%Becky1208 lp_load: refreshing parameters Initialising global

Hi, I have a server which until recently was serving a domain of about 20 XP PCs in a school. Over the summer I updated Samba to 3.5.4-0.70, and replaced the desktops with new machines which are running Win7 Pro 64 bit SP1. This being a school, I have a system of mandatory group profiles set up, and all of the pupil groups curently have copies of the same mandatory profile (generated via the

On 2015-05-20 09:21, Timo Altun wrote: > Hi Davor, > > most of the domain accounts were part of an old NT4 domain. I did a > classicupgrade. > > Your theory with the NTUSER.DAT-files seemed so promising, > unfortunately that was not it. I created new accounts on an XP machine > and a Win7 machine and tried to join with them, but still receive the > same error. One of

Hello all, I guess that everyone knows the message "the trust relation between this workstation and the primary domain failed" when joining Win7 into samba domain. Unfortunately, the same problem appeared few hours/days after the machine was successfully joined in the domain(with reg keys from https://wiki.samba.org/index.php/Windows7) and user able to use it for awhile. Then at

Just the beginning of a question to anyone who might have experienced the following issue with Samba 3.0.2[5-6] series. We currently have service accounts accessing Samba shares on AIX 5.3 servers ( from TL04 - TL06 ). Most of the processes access the shares via UNC rather than mapped drives. After completing the upgrade to Samba 3.0.26a on the production side, the service accounts started

Hi Davor, I finally found it! After going through https://wiki.samba.org/index.php/Joining_a_Windows_Client_to_a_Domain , I checked the time settings on said clients and they differed from the AD DC too much. This also explains why some clients could join after a while...they synchronised with a NTP server after a day or so and then I was able to join. After that, joining the rest of clients was

Hi everyone, we have a funny problem connection from an XP machine to a 3.2.8 server. The level 10 log is copied in. Please look at the end of the log entries. Has anybody seen that kind of message?! Regards Volker --- [2009/02/16 13:15:08, 3] smbd/sec_ctx.c:set_sec_ctx(324) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2009/02/16 13:15:08, 5] auth/token_util.c:debug_nt_user_token(466)

Hi Davor, most of the domain accounts were part of an old NT4 domain. I did a classicupgrade. Your theory with the NTUSER.DAT-files seemed so promising, unfortunately that was not it. I created new accounts on an XP machine and a Win7 machine and tried to join with them, but still receive the same error. One of the machines I'm not able to join with, wasn't even part of the domain

I've been running samba on RHEL5 for the past couple of years with XP clients. Late last year, in order to support new Win7 clients, I upgraded from samba-3.0.33 packages to samba3x-3.3.8 (from the Red Hat-managed configuration tree) and after some struggles got everything working. But now after upgrading to samba3x-3.5.4 I am only able to connect as a known user and not as a guest. Relevant

Hi Davor, thanks for the answer. They were actually part of a NT4 domain called mayweg.net (the new realm name). But I did join workgroup "WORKGROUP" before I tried to join the new domain. If it's possible that they're sending the information the wrong way because they were part of a workgroup named after the new realm, is there any way to clear the old data (apart from a new

Hi Folks, I've fresh installed CentOS 5.5 and realized, that Samba is in version 3.0.33-3. Is it possible to conect WIN7 in a Samba-Dom?ne with this version? And I've read abaut RHEL 5.6 with samba 3.5.4. Can I expect, that this version is included in CentOS 5.6? And can I get this version with yum-update? Thx Timothy

Hi, I'm having a problem getting my Windows machines to access shares in Samba. When they browse to the Samba box it sometimes gives them an error saying that they don't have permission or that the server is unavailable. However this doesn't always happen and other times it lists the shares. When I try to access the shares it just prompts for the username/password over and over.

Hi there I am setting up a PDC with Centos 5 + Samba 3.5.4 + Openldap with Roaming profiles using kixstart tools to mount shared folder and modifing some registry entries on windows workstations, The Roaming profiles works fine between Win2000 and WinXP. but when I tried to join a Win7 or Vista workstations i get mixed errors. Sometimes the profiles loads sometimes not, or loads badly

Thank you for your reply. This was not a random link I followed. I have reviewed the Samba documentation at https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller, and all the testing that is listed there results in correct and expected answers... I had already noted the /etc/hosts situation, which interestingly does not change the answers I get in testing