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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi Guys,
I recently had a hard drive die on me and decided to go with Mandrake 10.0, after all I was previously running 9.0 so it was well overdue for an upgrade.
Anyway everything appears to be quite good so far besides a couple of niggling problems I am having with Samba.
When I do a testparm it comes up with the following:
In that particular line of smb.conf I have the following
Quote:
domain admin group = root darren
The next one I am not entirely sure whether it's anything to worry about but here it is when I do a testparm I receive
Quote:
Server role: ROLE_DOMAIN_PDC
Finally when logging into the domain I get the following error message appear in Windows XP
Quote:
Windows did not load your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Windows did not load your profile because a server copy of the profile folder already exists that does not have the correct security. Either the current user or the Administrator's group must be the owner of the folder. Contact your network administrator.
I suspect this particular error might be related somehow to the above domain admin group problem but I'm not entirely sure. It's no real hassle starting the profile from scratch, I guess my question is what is the best way of tackling this one?
I have tried deleting the profile folder as well as using a previous backup to no avail.
Any help on any of the above would be greatly appreciated.
Don't appear to be valid variables in smb.conf. I also saw them in HOWTOs and tried them, but always got the same error you did. They may have been supported in earlier versions of SAMBA, but they don't seem to work now. I would imagine there is a newer variable that does something similar, but I don't know what it is.
The:
Server role: ROLE_DOMAIN_PDC
Message is only a problem if you don't want the machine to be the PDC (Primary Domain Controller). But since you are logging a Windows XP client onto it, you do want it to be the PDC, so this is fine.
When I had the profiles problem, it was a mistake I made in the path names. At first it didn't point to the right directory, and then when it did, the permissions were such that it couldn't access it.
The best thing would be to post your smb.conf, and we can see what the problem might be.
I might also suggest not using roaming profiles if you don't need them. When I finally did get the profiles directory to load, it was useless since there was no profile there (it needs to be created) and I was presented with Windows XP in the classic theme with no desktop.
So unless you have a profile you want to load, you aren't going to be happy with the results. I would imagine there is something you can put in the profiles directory to make Windows XP use it's standard settings if a full profile isn't found (as it is with a Windows PDC), but I have yet to find it. Perhaps you can just copy it from a Windows PDC, I'll have to look into it.
Here's an interesting twist. I tried going back to a workgroup temporarily and then rejoining the domain which doesn't work as it's complaining about DNS issues or can't find that particular domain.
Below is a list of what came up in my log
Code:
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: [2004/04/17 12:06:58, 0] nmbd/nmbd_nameregister.c:register_name(480)
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: register_name: NetBIOS name CPE-144-136-205-175 is too long. Truncating to CPE-144-136-205
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: [2004/04/17 12:06:58, 0] nmbd/nmbd_nameregister.c:register_name(480)
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: register_name: NetBIOS name CPE-144-136-205-175 is too long. Truncating to CPE-144-136-205
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: [2004/04/17 12:06:58, 0] nmbd/nmbd_nameregister.c:register_name(480)
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: register_name: NetBIOS name CPE-144-136-205-175 is too long. Truncating to CPE-144-136-205
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: [2004/04/17 12:06:58, 0] nmbd/nmbd_nameregister.c:register_name(480)
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: register_name: NetBIOS name CPE-144-136-205-175 is too long. Truncating to CPE-144-136-205
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: [2004/04/17 12:06:58, 0] nmbd/nmbd_nameregister.c:register_name(480)
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: register_name: NetBIOS name CPE-144-136-205-175 is too long. Truncating to CPE-144-136-205
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: [2004/04/17 12:06:58, 0] nmbd/nmbd_nameregister.c:register_name(480)
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: register_name: NetBIOS name CPE-144-136-205-175 is too long. Truncating to CPE-144-136-205
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: [2004/04/17 12:06:58, 0] nmbd/nmbd_nameregister.c:register_name(480)
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: register_name: NetBIOS name CPE-144-136-205-175 is too long. Truncating to CPE-144-136-205
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: [2004/04/17 12:06:58, 0] nmbd/nmbd_nameregister.c:register_name(480)
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: register_name: NetBIOS name CPE-144-136-205-175 is too long. Truncating to CPE-144-136-205
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: [2004/04/17 12:06:58, 0] nmbd/nmbd_nameregister.c:register_name(480)
Apr 17 12:06:58 cpe-144-136-205-175 nmbd[16829]: register_name: NetBIOS name CPE-144-136-205-175 is too long. Truncating to CPE-144-136-205
Now looking at my hostname it is cpe-144-136-205-175 instead of holden which it should be.
I have gone hostname holden but as soon as I restart the box the same thing comes back again.
I am on Telstra Cable here in Australia and that is my IP address which it gets from a DHCP server, any idea's how I can change this as I believe to be the likely cause of my problems to date.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.