similar to: Samba4 - Win7 RSAT tools - global catalog (GC) cannot be contacted

Displaying 20 results from an estimated 6000 matches similar to: "Samba4 - Win7 RSAT tools - global catalog (GC) cannot be contacted"

2013 Aug 15
2
Samba4 and iptables
Hi everyone, I had posted recently about getting Samba4 to work on CentOS 6.4 but having changes only replicating in one direction, from the Win2k3 AD but not back to it. I solved the problem, this time, by disabling iptables. I find it a bit hard to understand. These are the rules I have set up: *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [52:5888] -A INPUT -m state
2019 Jul 19
0
Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT
On 19/07/2019 11:13, Alfonso Conner via samba wrote: > Hi Samba Team, > > Have recently followed Samba guide and successfully migrate from PDC to AD > and from BDC to join AD forest. > Need some advice here as I encountered global catalog (GC) cannot be > contacted issue when using RSAT. > This message pops up when I click "member of" tab while viewing user >
2019 Jul 22
0
Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT
On 22/07/2019 01:21, Alfonso Conner wrote: > Hi Rowland, > > Currently using Samba 4.8.5 > 2 x DCs running on CentOS 6.10 (Final) > Configured 1 DC via classic upgrade, and the latter DC join AD forest. > Would it be alright if I were to redo the classic upgrade? You can if you want to, but I feel that your problem may have nothing to do with Samba. Your first problem is your
2019 Jul 22
0
Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT
On 22/07/2019 09:23, Alfonso Conner wrote: > Hi Rowland, > > In fact currently in my test environment using the same version of OS > 6.10 and Samba 4.8.5. > I ran 'netstat -plaunt | egrep "ntp|bind|named|samba|?mbd"', I have > :::3268, :::3269, I do not see 0.0.0.0:3268 <http://0.0.0.0:3268> and > 0.0.0.03269. > While I use a Windows PC join to my
2019 Jul 22
0
Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT
Hi Rowland, Just a curious question. Since the origin of my AD comes from PDC. If I were to try and do a classicupgrade, using same IP, same hostname, same realm, will my windows pc have login issues? Regards On Mon, Jul 22, 2019 at 5:04 PM Alfonso Conner <c1581634 at gmail.com> wrote: > Hi Rowland, > > Noted with thanks. > > Regards > > On Mon, Jul 22, 2019 at 4:31
2019 Jul 22
1
Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT
On 22/07/2019 10:24, Alfonso Conner wrote: > Hi Rowland, > > Just a curious question. > Since the origin of my AD comes from PDC. If I were to try and do a > classicupgrade, using same IP, same hostname, same realm, will my > windows pc have login issues? > To be honest, I am not entirely sure, you should get the same results every time you run the classicupgrade, so your
2019 Jul 22
2
Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT
Hi Rowland, Noted with thanks. Regards On Mon, Jul 22, 2019 at 4:31 PM Rowland penny via samba < samba at lists.samba.org> wrote: > On 22/07/2019 09:23, Alfonso Conner wrote: > > Hi Rowland, > > > > In fact currently in my test environment using the same version of OS > > 6.10 and Samba 4.8.5. > > I ran 'netstat -plaunt | egrep
2019 Jul 22
2
Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT
Hi Rowland, Currently using Samba 4.8.5 2 x DCs running on CentOS 6.10 (Final) Configured 1 DC via classic upgrade, and the latter DC join AD forest. Would it be alright if I were to redo the classic upgrade? Hope to hear from you soon. Thanks and Regards On Fri, Jul 19, 2019 at 7:06 PM Rowland penny via samba < samba at lists.samba.org> wrote: > On 19/07/2019 11:13, Alfonso Conner
2019 Jul 22
2
Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT
Hi Rowland, In fact currently in my test environment using the same version of OS 6.10 and Samba 4.8.5. I ran 'netstat -plaunt | egrep "ntp|bind|named|samba|?mbd"', I have :::3268, :::3269, I do not see 0.0.0.0:3268 and 0.0.0.03269. While I use a Windows PC join to my test domain, I have no issues with GC. Not sure how the GC problem can happen but seems to me it looks like a
2019 Jul 19
2
Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT
Hi Samba Team, Have recently followed Samba guide and successfully migrate from PDC to AD and from BDC to join AD forest. Need some advice here as I encountered global catalog (GC) cannot be contacted issue when using RSAT. This message pops up when I click "member of" tab while viewing user properties although it will display correctly after I acknowledged the error. Another similar
2013 May 21
1
samba4 AD - strange slowness after enable iptables based firewall
Hi; I sucesyfully ran AD on samba4 software. All required by me functions works properly but when I turn on firewall my enviroment is getting very slow - logon process is 3 times longer then on system with disabled firewall service. Below I pasted my firewall configuration - I based on samba tutorial and aexples and official microsoft web page with needed ports: Have you similar problems after
2009 Aug 03
3
firewall question
My firewall config is below... I am trying to figure out why another machine has access to port 5038 on my machine based on these firewall rules. I thought the reject at the bottom would take care of all other ports? It does not. I have restarted with "server iptables restart" and same thing. I can connect from another machine to my machine on port 5038. How do I prevent this?
2009 Aug 04
4
firewall setup for nfs
Below is my firewall rules for iptables. everything is working fine except for NFS I cannot mount my drive. If I turn off iptables I can mount. Looking at this : http://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-nfs.html Important In order for NFS to work with a default installation of Red Hat Enterprise Linux with a firewall enabled, IPTables with the default TCP port 2049
2019 Feb 12
1
Samba and ufw (Martin McGlensey)
Louis, Made the changes. Still unable to mount office. Firewall also blocks Thunderbird mail and maybe internet. Will check that more fully later.Any thoughts ob Tony's response? Outputs: martin at radio:/etc$ sudo apt-get install ufw Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no
2005 Apr 11
3
Default Firewall Entries
Hello CentOS, I'm curious... there seems to be a couple of default firewall rules that I'm not familiar with in the CentOS 4.0 # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD
2019 Feb 06
2
Samba and ufw
Rowland, Did some editing in smb.conf that I had to reverse. Now I'm back to being able to connect with the firewall disabled. When I enable the firewall I get as far as windows network -> workgroup but no connection. I have only the rules you recommended in your last email. Louis, The information you requested is below: martin at radio:~$ dpkg -l|egrep "iptables|ufw" iiĀ 
2008 Feb 26
1
/etc/sysconfig/iptables on a stock CentOS 5 install
Greetings: i have a pretty stock CentOS 5 machine with ports 80 and 22 exposed, so my /etc/sysconfig/iptables file is pretty standard/straightforward. my question is: how is this config file initially generated? i'd like to re-create it, and add a couple of rules .... so i don't want to lose what's in there already. i see that my /etc/sysconfig/system-config-securitylevel has
2007 Apr 27
0
kernel 2.6.21 on centos 5
I have a computer that I needed to put 2.6.21 on. Everything is working fine after recompile except when iptables is starting up it errors with iptables-restore: line 23 failed. This is the normal centos 5 iptables. nothing special. What might I be missing in the new kernel that I get this error? Thanks, The file is below. Jerry --------------------------------------- # Firewall configuration
2006 Apr 27
0
Iptables
Hi, I have a problem related to the iptables, when I turn on the iptables the dhcp doesn''t work! This only happens if I boot the xen kernel, if I boot the default kernel it works just fine! In both I have the iptables active. My configuration is this: :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A
2004 Dec 29
18
No response on port 80 with Shorewall
I have problem getting answer on http request from all my local subnets but not from local subnet. Ping and requests on ports 21 22 23 25 110 works fine. I logged port 80 in rules files and I got accept entry same for local subnet and other subnets. Local subnet is 192.168.6 Dec 29 09:52:40 zinfsrv2 kernel: Shorewall:loc2fw:ACCEPT:IN=eth0 OUT= MAC=00:09:6b:07:ca:cc:00:10:b5:fa:bd:71:08:00