Zentyal Forum, Linux Small Business Server
Zentyal Server => Installation and Upgrades => Topic started by: Lynge on October 04, 2009, 12:58:25 pm
-
Hi
I have just setup a new ebox and it is just great, but I have 2 problems (so far) the first is VPN, but I will just use a different thread for that.
The second is that I cannot connect windows7 machines to the domain.
I was testing it with windows7 and I could not figure out why on earth I couldn't get it working. Then I tried it with a winXP, and it logged in straight away. And now I have just tested it with a different win7 machine and I got the same result.
For good measure, here is the error:
"The following error occurred attempting to join the domain "lmg.local":
The specified domain either does not exist or could not be contacted."
I shall gladly add any info you might need. I have just performed a backup of the configuration, but it is not obvious to me which of the files you could need. So please speak up.
-
Information from the Samba site: Can you join the Samba domain if you if you put the following two DWORD registry values in place on your Win7 client and reboot:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters
DomainCompatibilityMode = 1
DNSNameResolutionRequired = 0
-
I've tried this regedit.exe solution and it does not work. It does let you add the client to the domain, however, when logging on it errors: "The trust relation between this computer and the domain is invalid!"
Or something of that sort. Anyone else have any good ideas on this?
-
Just sent the latest server out the door, so I gotta get another one up for testing, but then I will give this a try also. Even though tommie has already given it a go. Bette test it twice :)
-
Just for letting you know that there is another thread [1] talking about the same issue. :)
Cheers,
[1] http://forum.ebox-platform.com/index.php?topic=1972.0
-
I tried multiple solutions. But ebox has SAMBA 3.0.28 and that is not enough for it to work. You need 3.3.4 at least. :)
That was my error. I did not check the SAMBA version. So now I will just get rid of e-box and do it myself installing samba and bind and dovecot etc. etc.... :) Or will ebox start using current packages? :)
-
Hey Tommie,
Could please give us some pointer about the minimum samba version for windows 7?
-
Looks like there are a couple of issues with Windows 7 and Samba. Firstly, MS says that they purposely engineered Win7 without any attempt at making it compatible with logging into an NT4 domain, however it looks like some folks have succeeded in joining and using Samba domains providing the Samba PDC is using at least Samba 3.3.6.
There appear to be a couple of issues - the registry keys that define crypto credentials already discussed and DNS domain suffixes appending to hostnames.
This thread has a lengthy discussion which includes some folks who have achieved success:
http://www.nabble.com/Windows-7-RC-td23405949i20.html
They are using Samba as a PDC, not eBox, however the issues should be the same across any version of Samba. The question is whether eBox can be upgraded to the necessary Samba version - if that can be done, then it appears that there is hope for joining Windows 7 systems to domains with eBox Samba PDCs.
Kind regards,
Rob in Memphis
-
http://trac.ebox-platform.com/wiki/Document/HowTo/Windows7Support
-
OK so I followed the instructions in the WIKI Last night but I borked my server and had to start again. I have rebuilt the server and this time I chose to keep the package maintainers samba.conf instead of preserving my own. This seemed to do the trick.
So I did the reg key updated samba and ebox-samba (i did an apt-get update && apt-get upgrade after initial install anyway).
The win7 machine this time failed to join domain. So I tested on xp same issue :-(. So then I changed the domain name saved changes. This time the XP vm joined ok and so did the win7 (although it complained about not being able to rename computer or something).
The next issue I have is that I can no longer access any shares on either xp or win7. User share folder is not mapped either.
Win7 waits a mo then errors "Windows cannot access \\ubuntu-ebox\Install error code 0x80070043 The network name cannot be found"
XP pops up and asks for credentials but when entered they never work.
Im close.. But I need those shares.
Also Win7 is alot slower at joining the domain took a few minutes where as XP did it in about 20 seconds.
-
That's really strange. Anyone is experiencing similar problems?
-
Now we have a new version of samba (3.4.3) in our 1.3 repositories, maybe you can try to upgrade it to see if it solves your problems. It is supposed to solve issues with Windows7 according to the samba guys.
-
This is sorry to see :(
I have two win7 64bit machines coming in this week and a new eBox 1.2 up and running :-\
Has anybody confirmed the workaround that J. A. Calvo posted earlier today? I cannot test it yet.
Does this affect both win7 32 & 64 bit setups? Can anyone confirm for 64bit?
Much thanks for an update. And good luck!
~dan
-
The new samba package that I uploaded yesterday it's supposed to fix problems with share access. Some people reported that login worked but they couldn't access shares. I haven't tested anything with windows7 64bit. Hope someone could give us more feedback.
-
So I "borrowed" a machine from work and installed WIndows 7 64bit Pro (full version build 7600) on it.
I'm gonna try the eBox updated samba and see if i can get it up and running tonight, wish me luck.
Like I said before, I a noob here with linux server stuff. Will the 1.4 version of eBox upgrade the samba that I am upgrading tonight as per J. A. Calvo's package update? J.A., does an updated version just figure what is outdated and update it saving/converting the config files/database?
Thanks
~dan
is there a fingers crossed emoticon?
-
Success! 8) After updating samba with the one in the 1.3 repositories (since i'm using 1.2 from the .iso and I chose to KEEP my samba.conf instead of using the repo version) I am able to connect to an eBox domain from a Windows 7 64bit client
and browse shares.
Turns out that the share and now mapped drive are able to be seen in the file explorer but cannot be accessed (not found).
I also tried to add the pdf printer and it failed with an 0x00000000d error.
So I can only login to the domain now. The shares worked for a few minutes i even transferred files.
After a first reboot I was greeted with a dialog box asking me to reboot to apply changes? What changes, I'm already connected to the domain!
The initial logon is very long. after I enter user and pass, the system waits about 90sec+ before displaying desktop.
Subsequent reboot and logon is about 60sec+ before desktop. Is this a roaming profile thing or just Windows 7? I do not have roaming profiles selected.
When I "return" the machine I will note the time between authentication and desktop display on a SBS2003 domain.
I cannot test printing with my home setup. HP1000 needs firmware loaded every time and I don't care enough to get that working. All the work machines are 5 years newer than it.
Hope this helps someone. I can test for another day if someone needs something.
Thanks J. A. Calvo and the rest of the eBox team.
best,
~dan
-
Yes, the logon on Windows 7 is also too long for me, about 60 sec as you say (maybe less, but it's a lot of times slower than Windows XP). I don't know why is that, but either has to be a Windows7 issue or a Samba one. I don't thing eBox has nothing to do with that...
Thank you for the testing!
-
i have the shares working now with windows 7 64 and eBox 1.3.5 on ubuntu 9.10 running samba 3.4.0
all packages were installed through synaptic.
on the winblows, i mean windows 7 side, i followed the registry edits from http://trac.ebox-platform.com/wiki/Document/HowTo/Windows7Support along with adjustments to "Local Security Policy" in windows posted here: http://www.dustypixels.com/blog/2009/11/07/windows7-samba-shares/
now the logon is down to 43 sec from 60 sec. i know we can do better than this because i timed the logon to sbs2003 and it was like 2 sec.
the shares persist through reboots now and i'm hooking up my hp1000 (that needs firmware loaded each time :( % ) to test samba printing.
running an application from a share asks for authentication by an elevated user on the domain (ebox) which i like. but if i just download an application locally on the windows machine it does not.
i'll post updates to the printers and if i hit a wall.
will i have to hose the 1.3.5 install to upgrade to 1.4?
thanks again eBox guys and gals.
~dan
-
Hey Tommie,
Could please give us some pointer about the minimum samba version for windows 7?
Hey Javi, sorry for the late reply. Ebox will not work with Windows 7 clients due to the Samba version used in 1.2x. It seems that 1.4 will have windows 7 support. However, all ebox needs is a 3.4.x version of samba to support Windows. That is all I guess....
Since ebox is not very agile when it comes to package change, I think I will just stick to my self-made ebox version which runs like a charm and updates through apt-get upgrade instantly...
cheers,Tommie
-
Since ebox is not very agile when it comes to package change, I think I will just stick to my self-made ebox version which runs like a charm and updates through apt-get upgrade instantly...
What do you mean with not agile to package change? We have samba 3.4.3 in our repository from time ago:
http://trac.ebox-platform.com/wiki/Document/HowTo/Windows7Support/
-
No offense tommie but, if you have created something that you believe works better, why not share your findings and configuration with the developers and the community so that everyone can benefit.
Anything we do helps eBox to make a run at complete commercial SBS server solutions such as M$ server. I have been running eBox with windows 7 for some time now in a production environment by following the instructions from the http://trac.ebox-platform.com/wiki/Document/HowTo/Windows7Support
tommie, how long are your logon times using your "self-made" solution in windows 7?
best,
~dan
-
No offence taken. But I do not think my version is better. My version has to be updated and configured by hand, I wish I could get the same thing done with Ebox. However, manually upgrading the samba package with Ebox did not work for me.
Since the version 'supported' by ebox is stated not to be supported. I just installed Samba and configured it myself. Now Windows 7 clients do hook-up to the domain.
I will wait untill 1.4 is released and see where that takes us. As of right now people here authenticate to a very simple samba setup.... :(
-
What samba version are you using?
-
tommie, how long are your logon times using your "self-made" solution in windows 7?
best,
~dan
Hey Dan,
It takes about 5 seconds to load the user profile. But I am not roaming those profiles. Users here have a share where they can upload documents which they need at home.
The only problem I had with ebox was adding Windows 7 clients to the network. I also found that roaming profiles sometimes errored after changing this option more than once. The (client side) error I got was that there was not enough disk space to save the roaming profile or file security was setup wrong.
So, since 1.4 is comming out soon, I will give that a go. Otherwise I might try ClearOS (clarckconnect). I need something setup at least before february! ;)
Cheers,
Tommie
-
What samba version are you using?
3.4.3