Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Having just begun using Windows XP clients in my domain, controlled by a Samba PDC, I have had to upgrade to the latest version of Samba.
This in itself posed its own problems, but after a couple of days of tweaking I was able to configure the new version and set up my Windows 98 clients. This worked exactly as it had done before and caused no issues, but when i began setting up the XP clients they were unable to obtain the profiles from Samba.
They found the PDC with no problems and are able to log on and authenticate, but when they try to load tehir profiles form the PDC a dialogue is displayed saying that Windows could not find or gain access to the profiles and that a temporary profile will be used.
I have experimented with changing the signorseal registry key from 0 to 1 and vice versa but to no avail, does anybody know what might be causing this?
Are you sure that XP authenticated properly? On XP, NT and 2k clients, there is a feature that allows you to log on even thought the domain controller is not up and running, (AKA log on using cached credentials.) Go to the event viewer and look for any error logs which applies to logons. I ran into that problem myself a while back. How did you upgrade samba? Was samba installed initially via rpm or from source? How many XP clients do you have joined to the domain? You should set the local security policy so that it will disallow logging on with cached credentials. Go to LSP under administrative tools, security options, and set "Interactive Logon: Number of previous logons .........." to 0. This way, all clients within your domain will experience problems and immediately alert you instead of it happening intermittently on a few machines. Sometimes you won't even know that a problem exists.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.