Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: 1 [2]
16
Installation and Upgrades / Re: Zentyal 3 - Cannot join Domain with Windows 7 pro client
« on: February 05, 2013, 09:09:21 pm »
Push ...
Does anybody have an idea, what might be wrong?
Please help,
Ralf
Does anybody have an idea, what might be wrong?
Please help,
Ralf
17
Installation and Upgrades / Re: Zentyal 3 - Cannot join Domain with Windows 7 pro client
« on: January 26, 2013, 10:33:00 pm »
Hi,
thank you all for your replies.
I did a totally new and fresh install today with the latest Zentyal 3 installation image 32bit. I think, I followed all the instructions I got in the past:
- static IP address for local lan
- Enabled NTP server and succesfully syncing the client
- Fixed DNS server in lan adapter configuration
- Flushing DNS Cache on the client with ipconfig /flushdns
- of course I entered the the FQDN, in my case SOLARIS.HOME as domain name , there is no .lan extension in the domain name
- client can connect to the server and to the internet
- Configuration of network adapters, DNS and NTP before installing file sharing packages
- prepared the build-in Administrator user changing its password to something I know and verify to be member of group Domain Admins
- ...
But my problem still exists! Trying to join the domain, there is no login box, but only this message (details part, now in english):
This is my dig output on the server, similar to that one on my linux client, when connected to the server:
and
Maybe, there is a DNS issue I didn't recognized, yet?
Any idea?
Thank you all for help,
Ralf
PS: @daniellench: did you installed 64bit or 32bit version of Zentyal? I heard about some guys, that they were successful using 64bit version. But my prefered hardware is restricted to use 32bit version of Zentyal.
thank you all for your replies.
I did a totally new and fresh install today with the latest Zentyal 3 installation image 32bit. I think, I followed all the instructions I got in the past:
- static IP address for local lan
- Enabled NTP server and succesfully syncing the client
- Fixed DNS server in lan adapter configuration
- Flushing DNS Cache on the client with ipconfig /flushdns
- of course I entered the the FQDN, in my case SOLARIS.HOME as domain name , there is no .lan extension in the domain name
- client can connect to the server and to the internet
- Configuration of network adapters, DNS and NTP before installing file sharing packages
- prepared the build-in Administrator user changing its password to something I know and verify to be member of group Domain Admins
- ...
But my problem still exists! Trying to join the domain, there is no login box, but only this message (details part, now in english):
Code: [Select]
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.
DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain SOLARIS.HOME:
The query was for the SRV record for _ldap._tcp.dc._msdcs.SOLARIS.HOME
The following domain controllers were identified by the query:
deep-thought.solaris.home
Common causes of this error include:
- Host (A or AAAA) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or are not running.
For information about correcting this problem, click Help.
This is my dig output on the server, similar to that one on my linux client, when connected to the server:
Code: [Select]
root@deep-thought:/home/localadmin# dig deep-thought.solaris.home
; <<>> DiG 9.8.1-P1 <<>> deep-thought.solaris.home
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4003
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 1
;; QUESTION SECTION:
;deep-thought.solaris.home. IN A
;; ANSWER SECTION:
deep-thought.solaris.home. 259200 IN A 192.168.0.200
deep-thought.solaris.home. 259200 IN A 192.168.10.253
;; AUTHORITY SECTION:
solaris.home. 900 IN NS deep-thought.solaris.home.
;; ADDITIONAL SECTION:
deep-thought.solaris.home. 900 IN AAAA ::1
;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Jan 26 22:27:32 2013
;; MSG SIZE rcvd: 117
and
Code: [Select]
root@deep-thought:/home/localadmin# dig -x 192.168.0.200
; <<>> DiG 9.8.1-P1 <<>> -x 192.168.0.200
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19234
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3
;; QUESTION SECTION:
;200.0.168.192.in-addr.arpa. IN PTR
;; ANSWER SECTION:
200.0.168.192.in-addr.arpa. 259200 IN PTR deep-thought.solaris.home.
;; AUTHORITY SECTION:
0.168.192.in-addr.arpa. 259200 IN NS deep-thought.solaris.home.
;; ADDITIONAL SECTION:
deep-thought.solaris.home. 259200 IN A 192.168.0.200
deep-thought.solaris.home. 259200 IN A 192.168.10.253
deep-thought.solaris.home. 900 IN AAAA ::1
;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Jan 26 22:29:47 2013
;; MSG SIZE rcvd: 157
Maybe, there is a DNS issue I didn't recognized, yet?
Any idea?
Thank you all for help,
Ralf
PS: @daniellench: did you installed 64bit or 32bit version of Zentyal? I heard about some guys, that they were successful using 64bit version. But my prefered hardware is restricted to use 32bit version of Zentyal.
18
Installation and Upgrades / Re: Zentyal 3 - Cannot join Domain with Windows 7 pro client
« on: January 17, 2013, 04:11:01 pm »
Hi, Jason,
yes, when I use SOLARIS.HOME, I immediately get the second error "An Active Directory ...", even if I use static or dynamic DNS addresses.
When I enter SOLARIS, I get the login box, but then the other error occurs "The following error occured ...".
With Zentyal 2.2 I get the login box and after a while I get the welcome message, that I successful joined the domain.
Following that post you linked, it seems, that you has disabled firewall? Mh, I don't think that this would be good for me, because I want to use the routers WLAN to provide an internet connection for visitors outside of my private network.
Should I try to disable firewall for testing purposes?
Regards,
Ralf
yes, when I use SOLARIS.HOME, I immediately get the second error "An Active Directory ...", even if I use static or dynamic DNS addresses.
When I enter SOLARIS, I get the login box, but then the other error occurs "The following error occured ...".
With Zentyal 2.2 I get the login box and after a while I get the welcome message, that I successful joined the domain.
Following that post you linked, it seems, that you has disabled firewall? Mh, I don't think that this would be good for me, because I want to use the routers WLAN to provide an internet connection for visitors outside of my private network.
Should I try to disable firewall for testing purposes?
Regards,
Ralf
19
Installation and Upgrades / Re: Zentyal 3 - Cannot join Domain with Windows 7 pro client
« on: January 16, 2013, 06:40:52 pm »
@jase:
Thank you for your hint.
I did, what you suggests and changed the time synchronisation to use Zentyal NTP. Sorry, I not previously observed that I should configure the Win 7 client to sync with the server. Interesting, when I entered the IP of the server, sync failed but entering the full qualified server name, sync works and time of client and server is in sync.
Than I did another try to join the domain. And just one(!) time, the login box came up but the process failed again with the error message I posted in my first post. No changes. All further tries without the login box an the same message. Mh.
@Kurtis:
I don't know, if your problem is related to mine, but the severity just was changed to "critcal"
. Which version did you install? 32bit or 64bit?
Regards,
Ralf
Thank you for your hint.
I did, what you suggests and changed the time synchronisation to use Zentyal NTP. Sorry, I not previously observed that I should configure the Win 7 client to sync with the server. Interesting, when I entered the IP of the server, sync failed but entering the full qualified server name, sync works and time of client and server is in sync.
Than I did another try to join the domain. And just one(!) time, the login box came up but the process failed again with the error message I posted in my first post. No changes. All further tries without the login box an the same message. Mh.
@Kurtis:
I don't know, if your problem is related to mine, but the severity just was changed to "critcal"
. Which version did you install? 32bit or 64bit?Regards,
Ralf
20
Installation and Upgrades / Re: Zentyal 3 - Cannot join Domain with Windows 7 pro client
« on: January 15, 2013, 11:08:49 pm »
Hi, ichat,
Thank you for reply.
OK, here is my configuration:
My Zentyal box is dhcp server, dns server, ntp server and wins server:
- DHCP enabled on eth1 (internal network device with ip 192.168.0.200)
- DNS domain: solaris.home, ip address: 192.168.0.200, host: deep-thought with ip 192.168.0.200
- NTP enabled: local Zentyal NTP
- WINS enabled: local Zentyal
My client is connected directly to the internal network device of the server. The external network device points to the internet dsl router. DHCP on the external network device is disabled.
my client uses an ip address from the internal network static or alternatively dynamically.
A nslookup deep-thought on the client resolves to deep-thought.solaris.home .
A nslookup 192.168.0.200 (servers internal ip address) resolves to deep-thought.solaris.home, too.
When I try to join the domain with its netbios name, the login box comes up to enter domain admins credentials but it fails with the following error message (German):
But I think, this is the wrong way, because of samba 4 likes to get the FQDN?
Hope that helps.
Thank you very much!
Rergards
Ralf
Thank you for reply.
OK, here is my configuration:
My Zentyal box is dhcp server, dns server, ntp server and wins server:
- DHCP enabled on eth1 (internal network device with ip 192.168.0.200)
- DNS domain: solaris.home, ip address: 192.168.0.200, host: deep-thought with ip 192.168.0.200
- NTP enabled: local Zentyal NTP
- WINS enabled: local Zentyal
My client is connected directly to the internal network device of the server. The external network device points to the internet dsl router. DHCP on the external network device is disabled.
my client uses an ip address from the internal network static or alternatively dynamically.
A nslookup deep-thought on the client resolves to deep-thought.solaris.home .
A nslookup 192.168.0.200 (servers internal ip address) resolves to deep-thought.solaris.home, too.
When I try to join the domain with its netbios name, the login box comes up to enter domain admins credentials but it fails with the following error message (German):
Code: [Select]
Bei dem Versuch der Doäne "SOLARIS" beizutreten, trat folgender Fehler auf: Die angeebene Domäne ist nicht vorhanden, oder es konnte keine Verbindung hergestellt werden.But I think, this is the wrong way, because of samba 4 likes to get the FQDN?
Hope that helps.
Thank you very much!
Rergards
Ralf
21
Installation and Upgrades / Re: Zentyal 3 - Cannot join Domain with Windows 7 pro client
« on: January 15, 2013, 12:10:02 pm »
Hallo Jason,
thank you very much for your reply!
Yes, I'm using the realm of Zentyal ("SOLARIS.HOME") and I get the message I posted above, nothing else.
I also didn't get any login box, where I have to enter the credentials of a domain admin, as I expected.
Just only that message that maybe is related to some problems with DNS, I guess.
The login box for the credentials of the domain admin only comes up, when I just only would enter "SOLARIS" as the domain name, but for samba4, that would be wrong and without any success.
And, as you can see, the client recognizes the server: "deep-thought.solaris.home".
Before I tryed to join the domain, I did an ipconfig /flushdns to avoid, that the client keeps some information from a former server installation (Zentyal 2.2). I also played around with fix ip addresses and fix DNS gateway or DHCP but fix DNS gateway but nothing helped.
The server can be pinged with its name or ip, I also can reach the internet through the server.
I read about some guys who where successful with 64bit version of Zentyal. But my preferred hardware does not support 64bit. Possible, that a change to 64bit might be helpful?
Regards
Ralf
thank you very much for your reply!
Yes, I'm using the realm of Zentyal ("SOLARIS.HOME") and I get the message I posted above, nothing else.
I also didn't get any login box, where I have to enter the credentials of a domain admin, as I expected.
Just only that message that maybe is related to some problems with DNS, I guess.
The login box for the credentials of the domain admin only comes up, when I just only would enter "SOLARIS" as the domain name, but for samba4, that would be wrong and without any success.
And, as you can see, the client recognizes the server: "deep-thought.solaris.home".
Before I tryed to join the domain, I did an ipconfig /flushdns to avoid, that the client keeps some information from a former server installation (Zentyal 2.2). I also played around with fix ip addresses and fix DNS gateway or DHCP but fix DNS gateway but nothing helped.
The server can be pinged with its name or ip, I also can reach the internet through the server.
I read about some guys who where successful with 64bit version of Zentyal. But my preferred hardware does not support 64bit. Possible, that a change to 64bit might be helpful?
Regards
Ralf
22
Installation and Upgrades / [SOLVED] Zentyal 3 - Cannot join Domain with Windows 7 pro client
« on: January 14, 2013, 10:01:44 pm »
Hallo all,
I'm still not able to join a Windows 7 pro client into a samba domain.
After returned to Zentyal 2.2 a gave Zentyal 3 another chance, after I found this information because it's exactly the scenario I have:
http://trac.zentyal.org/wiki/Documentation/Community/Development/singlez
I also found this: http://forum.zentyal.org/index.php/topic,13501.msg55949.html#msg55949 as an additional information that I have to configure static DNS informations to the network adapter, related to this informations http://wiki.samba.org/index.php/Samba4, but after exactly followed the instructions I still get this error, when I try to join the domain:
Sorry, that this message is in German but I hope, you know, what it might means.
I did a fresh install from the latest Zentyal installation image (32bit) and installed all updates.
nslookups from the Windows client was successful with server name an DNS domain name, but not with the IP address. Strange?
By the way: To join the domain using Zentyal 2.2 and following the well known instructions succeeded at once.
Maybe somebody can help me find the faults?
Thank you very much,
Ralf
I'm still not able to join a Windows 7 pro client into a samba domain.
After returned to Zentyal 2.2 a gave Zentyal 3 another chance, after I found this information because it's exactly the scenario I have:
http://trac.zentyal.org/wiki/Documentation/Community/Development/singlez
I also found this: http://forum.zentyal.org/index.php/topic,13501.msg55949.html#msg55949 as an additional information that I have to configure static DNS informations to the network adapter, related to this informations http://wiki.samba.org/index.php/Samba4, but after exactly followed the instructions I still get this error, when I try to join the domain:
Code: [Select]
Hinweis: Diese Informationen sind für einen Netzwerkadministrator bestimmt. Wenden Sie sich an den Netzwerkadministrator, wenn Sie kein Netzwerkadministrator sind, und leiten Sie die Informationen in der Datei C:\Windows\debug\dcdiag.txt weiter.
Die DNS-Abfrage über den Ressourceneintrag der Dienstidentifizierung (SRV), der zur Suche eines Domänencontrollers für die Domäne "SOLARIS.HOME" verwendet wird, wurde erfolgreich abgeschlossen:
Es handelt sich um die Abfrage des SRV-Eintrags für _ldap._tcp.dc._msdcs.SOLARIS.HOME.
Die folgenden Domänencontroller wurden von der Abfrage identifiziert:
deep-thought.solaris.home
Es konnte jedoch keine Verbindung mit Domänencontrollern hergestellt werden.
Die häufigsten Ursachen dieses Fehlers sind:
- Hosteinträge (A oder AAAA), die die Namen der Domänencontroller deren IP-Adressen zuordnen, fehlen oder enthalten nicht die richtigen Adressen.
- Die in DNS registrierten Domänencontroller verfügen nicht über eine Netzwerkverbindung oder werden nicht ausgeführt.Sorry, that this message is in German but I hope, you know, what it might means.
I did a fresh install from the latest Zentyal installation image (32bit) and installed all updates.
nslookups from the Windows client was successful with server name an DNS domain name, but not with the IP address. Strange?
By the way: To join the domain using Zentyal 2.2 and following the well known instructions succeeded at once.
Maybe somebody can help me find the faults?
Thank you very much,
Ralf
23
German / Re: SOGo 2.0 auf Zentyal 3.0 und Sieve
« on: January 06, 2013, 09:44:38 pm »
Hello all,
I've stopped playing around with SOGo on Zentyal 3 because off several different problems - not only to make SOGo properly run, but also joining a Win 7 pro client into the SAMBA domain, which was very disappointing to me.
Now give Zentyal 2.2 a try without any groupware for the moment.
Happy new year,
Ralf
I've stopped playing around with SOGo on Zentyal 3 because off several different problems - not only to make SOGo properly run, but also joining a Win 7 pro client into the SAMBA domain, which was very disappointing to me.
Now give Zentyal 2.2 a try without any groupware for the moment.
Happy new year,
Ralf
24
German / Re: Performance der Weboberfläche
« on: November 03, 2012, 01:31:11 pm »
Hallo Bernhard,
vielen Dank für Deine Antwort.
Die Seite kommt sofort mit http://serverIP. Das geht sogar bereits remote und genauso schnell, wie erwartet.
Das ist ja der Standard-Port und die Standard-Adresse des Apache-Webservers. Der Inhalt ist aber auch gering. Es ist noch gar kein Content hinterlegt. Ist quasi die initiale Startseite nach Installation eines Apache.
Ich war aber auch der Meinung, der Zentyal bringt für die Verwaltung einen eigenen Webserver mit.
Grüße,
Ralf
vielen Dank für Deine Antwort.
Die Seite kommt sofort mit http://serverIP. Das geht sogar bereits remote und genauso schnell, wie erwartet.
Das ist ja der Standard-Port und die Standard-Adresse des Apache-Webservers. Der Inhalt ist aber auch gering. Es ist noch gar kein Content hinterlegt. Ist quasi die initiale Startseite nach Installation eines Apache.
Ich war aber auch der Meinung, der Zentyal bringt für die Verwaltung einen eigenen Webserver mit.
Grüße,
Ralf
25
German / Performance der Weboberfläche
« on: October 15, 2012, 04:17:33 pm »
Hallo,
ich freunde mich ja gerade mit Zentyal an ;-)
Nun habe ich die Beobachtung gemacht, dass die Weboberfläche, die ich zur Zeit noch lokal auf dem Server benutze, ziemlich lahm ist und enorm Performance frisst. Ist das normal? Man kann bei jeder Änderung, sprich zum Beispiel Wechsel zu einem Modul sehen, wie im Addon der Desktop-Oberfläche (unten rechts) die CPU-Leistung in die Höhe schießt.
Habe schon mal irgendwo gelesen, bei Verbindungen von außen könnte es ein Cache-Problem mit den Seitenelementen sein - klar. Aber wenn alles lokal läuft und ich schon X mal in der Weboberfläche war, kann das ja nicht mehr sein.
So schlapp ist meine Kiste doch gar nicht. P4 mit 3GHz, 2GB Ram.
Herzliche Grüße von,
Ralf
ich freunde mich ja gerade mit Zentyal an ;-)
Nun habe ich die Beobachtung gemacht, dass die Weboberfläche, die ich zur Zeit noch lokal auf dem Server benutze, ziemlich lahm ist und enorm Performance frisst. Ist das normal? Man kann bei jeder Änderung, sprich zum Beispiel Wechsel zu einem Modul sehen, wie im Addon der Desktop-Oberfläche (unten rechts) die CPU-Leistung in die Höhe schießt.
Habe schon mal irgendwo gelesen, bei Verbindungen von außen könnte es ein Cache-Problem mit den Seitenelementen sein - klar. Aber wenn alles lokal läuft und ich schon X mal in der Weboberfläche war, kann das ja nicht mehr sein.
So schlapp ist meine Kiste doch gar nicht. P4 mit 3GHz, 2GB Ram.
Herzliche Grüße von,
Ralf
26
German / Re: [gelöst] Zarafa - Fragen zu Email-Alias und senden
« on: October 15, 2012, 03:55:09 pm »
Hallo Rosi,
vielen Dank. Dein Post hat mir sehr geholfen, allerdings bei mir hat der Teil mit der Einbindung der access-Datei bereits gereicht.
Ich habe drei verschiedene offizielle Domains, die nun auch relayen dürfen.
[Edit:] Ich benutze kein Zafara ...
Aber wäre das nicht irgendwie sinnvoll, wenn man so was auch über die Weboberfläche konfigurieren könnte? Das man mit offiziellen Adressen über den Zentyal relayen möchte ist doch eher die Regel, als die Ausnahme.
Grüße,
Ralf
vielen Dank. Dein Post hat mir sehr geholfen, allerdings bei mir hat der Teil mit der Einbindung der access-Datei bereits gereicht.
Ich habe drei verschiedene offizielle Domains, die nun auch relayen dürfen.
[Edit:] Ich benutze kein Zafara ...
Aber wäre das nicht irgendwie sinnvoll, wenn man so was auch über die Weboberfläche konfigurieren könnte? Das man mit offiziellen Adressen über den Zentyal relayen möchte ist doch eher die Regel, als die Ausnahme.
Grüße,
Ralf
27
German / Re: SOGo 2.0 auf Zentyal 3.0 und Sieve
« on: October 15, 2012, 03:45:47 pm »
@christian: Happy to hear about that. I myself made some new experiences, too.
To use SOGo Connector it seems to be important to log in at an external thunderbird client with with username only, without the domain part. Because of that, I had to modify dovcot-ldap.conf.mas.
SOGo Connector seems to use the username used to connect to the imap server to generate the path to the calendar and addressbook sources.
It works for me for the moment, but I'm not realy shure this is the best way.
Thanks for sharing,
Ralf
To use SOGo Connector it seems to be important to log in at an external thunderbird client with with username only, without the domain part. Because of that, I had to modify dovcot-ldap.conf.mas.
SOGo Connector seems to use the username used to connect to the imap server to generate the path to the calendar and addressbook sources.
Code: [Select]
#pass_filter = (&(objectClass=CourierMailAccount)(mail=%u))
pass_filter = (&(objectClass=posixAccount)(uid=%n))
pass_attrs = mail=user,userPassword=password
It works for me for the moment, but I'm not realy shure this is the best way.
Thanks for sharing,
Ralf
28
German / Re: SOGo 2.0 auf Zentyal 3.0 und Sieve
« on: October 11, 2012, 06:35:14 pm »
Hi, FarquahrWindsor,
thank you for your reply. Sorry that I couldn't answer but first of all, I had to repair some faulty configurations before trying other things. No I tried with user ebox and its password out of the secret-file but that doesn't worked.
Any idea?
Who is the sieve administrator on an Zentyal-Installation an what is the password?
Does anybody found a solution for this problem?
It's not as serious, but I think, it's a nice chalange to make it run.
Thanks for everybody, who has an idea!
Ralf
Hi, FarquahrWindsor,
vielen Dank für Deine Antwort. Sorry, dass ich noch nicht antworten konnte, aber ich musste zunächst fehlerhafte Einstellungen reparieren, bevor ich was neues ausprobiere. Nun habe ich es mit dem ebox-User und seinem Kennwort aus der secret-Datei versucht, aber es funktioniert auch nicht.
Jemand eine Idee?
Wer ist der sieve Administrator auf einer Zentyal-Installation und was ist sein Kennwort?
Hat jemand bereits eine Lösung für das Problem?
Es ist nicht sehr schwerwiegend, aber eine nette Herausforderung, es zum Laufen zu bekommen.
Vielen Dank im Voraus für weitere Anregungen!
Ralf
thank you for your reply. Sorry that I couldn't answer but first of all, I had to repair some faulty configurations before trying other things. No I tried with user ebox and its password out of the secret-file but that doesn't worked.
Any idea?
Who is the sieve administrator on an Zentyal-Installation an what is the password?
Does anybody found a solution for this problem?
It's not as serious, but I think, it's a nice chalange to make it run.
Thanks for everybody, who has an idea!
Ralf
Hi, FarquahrWindsor,
vielen Dank für Deine Antwort. Sorry, dass ich noch nicht antworten konnte, aber ich musste zunächst fehlerhafte Einstellungen reparieren, bevor ich was neues ausprobiere. Nun habe ich es mit dem ebox-User und seinem Kennwort aus der secret-Datei versucht, aber es funktioniert auch nicht.
Jemand eine Idee?
Wer ist der sieve Administrator auf einer Zentyal-Installation und was ist sein Kennwort?
Hat jemand bereits eine Lösung für das Problem?
Es ist nicht sehr schwerwiegend, aber eine nette Herausforderung, es zum Laufen zu bekommen.
Vielen Dank im Voraus für weitere Anregungen!
Ralf
29
German / SOGo 2.0 auf Zentyal 3.0 und Sieve [not solved but closed]
« on: October 06, 2012, 08:38:31 pm »
Hallo,
ich hoffe, ich bin hier richtig. Ich konfiguriere zur Zeit SOGo 2.0 auf einem frisch installierten Zentyal. Nun möchte ich die Abwesenheitsfunktion mit automatischer Beendigung einrichten, Stichwort "Vacation messages expiration" in der SOGo-Doku.
Für SOGo gibt es da einen Cron-Job, den man verwenden soll:
Nun ist es mir ein Rätsel, was ich für authname:authpassword verwenden soll.
Welche Anmeldeinformtionen unter Zentyal entsprechen denen für den Sieve Administrator?
Ich habe auch schon den Ansatz gefunden, die Dovecot-Konfiguration anzupassen und einen "Master"-User anzulegen, aber das scheint bei Zentyal ja nicht so einfach zu sein, da zum einen die Userdaten ja aus der LDAP-Konfig gezogen werden, und bei jeden Start von Zentyal die Konfiguration offenbar neu geschrieben wird.
Hat hier schon mal jemand die Funktion erfolgreich mit SOGo auf Zentyal umgesetzt?
Hier noch die Meldung, die ich bekomme, wenn ich als User "sogo" den Cron-Befehl manuell mit beliebigen Anmeldeinfos versuche:
Befehl:
"username" und "myhost.mydomain" sind Dummies, die real natürlich den echten Gegebenheiten entsprechen.
Immerhin scheint das Skript zu erkennen, das username eine Abwesenheitsmeldung geschaltet hat.
Bin für jede Hilfe dankbar,
Grüße,
Ralf
ich hoffe, ich bin hier richtig. Ich konfiguriere zur Zeit SOGo 2.0 auf einem frisch installierten Zentyal. Nun möchte ich die Abwesenheitsfunktion mit automatischer Beendigung einrichten, Stichwort "Vacation messages expiration" in der SOGo-Doku.
Für SOGo gibt es da einen Cron-Job, den man verwenden soll:
Code: [Select]
0 0 * * * sogo /usr/sbin/sogo-tool expire-autoreply authname:authpassword"SIEVE-Skripte verwalten" habe ich in Zentyal angehakt.Nun ist es mir ein Rätsel, was ich für authname:authpassword verwenden soll.
Welche Anmeldeinformtionen unter Zentyal entsprechen denen für den Sieve Administrator?
Ich habe auch schon den Ansatz gefunden, die Dovecot-Konfiguration anzupassen und einen "Master"-User anzulegen, aber das scheint bei Zentyal ja nicht so einfach zu sein, da zum einen die Userdaten ja aus der LDAP-Konfig gezogen werden, und bei jeden Start von Zentyal die Konfiguration offenbar neu geschrieben wird.
Hat hier schon mal jemand die Funktion erfolgreich mit SOGo auf Zentyal umgesetzt?
Hier noch die Meldung, die ich bekomme, wenn ich als User "sogo" den Cron-Befehl manuell mit beliebigen Anmeldeinfos versuche:
Befehl:
Code: [Select]
/usr/sbin/sogo-tool expire-autoreply sieve:SECRETErgebnisCode: [Select]
Oct 06 18:48:53 sogo-tool [11560]: <0x0x8b70370[SOGoCache]> Cache cleanup interval set every 300.000000 seconds
Oct 06 18:48:53 sogo-tool [11560]: <0x0x8b70370[SOGoCache]> Using host(s) 'localhost' as server(s)
2012-10-06 18:48:53.176 sogo-tool[11560] failure. Attempting with a renewed password (no authname supported)
2012-10-06 18:48:53.177 sogo-tool[11560] Could not login 'username' on Sieve server: <0x0x8ba3da8[NGSieveClient]: socket=<NGActiveSocket[0x0x8ba8b10]: mode=rw address=<0x0x8baa718[NGInternetSocketAddress]: host=localhost.localdomain port=42376> connectedTo=<0x0x8ba62a8[NGInternetSocketAddress]: host=myhost.mydomain port=4190>>>: (null)
2012-10-06 18:48:53.182 sogo-tool[11560] An error occured while removing auto-reply of user username
"username" und "myhost.mydomain" sind Dummies, die real natürlich den echten Gegebenheiten entsprechen.
Immerhin scheint das Skript zu erkennen, das username eine Abwesenheitsmeldung geschaltet hat.
Bin für jede Hilfe dankbar,
Grüße,
Ralf
30
Installation and Upgrades / Re: Starting modules stops after upgdating vom clean 3.0 to 3.0.1
« on: September 24, 2012, 10:19:40 pm »
Hi all,
I'm totally new at zentyal and I got these problems on a fresh install of zentyal, too.Thank you for this workaround but I think, this value for sleep is too much.
For me sleep 10 works fine, but I agree with you, this only can be a temporary solution.
Hope for an update.
Ralf
I'm totally new at zentyal and I got these problems on a fresh install of zentyal, too.Thank you for this workaround but I think, this value for sleep is too much.
For me sleep 10 works fine, but I agree with you, this only can be a temporary solution.
Hope for an update.
Ralf
Pages: 1 [2]