ranger

I think 2.2.2 added support for XP, but can't remember exactly now ... Did you read the instructions that accompany the binaries on the samba FTP mirrors??? You will need at least: samba-server samba-common With urpmi, add the urpmi source (as it says in the README.txt): # urpmi.addmedia samba-2.2.6 http://www.samba.org/samba/ftp/Binary_Pack...e/RPMS/`awk '{print $4}' /etc/mandrake-release` with hdlist.cz urpmi samba-server

You don't say from where, but judging from the release numbers, that looks like it's from a samba mirror. Did you read the docs on those RPMS??? You shouldn't use --auto-select, and you should use 'urpmi samba-server' now, the name of the server package has changed. That said, there seems to be a problem on some releases of Mandrake, where urpmi doesn't select correctly. LDAP = lightweight directory access protocol. Samba can store passwords either in the smbpasswd file, or in LDAP. LDAP is the most flexible, and allows you to centralise accounts, and have multiple domain controllers. But at present, this is configured at compile-time, so we provide seperate packages. Please read the docs that accompany the RPMS next time, and mail the author of the docs (that would be me) if there are issues. And, 2.2.6 is actually the current stable release, RPMS of 2.2.6 for 8.0, 8.1, 8.2 and 9.0 are ready at http://ranger.dnsalias.com/mandrake/samba, and will go up onto ftp.samba.org soon. There will also be an official update based more or less on these for 9.0.

Mount with the 'acl' option. Ie, mount /dev/hdXY /mnt/path -o acl Or add 'acl' (without the quotes) to the options section (which normally has 'defaults') of the fstab entry for the partition.

In the file /etc/shorewall/rules, you should see 4 rules, that start like this: ACCEPT masq fw tcp ACCEPT masq fw udp ACCEPT fw masq tcp ACCEPT fw masq udp Add ports 137-139 in the list of allowed ports, mine looks something like this now: ACCEPT masq fw tcp domain,bootps,http,https,631,imap,pop3,smtp,nntp,ntp,137,138,139,ssh - ACCEPT masq fw udp domain,bootps,http,https,631,imap,pop3,smtp,nntp,ntp,137,138,139,ssh - ACCEPT fw masq tcp 631,137,138,139 - ACCEPT fw masq udp 631,137,138,139 -

AFAIK, the Windows XP internet connection sharing runs a mini dhcp server, which can tell your linux box all the right settings (netmask, dns, gateway etc), so maybe just try using dhcp, and it should all work. If you don't want to, chances are the Windows XP box has setup DNS forwarding, so set it as your DNS. And, before you decide on this, scan your box at http://scan.sygatetech.com, and if *anything* is open, show your stepdad. At least with linux you can get everything marked as "blocked" (aka invisible).

You need to set a uid, gid and umask for the shares, so that you have access as the user who is trying to access them after mounting. You will need to add it in the advanced settings. Something like 'uid=501,gid=501,umask=027' will give uid 501 full access, group with gid 501 read-only, and everyone else no access.

I think you need to add an entry for the laptop in the hosts file on the server. This looks like name resolution issues, and that should fix it.

Well, samba is seeing the printer share on the machine (hpdeskje I guess)? Can you post your /etc/cups/printers.conf It should have a section for that printer, with a url of: smb://username:password/home/alien/hpdeskje You could test it with a text file, like this: smbclient //alien/hpdeskje -U username smbclient>print /etc/fstab If you don't get a light flashing or paper coming out the printer, then there may be an issue with samba. If you do, then it's probably CUPS configuration that's stuffed.

It's probably better to set up DDNS, so that you have working reverse lookups, and the machines will get whatever name is set, then you can just ping the name. Otherwise, just run: # tail -f /var/log/syslg|grep DHCP and you will see all the DHCP traffic. Windows machines should normally send their name in the DHCPREQUEST There are probably also some simple apps which will show you all the current leases, you may want to search on freshmeat.net

Note that most windows-type filesystems don't support the setting of individual permissions on files. So, you must apply the permissions at mount time, which will apply to all files accessed by the mount point. It gets a bit sticky with permissions on the files on the server side (with NT/Win2k running on NTFS on the server). To change the permissions, unmount the share, and use 'uid=','gid=', and 'umask=' options. For my fat32 data share, I normally use 'uid=501,gid=502,umask=027', which gives me (I have uid 501) ownership and all permissions, the group with gid 502 has everything by write (the 2), and no one else has any permissions on the files. (The umask defines which permission bits may not be set, so setting 2 prevents w access, setting 4 prevents r access, and setting x prevents execute, or for directories, enter. Then, just add them up, to get 7, for example). Then, remount the share.

Samba only provides the transport for the printer file that is sent to the print share. Most smbclient/smbmount front-ends don't show printer shares, since they can't so anything with them. You can check with smbclient, which should show you: [bgmilne@bgmilne bgmilne]$ smbclient -L cm -I 192.168.0.253 added interface ip=192.168.0.251 bcast=192.168.0.255 nmask=255.255.255.0 added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0 Password: Sharename Type Comment --------- ---- ------- CDROM Disk D Disk PRINTER$ Disk LASER Printer C Disk WPS Disk IPC$ IPC Remote Inter Process Communication Server Comment --------- ------- CM win98se Workgroup Master --------- ------- HOME CM If the print share is shown, then that is about it ... (although we can test the share itself also). Just take a look in your /etc/cups/printers.conf, and see if the details are correct. AFAICR, the url should be something like: smb://user:password@workgroup/server/print_share