Error Reading Information On Service Winbind
Contents |
connection with Windows Domain/DNS Issues related to configuring your network Post Reply Print view Search Advanced search 10 posts • Page 1 of 1 pbasehore Posts: 27 Joined: 2008/05/08 12:02:17 Location: error reading information on service httpd Peachtree City, GA, USA Contact: Contact pbasehore AOL NetBIOS name connection with Windows Domain/DNS
Error Reading Information On Service Ntpd No Such File Or Directory
Quote Postby pbasehore » 2008/05/08 12:20:50 I am new to CentOS, so I apologize if this is a simple question--I'm error reading information on service telnet no such file or directory used to more "desktop" distros like PCLinuxOS. This is my first Linux install for a strictly server role.I am using CentOS 5.1 for a Nagios server (I also have KDE, Apache, and MySQL
Error Reading Information On Service Portmap No Such File Or Directory
installed as well.) I have Samba set up to connect to our Windows Domain the same way I have in other distros, but the hostname/NetBIOS name is not responding to our DNS. Also, I can only see the "it works!" screen in Apache on the local box--neither Windows or Linux can see it through the network using the hostname or the static IP.I have SELinux and error reading information on service postgresql no such file or directory the Firewall turned off.I am able to ping the IP address using both Windows and Linux, but I am never able to ping the hostname. In my network configuration file, I have my hostname set toHostname.domain.comI also went into the KDE Control Center and configured Samba identically to another box (that works). Still no dice. What do I need to do to get external computers on the network to recognize my server's hostname?Also, before I forget, I have added the computer into Active Directory and the DNS tables with the static IP. Thanks for the help! Top scottro Forum Moderator Posts: 2215 Joined: 2007/09/03 21:18:09 Location: NYC Contact: Contact scottro Website Re: NetBIOS name connection with Windows Domain/DNS Quote Postby scottro » 2008/05/08 14:32:34 If I understand this issue, it seems as if it might be a problem with the AD server's DNS setup. Is it possible that the error is on that side? Also, one thing that sometimes gets missed (though I think this is more a Fedora than CentOS issue) is to make sure that nmb as well as smb gets turned on. (I'm not sure if the problem was Fedora's, the samba rpm at s
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
happily, but there was one change that took a little while to figure out. We'll run through all the steps, from beginning to end, http://tech.lanesnotes.com/2010/11/ad-authentication-with-rhel-6.html here. Install the prerequisites We're using samba and samba-winbind for this, so make sure these are installed. yum install samba samba-winbind If you're running RHEL5 and a Windows 2008 R2 domain, you'll want to use samba3x, instead of the samba. See this article for more information on that front. Edit the Configuration Files you'll want to have the following settings. I've grouped them here to make it all error reading more readable. Changes from the default are in blue. /etc/krb5.conf default_realm = EXAMPLE.COM dns_lookup_realm = true dns_lookup_kdc = true ticket_lifetime = 24h renew_lifetime = 7d forwardable = yes [realms] EXAMPLE.COM = { default_domain = example.com } [domain_realm] .example.com = EXAMPLE.COM example.com = EXAMPLE.COM Here we're defining the kerberos realm and domains. "example.com" will be replaced with your AD domain name. Do note the capitalization; it matters. /etc/samba/smb.conf workgroup error reading information = example realm = EXAMPLE.COM security = ads idmap uid = 10000-500000 idmap gid = 10000-500000 template shell = /bin/bash winbind use default domain = true winbind offline logon = false winbind nested groups = yes encrypt passwords = yes Here we've told samba to use the kerberos realm EXAMPLE.COM (you'll substitute your domain from the krb5.conf file). We're using ads for security (Windows-style), and we're allocating a bunch of UIDs and GIDs for mapping the domain users and groups to the Linux equivalents. /etc/nsswitch.conf passwd: files winbind shadow: files group: files winbind Here we're telling the system to look not only in the /etc/passwd and /etc/group files for authentication, but also to use winbind. Join the Domain Now's the fun part: we can join the system to the domain. chkconfig smb on service smb restart net ads join -U username where username is a domain user who has permissions to join a computer to the domain. You should get a response that the server has joined your realm. Depending on your DNS configuration, you might get some errors like the following: [root@linuxserver1]# net ads join -U username Enter username's password: Using short domain name - EXAMPLE Joined 'LINUXSERVER1' to realm