To fix this error:
# nslookup mydomain.com
nslookup: error while loading shared libraries: liblwres.so.50: cannot open shared object file: No such file or directory
Do this:
# ldconfig
# dig mydomain.com
; <<>> DiG 9.6.1-RedHat-9.6.1-2.fc11 <<>> mydomain.com
...
From the ldconfig manpage:
ldconfig creates the necessary links and cache to the most recent shared libraries found in the directories specified on the command line, in the file /etc/ld.so.conf, and in the trusted directories (/lib and /usr/lib). The cache is used by the run-time linker, ld.so or ld-linux.so. ldconfig checks the header and filenames of the libraries it encounters when determining which versions should have their links updated.
If your SSH public key authentication is failing with errors like this:
$ ssh -vvv myhost.com
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/kitamura/.ssh/id_dsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
…try these permissions on the server:
server$ chmod go-w ~/ (same as 755)
server$ chmod 700 ~/.ssh
server$ chmod 600 ~/.ssh/authorized_keys
more troubleshooting tips
- Go through the usual setup at Samba.org or use YUM (yum install -y samba)
- By default, the smb.conf allows sharing of home directories.
- Add a Samba user (smbpasswd -a myusername)
- On Fedora, run SELinux Administration
- On the left menu, click “Boolean”.
- Scroll down to “samba”, and check the box next to “Allow samba to share users home directories”.
- Also on Fedora, make sure your Firewall allows the Samba ports 139 and 445.
- On Windows Vista, now map the network drive.
Sample smb.conf:
[homes]
comment = Home Directories
browseable = no
writable = yes
; valid users = %S
; valid users = MYDOMAIN\%S
On the destination server, remove the known_hosts file:
rm ~/.ssh/known_hosts
Also, try this in your /etc/hosts.allow file
/etc/hosts.allow:
SSHD: ALL
Recent Comments