mazeroth
11-08-2002, 01:27 AM
Hey people. I have mandrake 9, installed samba and it works under my WinXP Pro machine. I run \\Linux , put in user/pass and get it. But for some weird reason I can't access the network neighborhood Other (where the linux machine is in).
Says Others is not accessbile, don't have permissions to access it. Why can I get into the Linux machine, but can't open the neighborhood place it's in in windows? Thanks.
oOIIEONOo
11-08-2002, 02:27 AM
just a thought have you created a samba user on your linux computer .
;)
rustskull
11-08-2002, 02:32 AM
most people will suggest using swat, but I've never bothered because hacking your smb.conf file for fun and profit was always really easy to do for what I needed. It just sounds like you need to go in and set up shares to expose to the windows side of the network. what you;ll see commonly is that by default you are able to get into your home directory. any user that exists on the linux side will be able to access it the way you are, but every person will only see their own home directory, if they have one...it's a global setting that assists in portability of people and centralization of home accounts...
man smb.conf
and if you don't need to set up printing or anything else from the windows side via samba, it's pretty quick and dirty. Both the solaris distribution and my debian distro have commented out examples for any configuration you'd need to do, right in the conf file itself...why I never had to fire up swat. seemed like a nuisance, really.
What you basically are doing is giving each particular directory entry point a name that will be visible from the windows side, and as long as you have synced your samba, shadow, and nt passwords, you'll be able to see the shares immediately when you login to nt, and will be able to surf down any of the subdirectories below the shares, as long as the permissions are set correctly on the linux side.
couple cautions...
permissions will propagate through and can be altered from the windows side to the linux, as long as the user on the windows side has proper permission in the first place on the linux side...makes sense, but surprised me on a couple occasions when using tools that set thing like that automagically during use...
TURN OFF CASE MANGLING it will cause you no end of fury, again was having tools hurl before I knew what samba was about, did a quick study over a few hours and found out that files we were pushing in from the windows side were getting hosed up and all of a sudden libraries that were fine from our customers were non-functional when the tools tried to follow the paths. set a simple setting to "no" in smb.conf, everything all happy again. Make sure to keep original case too, there's a setting for that.
LINUX HATES SPACES IN FILENAMES...well, not really, as long as you encase the name in double quotes, it will take it...but tools will die, java won't work right, etc etc. The famous thing will be when you create "new folder" on the windows side and then go try and look for it on linux...heh. all sorts of weird stuff can happen because of things windows allows...samba is very diligent about doing exactly what you tell it to.
can't think of much more of the showstopper variety...
as usual, more info than was needed or even wanted...
HTH
-rust
mazeroth
11-09-2002, 02:35 PM
Thanks people, I played with it a little bit more and now it works, not sure why. Maybe it was when I changed the security to User instead of default. I also used Webmin and that was very helpful. I recommend it to everyone. www.webmin.com