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
1
Installation and Upgrades / Re: CONFIGURE A STATIC IP FOR eth0
« on: February 18, 2011, 04:35:23 pm »
Keeping the Zentyal box as a "reserved IP" will certainly work for all practical purposes.
However, just to see if it was the router, I changed all the new network boxes out and put in some old ones.
Did not change the outcome, so next (last?) step will be to look into the Ubuntu driver for the onboard NIC of eth0.
However, just to see if it was the router, I changed all the new network boxes out and put in some old ones.
Did not change the outcome, so next (last?) step will be to look into the Ubuntu driver for the onboard NIC of eth0.
2
Installation and Upgrades / Re: CONFIGURE A STATIC IP FOR eth0
« on: February 16, 2011, 03:50:36 pm »
Thanks for all your help on this one. Having gone through the same loops again and again, I have decided to give up on getting the Zentyal box to work to the internet on a Fixed LAN IP.
As the TP-Link router has the ability to reserve an IP to a MAC address, I am using that to give the Zentyal box a effective static IP - and it works with eth0 set at DHCP and the "auto-detected" gateway coming in correctly as the TP-Link's own LAN IP.
As to the topology of my network:
Zentyal NAS =======LAN======}
}{TP Link ROUTER}==(Billion MODEM}===ADSL===ISP
Win 7 System Admin ==LAN====== } (DHCP Server) (half-bridge)
/
Win 7 Client 1>5----------Wifi-----------------/
I can put anything other than the Zentyal box on a static IP and it works. Samba shares are working over the LAN, so I can't see that I have a firewall/NAT problem.
The ROUTER has ALG (FTP ALG: Enable TFTP ALG:Enable H323 ALG:Enable)so should be invisible to the Zentyal box.
I can only assume that somewhere in the ROUTER firmware or underlying Ubuntu there is an incompatibility. Unfortunately, as TP-LINK in UK has failed to answer any request for support (compared to Billion who have been brilliant), it seems unlikely that I will be unable to follow up any potential of a firmware bug.
As the TP-Link router has the ability to reserve an IP to a MAC address, I am using that to give the Zentyal box a effective static IP - and it works with eth0 set at DHCP and the "auto-detected" gateway coming in correctly as the TP-Link's own LAN IP.
As to the topology of my network:
Zentyal NAS =======LAN======}
}{TP Link ROUTER}==(Billion MODEM}===ADSL===ISP
Win 7 System Admin ==LAN====== } (DHCP Server) (half-bridge)
/
Win 7 Client 1>5----------Wifi-----------------/
I can put anything other than the Zentyal box on a static IP and it works. Samba shares are working over the LAN, so I can't see that I have a firewall/NAT problem.
The ROUTER has ALG (FTP ALG: Enable TFTP ALG:Enable H323 ALG:Enable)so should be invisible to the Zentyal box.
I can only assume that somewhere in the ROUTER firmware or underlying Ubuntu there is an incompatibility. Unfortunately, as TP-LINK in UK has failed to answer any request for support (compared to Billion who have been brilliant), it seems unlikely that I will be unable to follow up any potential of a firmware bug.
3
Installation and Upgrades / Re: Getting started
« on: February 15, 2011, 01:04:44 pm »As for the subject of half-bridge modems, they seem to be causing a lot of confusion amongst users. I'm sorry to say I don't have access to one, so I cannot test how to get a working setup.
It is when you're using PPPoA you'll run into problems, as you will need to keep the half-bridge configuration and do some trickery on the router instead.
The basics of it are explained pretty well on this page, I hope that will aid in solving your problem.
Good luck.
::Trym
Now that I have read the link in detail, it suggests that this problem is possibly not at the Zentyal end as I am in UK with PPoA for ADSL, set up ISP(dynamic IP)>MODEM(half-bridge)>WAN port>ROUTER>LAN port>Zentyal box.
With DHCP for eth0, Zentyal is picking up my Router as the default gateway at 192.168.100.XX1
A Route Trace shows:
traceroute to zentyal.org (92.243.17.196), 30 hops max, 60 byte packets
1 192.168.100.XX1 0.247 ms 0.287 ms 0.345 ms my Router
2 192.168.100.XX2 1.415 ms 2.033 ms 2.184 ms my MODEM's LAN address
3 91.85.160.1 26.210 ms 29.294 ms 31.993 ms
4 81.5.191.137 56.103 ms 56.751 ms 56.948 ms
The Router is showing:
WAN
MAC Address: XX-XX-XX-XX
IP Address: 91.85.164.168 Dynamic IP
Subnet Mask: 255.255.255.0
Default Gateway: 91.85.164.167
DNS Server: 212.104.130.9 , 212.104.130.65
I think (from the link) that the PPoA WAN default gateway is normally dynamically allocated as one off from the dynamic IP, so I am not sure that a fixed route can be allocated by Zentyal that will remain applicable indefinitely.
The other "strange" thing with the working LAN>WAN setup I am using, is that it ONLY works if both the MODEM and the ROUTER are set to DHCP server - which would actually seem to be the WRONG way to setup. Again, I can only assume that this is something in the "dark art" of the half-bridge firmare implementation.
The Win7 boxes on the network are able to run off fixed IPs to the Internet through this setup, so getting the routing "sorted" on the Zentyal box would seem to actually be at the Linux level - which is beyond me and the reason that I had hoped that Zentyal would work "out of the box".
Anyway takk for hjelpen Trym.
4
Installation and Upgrades / Re: CONFIGURE A STATIC IP FOR eth0
« on: February 15, 2011, 12:45:59 pm »
With a view to ensuring that I had not corrupted the ebox installation, I have completely re-installed Zentyal - this time using a static IP at installation.
First boot into the new Zentyal had no internet access and I had to change eth0 to DHCP to get the updates and finish the install.
This suggests that my problem is possibly not at the Zentyal end as I am in UK with PPoA for ADSL, set up ISP(dynamic IP)>MODEM(half-bridge)>WAN port>ROUTER>LAN port>Zentyal box.
With DHCP for eth0, Zentyal is picking up my Router as the default gateway at 192.168.100.XX1
A Route Trace shows:
traceroute to zentyal.org (92.243.17.196), 30 hops max, 60 byte packets
1 192.168.100.XX1 0.247 ms 0.287 ms 0.345 ms (my Router)
2 192.168.100.XX2 1.415 ms 2.033 ms 2.184 ms (my MODEM's LAN address)
3 91.85.160.1 26.210 ms 29.294 ms 31.993 ms
4 81.5.191.137 56.103 ms 56.751 ms 56.948 ms
The Router is showing:
WAN
MAC Address: XX-XX-XX-XX
IP Address: 91.85.164.168 Dynamic IP
Subnet Mask: 255.255.255.0
Default Gateway: 91.85.164.167
DNS Server: 212.104.130.9 , 212.104.130.65
I think that the PPoA WAN default gateway is normally dynamically allocated as one off from the dynamic IP, so I am not sure that a fixed route can be allocated by Zentyal that will remain applicable indefinitely.
Is there a setting in Zentyal network configuration that is going to get over the anomolies of PPoA dynamic WAN settings?
First boot into the new Zentyal had no internet access and I had to change eth0 to DHCP to get the updates and finish the install.
This suggests that my problem is possibly not at the Zentyal end as I am in UK with PPoA for ADSL, set up ISP(dynamic IP)>MODEM(half-bridge)>WAN port>ROUTER>LAN port>Zentyal box.
With DHCP for eth0, Zentyal is picking up my Router as the default gateway at 192.168.100.XX1
A Route Trace shows:
traceroute to zentyal.org (92.243.17.196), 30 hops max, 60 byte packets
1 192.168.100.XX1 0.247 ms 0.287 ms 0.345 ms (my Router)
2 192.168.100.XX2 1.415 ms 2.033 ms 2.184 ms (my MODEM's LAN address)
3 91.85.160.1 26.210 ms 29.294 ms 31.993 ms
4 81.5.191.137 56.103 ms 56.751 ms 56.948 ms
The Router is showing:
WAN
MAC Address: XX-XX-XX-XX
IP Address: 91.85.164.168 Dynamic IP
Subnet Mask: 255.255.255.0
Default Gateway: 91.85.164.167
DNS Server: 212.104.130.9 , 212.104.130.65
I think that the PPoA WAN default gateway is normally dynamically allocated as one off from the dynamic IP, so I am not sure that a fixed route can be allocated by Zentyal that will remain applicable indefinitely.
Is there a setting in Zentyal network configuration that is going to get over the anomolies of PPoA dynamic WAN settings?
5
Installation and Upgrades / Re: Getting started
« on: February 13, 2011, 07:22:58 pm »
Thanks for the link - on first read-through it looks like it may contain the answer to my problems, but it looks like it will take some time to digest.
PPoA is definitely common (if not the standard ADSL) in UK, but I haven't found anything as detailed as that NZ link you gave. I am certainly not getting that sort of detailed information from the MODEM/ROUTER vendors in UK, so I suspect that the PPoA half-bridge problems are not well known here either.
Anyway, I'll be trying some of the suggested fixes on both my MODEM and ROUTER and also looking into the LINUX comments there as well. I have a suspicion that at least one of my "black boxes" is running a LINUX derivative, but as I am "playing" with products from Billion, TP-LINK and Belkin, some research will be needed to confirm my suspicions.
As Zentyal is based in Spain, I don't suppose they have to understand or fix PPoA problems between ebox and a MODEM very often.
PPoA is definitely common (if not the standard ADSL) in UK, but I haven't found anything as detailed as that NZ link you gave. I am certainly not getting that sort of detailed information from the MODEM/ROUTER vendors in UK, so I suspect that the PPoA half-bridge problems are not well known here either.
Anyway, I'll be trying some of the suggested fixes on both my MODEM and ROUTER and also looking into the LINUX comments there as well. I have a suspicion that at least one of my "black boxes" is running a LINUX derivative, but as I am "playing" with products from Billion, TP-LINK and Belkin, some research will be needed to confirm my suspicions.
As Zentyal is based in Spain, I don't suppose they have to understand or fix PPoA problems between ebox and a MODEM very often.
6
Installation and Upgrades / Re: Windows 7 no account for computer on domain
« on: February 13, 2011, 04:54:02 pm »
You could also try:
Hi,
We have fixed this issue following the recomendations of this and other conversations. Thanks for your comments and suggestions!
There is no new package released yet, while we publish it you can see the changes in trac: https://trac.zentyal.org/changeset/20361
Regards,
7
Installation and Upgrades / Re: Windows 7 no account for computer on domain
« on: February 13, 2011, 04:46:37 pm »
Which versionof Win 7 are you running? I had no end of trouble trying to get Win 7 Home Premium to connect to Samba as I had enabled MS Home Group. The only solution I ever found was a clean re-install with the initial setup input as "Work Network" - don't ask me why, but the Win 7 Home Premium machines then talk to Samba OK.
8
Installation and Upgrades / Re: CONFIGURE A STATIC IP FOR eth0
« on: February 13, 2011, 04:11:22 pm »
Thanks for that - would seem that the key is in telling eth0 that's it is EXTERNAL as that's the only thing that I have had to change and it now works on a static IP.
I had left this alone as, on the initial "stand alone" installation, eth0 had been from DHCP and had "found" the correct gateway, but even although it was showing in the dashboard as "internal", clearly had full internet access.
I was further confused by the box being marked as "WAN" as I had presumed that this applied to a twin NIC interface where one of them was dedicated to WAN and the other to LAN.
Anyway - it now works the way I need it to, so, assuming that I have not broken anything else, I can continue with exploring the server and possibly expand from just using it as a NAS.
If anyone from Zentyal development ever reads these threads, they might like to include this step in the documentation relating to network setup.
Oh Dear
- spoke too soon. A re-boot of the system has left me without internet access again. Had to go back to DHCP provided IP on eth0 "up, internal, link ok" and auto-gateway "dhcp-gw-eth0"
I had left this alone as, on the initial "stand alone" installation, eth0 had been from DHCP and had "found" the correct gateway, but even although it was showing in the dashboard as "internal", clearly had full internet access.
I was further confused by the box being marked as "WAN" as I had presumed that this applied to a twin NIC interface where one of them was dedicated to WAN and the other to LAN.
Anyway - it now works the way I need it to, so, assuming that I have not broken anything else, I can continue with exploring the server and possibly expand from just using it as a NAS.
If anyone from Zentyal development ever reads these threads, they might like to include this step in the documentation relating to network setup.
Oh Dear
- spoke too soon. A re-boot of the system has left me without internet access again. Had to go back to DHCP provided IP on eth0 "up, internal, link ok" and auto-gateway "dhcp-gw-eth0"
9
Installation and Upgrades / Re: CONFIGURE A STATIC IP FOR eth0
« on: February 11, 2011, 12:58:25 pm »
Thanks for the interest - as I am currently only "trying" Zentyal, the installation is on a box on my existing LAN.
Existing LAN is: ISP > ADSL MODEM > ROUTER (DHCP) > SWITCH/AP (static IP) and 5 PCs (all on DHCP) & 2 Printers (on DHCP).
When Zentyall was installed as "stand alone server" eth0 was set to DHCP and so "the system" wrote in the gateway automaticaly (details of which can be viewed via the web interface). Both LAN and Internet are fully accessible from the Zentyal box. Inspection of the FIREWALL module in the dashboard does not show any automatically inserted entries.
Change eth0 to STATIC IP and then manually insert the same IP address and the "automatic" entry for gateway vanishes. Manually inserting the same IP for gateway that had previously been inserted (although allocating a different name) and only LAN is now accessible from the Zentyal box. (I have killed the FIREWALL module to minimise complications).
Due to the slow speed of the Dashboard saving changes, re-cycling through this to get back to putting eth0 back on DHCP becomes tedious when trying to isolate errors, so it's difficult to know if it's a bug or operator error.
Existing LAN is: ISP > ADSL MODEM > ROUTER (DHCP) > SWITCH/AP (static IP) and 5 PCs (all on DHCP) & 2 Printers (on DHCP).
When Zentyall was installed as "stand alone server" eth0 was set to DHCP and so "the system" wrote in the gateway automaticaly (details of which can be viewed via the web interface). Both LAN and Internet are fully accessible from the Zentyal box. Inspection of the FIREWALL module in the dashboard does not show any automatically inserted entries.
Change eth0 to STATIC IP and then manually insert the same IP address and the "automatic" entry for gateway vanishes. Manually inserting the same IP for gateway that had previously been inserted (although allocating a different name) and only LAN is now accessible from the Zentyal box. (I have killed the FIREWALL module to minimise complications).
Due to the slow speed of the Dashboard saving changes, re-cycling through this to get back to putting eth0 back on DHCP becomes tedious when trying to isolate errors, so it's difficult to know if it's a bug or operator error.
10
Installation and Upgrades / Re: Getting started
« on: February 10, 2011, 09:47:29 pm »
Thanks for taking the time to try to get someone with limited IT skills started with Zentyal - judging by the general lack of replies to posts on this forum, unless Zentyal (or Ubuntu) staff take more time to impart knowledge, Zentyal, which looks promising, will probably not get off the ground as a challenge to MS Server software, especially at the MS Home Server level in the small business environment (ie too small to have IT staff).
I have a similar setup to the one above, with an WAN > ADSL MODEM > ROUTER > LAN where it all falls over if I don't let the MODEM run as DHCP. The MODEM is set up in HALF-BRIDGE mode, so should be invisible to my LAN when passing traffic to the internet. I've tried a couple of different routers as DHCP with the MODEM's DHCP turned off. Using RouterStats Lite I can see that the MODEM is connected to my ISP, but not passing the connection to the LAN, at which stage I usually run out out time/patience and just put it back the way it works. (Never mind trying to work out why the WAN port on the ROUTER demands a fixed IP for the MODEM when it works OK in a LAN port using my ISP's dynamic IPs).
I have a similar "idiot" loop with trying to get Zentyal to run on a fixed IP and usually get no further than setting up the fixed IP and inserting the gateway address in the web interface (which leaves the box working on my LAN only - no internet access for updates etc) - and again usually run out out time/patience and just put it back the way it works.
In both the above, I suspect that there is a firewall problem, but so far lack the time and knowledge to track them down as none of the relevant web interfaces are particularly intuitive.
At this stage I am only initially using Zentyal as a NAS interface, while I try to get to grips with its capabilities. It's a pity that there aren't more like you actually answering queries on this forum.
I have a similar setup to the one above, with an WAN > ADSL MODEM > ROUTER > LAN where it all falls over if I don't let the MODEM run as DHCP. The MODEM is set up in HALF-BRIDGE mode, so should be invisible to my LAN when passing traffic to the internet. I've tried a couple of different routers as DHCP with the MODEM's DHCP turned off. Using RouterStats Lite I can see that the MODEM is connected to my ISP, but not passing the connection to the LAN, at which stage I usually run out out time/patience and just put it back the way it works. (Never mind trying to work out why the WAN port on the ROUTER demands a fixed IP for the MODEM when it works OK in a LAN port using my ISP's dynamic IPs).
I have a similar "idiot" loop with trying to get Zentyal to run on a fixed IP and usually get no further than setting up the fixed IP and inserting the gateway address in the web interface (which leaves the box working on my LAN only - no internet access for updates etc) - and again usually run out out time/patience and just put it back the way it works.
In both the above, I suspect that there is a firewall problem, but so far lack the time and knowledge to track them down as none of the relevant web interfaces are particularly intuitive.
At this stage I am only initially using Zentyal as a NAS interface, while I try to get to grips with its capabilities. It's a pity that there aren't more like you actually answering queries on this forum.
11
Installation and Upgrades / Re: Where I have to define the default route
« on: February 10, 2011, 09:11:09 pm »
It would seem the automatic addition of the default gateway is only true for eth0 set to DHCP, where you will get the gateway added (and visible in the web interface), along with external access, such as the internet (although there is no evidence of the relevant firewall rules in the web interface).
If you put eth0 onto a fixed IP there is no documentation as to what else has to be changed or what's required for entering the gateway address or where/how to enter the firewall changes needed to access other external addresses, such as the internet.
Zentyal is aimed at small businesses (and by that, I assume the intention is for organisations that do not have specialist IT staff), so its the web interface that should be able to provide information, rather than command line driven look-up tables you suggest.
If you put eth0 onto a fixed IP there is no documentation as to what else has to be changed or what's required for entering the gateway address or where/how to enter the firewall changes needed to access other external addresses, such as the internet.
Zentyal is aimed at small businesses (and by that, I assume the intention is for organisations that do not have specialist IT staff), so its the web interface that should be able to provide information, rather than command line driven look-up tables you suggest.
12
Installation and Upgrades / CONFIGURE A STATIC IP FOR eth0
« on: February 10, 2011, 06:42:47 pm »
Having installed the v2.0 and updates, I have built the necessary users etc to have the trial system initially work as a system backup. With that working off my existing LAN DHCP server, the next logical step to try is putting the Zentyal Server onto its own static IP.
However, just changing the eth0 setting to a valid LAN static address simply kills any external connection from the box. Manually adding the existing LAN gateway makes no difference - still no external connection from the box.
I have read the documentation and it gives absolutely no guidance as to what else needs changed to implement a static IP on a stand-alone server attached to an existin LAN.
What am I missing?
However, just changing the eth0 setting to a valid LAN static address simply kills any external connection from the box. Manually adding the existing LAN gateway makes no difference - still no external connection from the box.
I have read the documentation and it gives absolutely no guidance as to what else needs changed to implement a static IP on a stand-alone server attached to an existin LAN.
What am I missing?
13
Installation and Upgrades / Re: Windows 7 Mapped home folder (H:)
« on: October 31, 2010, 09:32:02 pm »
I have posted this elsewhere, but it may fix your problem.
The "fix" that has sorted the Windows 7 Home Premium system's ability to map the Zentyal server drive is called a clean re-installation of the Win 7 system BUT with the initial installation selection made for a WORK network when first asked. Absolutely no other changes have been made to the Win 7 or Zentyal systems and it all worked "out of the box".
(It does not seem to matter what sort of Win 7 network you try after you have made the initial install as "home" network - it would seem that it will never again link to SAMBA if initially installed as other than WORK network).
No doubt there is some logic in this from the way Win 7 default permissions are lodged in the registry, but I lack both time and ability to find it. Perhaps it is linked to the "new" Win 7 feature of the "homegroup" - I read somewhere that MS have been made to implement SAMBA interoperability, so perhaps their "new" Win 7 "homegroup" is exempt from the earlier ruling.
As a bonus, this has also solved another annoying problem that I was having, in that I can now connect to an old printer that is networked off the USB on an equally old ASUS WL-500g router that is running SAMBA.
What is still "missing" on the Win 7 network list (although reachable via IP address) are a couple of Belkin F5D7633-4 routers although both the old ASUS router and the Billion MODEM 5200S-RC show up.
Perhaps if someone can confirm this "fix" (or even better if Zentyal and/or Ubuntu can reverse engineer it to see what is happening in the Win 7 registry) it could go in the FAQs.
That might even save someone else having to spend quite so much time googling the problem for a working solution and improve the take-up of Zentyal in a "mixed" small business network?
The "fix" that has sorted the Windows 7 Home Premium system's ability to map the Zentyal server drive is called a clean re-installation of the Win 7 system BUT with the initial installation selection made for a WORK network when first asked. Absolutely no other changes have been made to the Win 7 or Zentyal systems and it all worked "out of the box".
(It does not seem to matter what sort of Win 7 network you try after you have made the initial install as "home" network - it would seem that it will never again link to SAMBA if initially installed as other than WORK network).
No doubt there is some logic in this from the way Win 7 default permissions are lodged in the registry, but I lack both time and ability to find it. Perhaps it is linked to the "new" Win 7 feature of the "homegroup" - I read somewhere that MS have been made to implement SAMBA interoperability, so perhaps their "new" Win 7 "homegroup" is exempt from the earlier ruling.
As a bonus, this has also solved another annoying problem that I was having, in that I can now connect to an old printer that is networked off the USB on an equally old ASUS WL-500g router that is running SAMBA.
What is still "missing" on the Win 7 network list (although reachable via IP address) are a couple of Belkin F5D7633-4 routers although both the old ASUS router and the Billion MODEM 5200S-RC show up.
Perhaps if someone can confirm this "fix" (or even better if Zentyal and/or Ubuntu can reverse engineer it to see what is happening in the Win 7 registry) it could go in the FAQs.
That might even save someone else having to spend quite so much time googling the problem for a working solution and improve the take-up of Zentyal in a "mixed" small business network?
14
Installation and Upgrades / Re: Windows 7 does not mount samba users home share within a domain (PDC)
« on: October 20, 2010, 07:37:18 pm »
Well, I have found a "fix" that has sorted the Windows 7 Home Premium system's ability to map the Zentyal server drive. It was called a clean re-installation of the Win 7 system BUT with the initial installation selection made for a WORK network when first asked. Absolutely no other changes have been made to the Win 7 or Zentyal systems and it all worked "out of the box".
(It does not seem to matter what sort of Win 7 network you try after you have made the initial install as "home" network - it would seem that it will never again link to SAMBA if initially installed as other than WORK network).
No doubt there is some logic in this from the way Win 7 default permissions are lodged in the registry, but I lack both time and ability to find it. Perhaps it is linked to the "new" Win 7 feature of the "homegroup" - I read somewhere that MS have been made to implement SAMBA interoperability, so perhaps their new Win 7 "homegroup" is exempt from the ruling.
As a bonus, this has also solved another annoying problem that I was having, in that I can now connect to an old printer that is networked off the USB on an equally old ASUS WL-500g router that is running SAMBA.
What is still "missing" on the Win 7 network list (although reachable via IP address) are a couple of Belkin F5D7633-4 routers although both the old ASUS router and the Billion MODEM 5200S-RC show up.
Looks like I may be able to "play" with Zentyal at home after all to see if I can tame it for work.
Perhaps if Zentyal technicians can confirm this "fix" (or even better if Zentyal and/or Ubuntu can reverse engineer it to see what is happening in the Win 7 registry) it could go in the FAQs.
That might even save someone else having to spend quite so much time googling the problem for a working solution and improve the take-up of Zentyal in a "mixed" small business network?
(It does not seem to matter what sort of Win 7 network you try after you have made the initial install as "home" network - it would seem that it will never again link to SAMBA if initially installed as other than WORK network).
No doubt there is some logic in this from the way Win 7 default permissions are lodged in the registry, but I lack both time and ability to find it. Perhaps it is linked to the "new" Win 7 feature of the "homegroup" - I read somewhere that MS have been made to implement SAMBA interoperability, so perhaps their new Win 7 "homegroup" is exempt from the ruling.
As a bonus, this has also solved another annoying problem that I was having, in that I can now connect to an old printer that is networked off the USB on an equally old ASUS WL-500g router that is running SAMBA.
What is still "missing" on the Win 7 network list (although reachable via IP address) are a couple of Belkin F5D7633-4 routers although both the old ASUS router and the Billion MODEM 5200S-RC show up.
Looks like I may be able to "play" with Zentyal at home after all to see if I can tame it for work.
Perhaps if Zentyal technicians can confirm this "fix" (or even better if Zentyal and/or Ubuntu can reverse engineer it to see what is happening in the Win 7 registry) it could go in the FAQs.
That might even save someone else having to spend quite so much time googling the problem for a working solution and improve the take-up of Zentyal in a "mixed" small business network?
15
Installation and Upgrades / Re: Windows 7 does not mount samba users home share within a domain (PDC)
« on: October 03, 2010, 09:00:57 pm »
Thanks for the advice.
Change/upgrade of Windows 7 version not practical (too many machines on the network on XP due for upgrade - cost too high). Change of Server software more likely if Zentyal cannot support connection to Win 7 Home Premium - as I have already connected other LINUX based server software such as ClearOS to Win 7 Home Premium machines using SAMBA.
Basic fact of life is that Windows dominates low cost computers due to "free" Home Premium pre-installation - cost of one copy of Windows Server much lower than cost of multiple copies of Win 7 Pro to support Zentyal server network - if Zentyal not able to be "proved" in my after work "fun" on home network, then it will not end up running my small business server either. After all, that's why the MS business model works and they get away with poor SAMBA support in Win 7.
Change/upgrade of Windows 7 version not practical (too many machines on the network on XP due for upgrade - cost too high). Change of Server software more likely if Zentyal cannot support connection to Win 7 Home Premium - as I have already connected other LINUX based server software such as ClearOS to Win 7 Home Premium machines using SAMBA.
Basic fact of life is that Windows dominates low cost computers due to "free" Home Premium pre-installation - cost of one copy of Windows Server much lower than cost of multiple copies of Win 7 Pro to support Zentyal server network - if Zentyal not able to be "proved" in my after work "fun" on home network, then it will not end up running my small business server either. After all, that's why the MS business model works and they get away with poor SAMBA support in Win 7.
Pages: [1] 2