Prev | Current Page 1349 | Next

Christopher Negus

"Linux Bible, 2008 Edition: Boot up to Ubuntu, Fedora, KNOPPIX, Debian, openSUSE, and 11 Other Distributions"

d/iptables restart
You then need to open access to ports 137, 138, and 139 in your firewall so that the Samba server
can accept connections for services. (See Chapter 18 for information about modifying your firewalls.)
User Passwords Working?
Try accessing a shared Samba directory as a particular user (from the local host or other Linux
system on your LAN). You can use the smbclient command to do this. Here is an example:
# smbclient //localhost/tmp -U chris
added interface ip=10.0.0.1 bcast=10.0.0.255 nmask=255.255.255.0
Password: *******
Domain=[ESTREET] OS=[Unix] Server=[Samba 2.2.7a]
smb: \>
In this example, smbclient connects to the directory share named tmp as the Samba user named
chris. If the password is accepted, you should see information about the server and a smb:\>
prompt. If you cannot access the same shared directory from a Windows client, it??™s quite possible
that the client is passing an improper username and password. Part of the problem may be that the
Windows client is not providing encrypted passwords.
For certain Windows clients, using encrypted passwords requires that you change a Windows
registry for the machine. One way to change the registry is with the Windows regedit command.
Registry changes required for different Windows systems are contained within the /usr/share/
doc/samba-*/docs/Registry directory.


Pages:
1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361