similar to: cannot update W7 or linux clients

Displaying 20 results from an estimated 9000 matches similar to: "cannot update W7 or linux clients"

2015 Jan 19
2
cannot update W7 or linux clients
Here yau go: root at dc01:~# cat /etc/bind/named.conf.options // Defined ACL Begin acl thisserverip { 192.168.16.54; }; acl all-networks { 192.168.16.0/24; }; // Defined ACL End options { directory "/var/cache/bind"; version "0.0.7"; // If there is a firewall between you and nameservers you want // to talk to, you may need to fix the firewall to allow multiple //
2015 Jan 09
3
getting NT_STATUS_LOGON_FAILURE
On 2015-01-09 08:44, Rowland Penny wrote: > On 09/01/15 14:34, Bob of Donelson Trophy wrote: > Now, more appropriately answering after the message. SEE BELOW, please. On 2015-01-09 07:24, L.P.H. van Belle wrote: Hai, Not entiraly correct.. change : dns-nameservers 208.67.222.222 <<<<<< have always struggled to dns-search dtshrm.lan dns-nameservers IP_OF_AD_DC and use :
2015 Jan 09
2
getting NT_STATUS_LOGON_FAILURE
On 09/01/15 17:26, Bob of Donelson Trophy wrote: > > > On 2015-01-09 10:23, Rowland Penny wrote: > >> On 09/01/15 15:47, Bob of Donelson Trophy wrote: >> >> On 2015-01-09 09:27, Rowland Penny wrote: >> >> On 09/01/15 15:00, Bob of Donelson Trophy wrote: >> On 2015-01-09 08:44, Rowland Penny wrote: W7 client "Preferred DNS server" is set
2015 Jan 09
2
getting NT_STATUS_LOGON_FAILURE
On 09/01/15 18:31, Bob of Donelson Trophy wrote: > > > On 2015-01-09 11:40, Rowland Penny wrote: > >> On 09/01/15 17:26, Bob of Donelson Trophy wrote: >> On 2015-01-09 10:23, Rowland Penny wrote: On 09/01/15 15:47, Bob of Donelson Trophy wrote: On 2015-01-09 09:27, Rowland Penny wrote: On 09/01/15 15:00, Bob of Donelson Trophy wrote: On 2015-01-09 08:44, Rowland Penny
2015 Jan 09
2
getting NT_STATUS_LOGON_FAILURE
On 09/01/15 18:56, Bob of Donelson Trophy wrote: > > > On 2015-01-09 12:45, Rowland Penny wrote: > >> On 09/01/15 18:31, Bob of Donelson Trophy wrote: >> On 2015-01-09 11:40, Rowland Penny wrote: On 09/01/15 17:26, Bob of Donelson Trophy wrote: On 2015-01-09 10:23, Rowland Penny wrote: On 09/01/15 15:47, Bob of Donelson Trophy wrote: On 2015-01-09 09:27, Rowland Penny
2015 Jan 09
2
getting NT_STATUS_LOGON_FAILURE
Now, more appropriately answering after the message. SEE BELOW, please. On 2015-01-09 07:24, L.P.H. van Belle wrote: > Hai, > > Not entiraly correct.. > > change : > >> dns-nameservers 208.67.222.222 <<<<<< have always struggled > > to > dns-search dtshrm.lan > dns-nameservers IP_OF_AD_DC > > and use : > net rpc rights
2015 Jan 09
1
getting NT_STATUS_LOGON_FAILURE
On 09/01/15 20:16, Bob of Donelson Trophy wrote: > > > On 2015-01-09 13:43, Rowland Penny wrote: > >> On 09/01/15 18:56, Bob of Donelson Trophy wrote: >> On 2015-01-09 12:45, Rowland Penny wrote: On 09/01/15 18:31, Bob of Donelson Trophy wrote: On 2015-01-09 11:40, Rowland Penny wrote: On 09/01/15 17:26, Bob of Donelson Trophy wrote: On 2015-01-09 10:23, Rowland Penny
2015 Jan 09
3
getting NT_STATUS_LOGON_FAILURE
I have been having issues with my W7 client "access is denied" to changing the security (user permissions) settings and have been posting regarding that issue yesterday. I have discovered that my "ads join member server" is not completely joined (I think.) I discovered a post from February 2014, by Louis "[Samba] member joined, but . . ." and ran some of his
2015 Jan 05
1
linux client join DC how?
On 05/01/15 14:04, Bob of Donelson Trophy wrote: > > > My shop is 10 minutes from my house. House and shop are connected by vpn > (between two IpFire firewalls.) I do a lot of configuring and testing > from home. Due to a Windows wake-on-lan issue (right now) I cannot wake > the lone DC W7 client from home. When I get to work this morning, W7 > client (thru ADUC) shows
2015 Jan 19
0
cannot update W7 or linux clients
On 19/01/15 20:30, Bob of Donelson Trophy wrote: > > > Here yau go: > > root at dc01:~# cat /etc/bind/named.conf.options > // Defined ACL Begin > acl thisserverip { > 192.168.16.54; > }; > acl all-networks { > 192.168.16.0/24; > }; > // Defined ACL End > > options { > directory "/var/cache/bind"; > version
2015 Jan 28
2
W7 client cannot adjust file permissions via ADUC
W7 client domain member? yes. Logged in as domainAdministrator? yes. "SeDiskOperatorPrivilege" set? yes Read "/Setup_and_configure_file_shares_with_Windows_ACLs"? yes. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [2] "Everyone deserves an award!!" On 2015-01-28 10:40, Marcel de Reuver wrote: >
2015 Feb 27
3
NT_STATUS_CONNECTION_REFUSED, again!!!
Thanks Rowland but that idea did not work. I will simply grant access to those that failed manually. (Really wish I had kept the VM that the scripthad worked on so I could go back and see what happened but, too late, I have already deleted to save precious hard drive space.) If I have any issues, I'll be back. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846
2015 Jan 30
2
W7 client cannot adjust file permissions via ADUC
On 30/01/15 20:48, Bob of Donelson Trophy wrote: > > > Okay, added 'gidNumber: 10000' to the domain users group on DC1. (Was > within my range 500-40000.) > > getnet passwd [user] returns nothing on DC1. > > W7 client still a "no". > > And now? > > Have you tried getent on the member server ? Lets forget W7 for the moment, get the Unix
2015 Feb 27
2
NT_STATUS_CONNECTION_REFUSED, again!!!
No. What I did was change the first few to see what happens. And still the first 13 (this time, last time 17) failed. I am baffled why the first 11 to 17 fail (randomly) and the remainder receive "Successfully granted rights." --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [1] "Everyone deserves an award!!" On
2015 Feb 27
2
NT_STATUS_CONNECTION_REFUSED, again!!!
Thanks Rowland. Being the novice that I am, I thought the line would 'pickup' my DOMAIN and replace the ${SAMBA_NT_DOMAIN}. So, I just tried the line correctly and it asked for my Administrator password and subsequently granted access. At least I know I can go and correct manually, if I need too. My /etc/resolv.conf is: root at dt01:~# cat /etc/resolv.conf search dts***m.dt
2015 Feb 27
2
NT_STATUS_CONNECTION_REFUSED, again!!!
At one point, I thought the same. Tried a "sleep 5" and still got some failures. (That was before I started counting the fails.) This is a P4 3.2Ghz with 1Gb RAM. Could it be that sluggish (at that moment) and need a "sleep 10" or "sleep 15" or more? It worked on my VM (of course it is running on a multi-core Xeon processor so maybe a sleep?) I'm going to try
2015 Feb 27
2
NT_STATUS_CONNECTION_REFUSED, again!!!
I thought I was over this the other day when I got it to work properly on my VM. Now, on an actual PC I am getting: ==========Test kerberos =============================== Lets test some things Testing : kerberos Password for Administrator at DTSHRM.DT: Warning: Your password will expire in 41 days on Fri Apr 10 08:43:58 2015 Ticket cache: FILE:/tmp/krb5cc_0 Default principal:
2015 Jan 30
1
W7 client cannot adjust file permissions via ADUC
On 30/01/15 21:19, Bob of Donelson Trophy wrote: > > > Both DC1 and member server return nothing on 'getent passwd > Administrator' > > I have no other users other than 'root' and 'Administrator' on all three > (DC1, DC2 & member.) > > My plan was to get file permissions (aka profiles) working and add some > test users. > > How do
2015 Jan 26
5
W7 client cannot adjust file permissions via ADUC
I have been improving my DC. I now have a DC01, DC02 and a DCMEMBER01. All running sernet-samba 4.1.16 on Debian 7.8.0 thanks to Louis' (old) scripts. (Any linux client work has gone on hold, for the moment.) Next step was to adjust the file permissions as instructed on "Setup and configure file shares with Windows ACLs". When I access the "Computer Management" (thru ADUC
2016 Oct 09
2
member server nslookup
I just transfered fsmo roles from one DC to my newer DC and all went well. Thank you Samba team!! Great documentation, BTW. My domain (basically) consists of one ADDC, one member server and two W10 clients and one W7 client. While setting up the newer DC had been running some nslookup on the DC's and decided to run nslookup on my member server and do not know if I have discovered and