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.


Messages - shahsx

Pages: [1] 2
1
I have recently upgraded from Zentyal 3.2 --> 3.5--> 4.06.  Although most things ran smoothly there were a few glitches that I am trying to rectify now.

When I was upgrading from 3.5 to 4.0 I noticed that the admin port was not being changed to port 8443 and remained at port 443. After some investigation I saw the Groupware Services (Zarafa) was still there under Network Services and had port 8443 assigned to it.  So I manually changed the webadmin port to port 8445 and ran the upgrade. After the upgrade I changed the admin port to 8440 to see if it would change the Zentyal Webadmin service port to 8440. However I now have two Zentyal Webadmin Service under two different ports.

I need some help in finding out how I can delete these from Network Services as on Webadmin the delete option is greyed out.

On a side note I also found that haproxy had not been uninstalled during the upgrade (like it should have been) so I did it manually.
Many Thanks

2
Installation and Upgrades / Re: openchange not running after provisioned
« on: February 25, 2014, 10:33:16 am »

Thanks.

Ticket opened Bug #210

3
Installation and Upgrades / Re: openchange not running after provisioned
« on: February 25, 2014, 08:47:00 am »
Hi,

Was this issue ever resolved, I am facing it at the moment.

4
Installation and Upgrades / Re: My turn to have a broken Samba.
« on: January 29, 2014, 02:49:49 pm »
I just ran the upgrade and have exactly the same error.

5
Hello,

Ok after a lot of effort from Christian (much appreciated) and Zentyal support we have finally got to the bottom of this. It turns out that this is not an issue at all but a new "design feature" of Zentyal 3.2.

There new strategy is that all services will listen on all interfaces   ???  A reference to the code here:
https://github.com/Zentyal/zentyal/commit/9b5096ff647841d658c8e47a986b0ee67ce9249e

It has something to do with clients that only use one interface and allowing them to do more with the system....I am not really to sure.

Workaround:
There is a workaround to this where you can initialise the "sortlist" function in DNS through a hook so only internal addresses are returned. It goes a little something like this:

sudo mkdir /etc/zentyal/stubs/dns
sudo cp /usr/share/zentyal/stubs/dns/named.conf.options.mas
/etc/zentyal/stubs/dns

Conf key to enabled at /etc/zentyal/dns.conf


another workaround would be to use hooks to configure Samba to look at just the internal interfaces.

Thanks,

6
ok more specifically the IP is dynamically added to DNS but it does not show up on the web interface.

7
The external IP is added through Network -> Interfaces.  When i go to the Host Record in DNS it just shows the Internal IP of the server and not the external IP but when I do nslookup i can see both IP's coming up.

Like I said if i restart DNS the external IP does not show up for a while on nslookup but after about five minutes it's there again so it is being added dynamically.

I guess I will open a ticket and see what happens.

8
Unfortunately the problem still persists. Restarting the DNS just cleared the cache so the external IP was not there for a while but it looks like it is dynamically adding it as it comes back after five minutes.

Any suggestions?

9
Christian I updated my last post. You were right about the single switch.  :-X

10
Finally it works!!

There is a bug in the Zentyal 3.2 DNS module.  Christian the external IP that i could see when I did the nslookup was not showing up in the host record so I couldn't delete it. But what I did find out is that every time I changed the WAN interface IP and saved the module the external IP was showing up when I did an nslookup. However after saving, if I went and restarted the DNS module from the Dashboard the external IP would not show up in the nslookup and it worked as it should.

Hey Christian I even got it working with both interface using one switch and no vlan's  :P Thanks for all your help.

Update: Spoke too soon the external IP has comeback again but that could be because I am on one swtich. Will disconnect the external interface again and restart DNS and report back.

11
The internal IP (10.216.16.1) is set up in Zentyal DNS as the "Domain IP Addess" and under hostnames as the IP of DC Server.

The external IP is just set up in Network-> Interfaces.

When I do an nslookup "servername"  from a client machine that's when I see both IP's against the DC server name. 

12
Internal - 10.216.16.1 /24
External -197.254.X.X /30

13
I rebuilt the server again with Zentyal 3.2 and once again configured an Internal and External interface. This time I only connected the Internal interface to the LAN swtich and have left the external interface disconnected. Everthing works fine as long as the external interface is "not set" as soon as I configure a Static IP on it but still leave it disconnected the external static IP shows up in the Internal DNS which is configured on Zentyal.

I am using a VM on Xenserver and have added two physical NIC's to the VM for the internal and external interfaces.

14
Thanks Christian for the quick reply. I thought as the interfaces were defined as Internal and External the server would do the speration even though they were on the same switch. Guess not.

15
Hello All,

I have just set up a fresh install of Zentyal Server 3.2 and gone through the basic coniguration of setting it up as a DC. I have set it up on a VM on Xenserver with two interfaces, Internal and External. Both interfaces are connected to one switch.

One thing i notice is that the DNS server is picking up the internal and external server IP addresses which it shouldn't.  This is the second time I have built this server because the same thing happend the first time.

Any ideas?

Thanks


Pages: [1] 2