samba problems

[Compunuts]

You said ;

i just meant that if i add the win user as a regular user on my pc wouldnt this give everyone a entry point into my system ?

ph34r already answered..

Setting the shell to /bin/false is good to prevent ssh/telnet/local logins, but won't prevent ftp/scp access or samba access, which is probably what you want.

If you have a user accout that is set to /bin/false, that use can't login remotely to your box as shell account thus eliminating the danger of remote exploit BUT still able to do if it's system exploit. So technically, yes, you are not safe 100% but no system is that way either.....

HTH...

[civ1492]

Thx for all the replies .. i think ill be safe if i just use a strong password and set the shell to /bin/false ..

[agar]

1. *Have you ever been able to Samba from Windoze to Linux?

The problem is accessing samba from the win98 machine. The linux/xp machine has no problems accessing any of the shares. Security is also not much of an issue. All computers on my lan share one external ip and theres only 2 ports open on a linux web/ftp server. So could it be the win98 machines problem?

[Coral_Sea]

The problem is accessing samba from the win98 machine. The linux/xp machine has no problems accessing any of the shares. Security is also not much of an issue. All computers on my lan share one external ip and theres only 2 ports open on a linux web/ftp server. So could it be the win98 machines problem?

Did you try the smb.conf file I suggested?

[Pleiades]

I did this to my 98 machine to see if the problem was with encrypted passwords -

(from M$ KB)

Start Regedit.exe.


Locate the following key in the registry:

HKLM\System\CurrentControlSet\Services\VxD\VNETSUP


Change the data value for the EnablePlainTextPassword value to 1 .


Restart your computer

I was then able to connect from the 98 box, so I had to fix the password encryption issue. Try it, and if it fixes it , get back to us and I'll fill you in on what I did to fix the encryption issue.

[agar]

Thanks I'll be sure to try that when I get a chance.

[agar]

I know this is from a long time ago but I finally went to try that registry fix on the win98se box and that key wasn't there.

[Guitarlynn]

[quote]

Do you have a user on the Linux box for your Dad's Win98
machine? You will have to do this and have a user on the
Linux box for the Win98 machine name also. Using "user"
level security, the share for the Win98 machine/user will
default to that "username" directory on the Linux box.... not
a specific share you want it to. Futher considerations would
be to set the GID bit on the "mp3" share so all users of that
Group have equal permissions and access to the share.

Remember, Windows 9x/ME are "single-user" OS's, the
machine-name and username will need to match.

Hope this helps,
~Guitarlynn

[agar]

Security is set to user. rob is the name of the win98se machine and rob is the name on the samba server. The user rob is in the same group that all files and directories are under.

[Guitarlynn]

Security is set to user. rob is the name of the win98se machine and rob is the name on the samba server. The user rob is in the same group that all files and directories are under.

OK, then when you try to access the server with "rob", samba will
mandate that rob goes to /home/rob. Unless you've changed the default settings, if /home/rob doesn't exist and/or hasn't been logged into on the Linux box itself, the user "rob" is denied access and gets the unknown user Samba error "$IPC" and is prompted for a password.

This does not happen with "share" level security and the main reason I suggest "share" for first time users on a trusted network.... a little frustrating eh? On the Linux box, log in as "rob", then logout, then you should be able to log in from the Win98 box assuming the Username and password match exactly. Also, Win9x/ME is not "case-sensitive", so you will want to use the "case-sensitive = no" option in smb.conf, otherwise things will get weird.

Hope this helps,
~Guitarlynn

http://leaf.sourceforge.net/devel/guitarlynn