SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : LINUX

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Thomas A Watson who wrote (2312)9/17/2000 6:50:57 AM
From: E. Charters  Read Replies (2) of 2615
 
I enabled encrypted passwords in samba. Win98 will see
my linux directories with either access set in windows.

Win95 II and win98 are encrypted passawords by deafult.

The smb.conf file on my linux samba machine is set to "encrypted =yes".

win 98 is set to access-share as samba docs say is required.

But when doing a 'smbclient '//winbox/sharename' -U username'
I get a 'password-username' mismatch from the linux box.

The username set in samba and the password in /etc/passwd and proper_directory/smbpasswd are exactly the same. And they are set the same on the windows box. That is the same in all three locations, two on the Linux box .. in samba and the system itself and one on the winbox with both username and password.

Networking works from win to Linux and from linux to linux box but not from the samba server in linux to the winbox.

Samba is set to user access or as they say "security=user" default in smb.conf and win is supposed to be set to sharename access to work with samba as samba people say.

However when I set the security=share OR security=user in Linux with windows set to either user or share the result is the same.

The only way you are going to get prompted for a password in windows with samba running is when you do the network setup in windows, is by selecting share access in windows.

When you select user acess in windows it tells you that the list of users is not available at this time. This Samba says is soluable by setting share level access in windows.

But nooo workee.

Never saw anything like it in all my nites and days.

I guess I can try non-encrypt in windows. The version of win98 I am using is the latest out this year as a replacement disk.

I was told that windows sometimes needs registry removal of all network components and reinstall but when I try to merely remove the network components in control panel, windows will not reboot telling me I have to run setup to replace the missing VXD driver. I don't even touch the registry for this insult. Of course setup will not run as the windows either requires a complete reinstall of windows and 300 megs free disk space and one hour or nada OR I have to restore the registry.. which can fail if there is not a recent backup or the backups age as you attempt to repair it with reboots.

Windows won't merely allow the driver to be replaced. That would be convenient. You might nejoy that. MS is not merely shooting itself in the foot it declares nuclear war against standing.

Still I cannot tell clients who want to reliably network to use Linux solely as the retraining is way oever the top. But what network tools to use? Is this a samba bug and is it fixed commercially or both samba-MS?

Linux could get real leg up if it could network with NT and win98 easily. I did not say free but nobody else said the solutions are anywhere. I would not say its chances are good with MS's attitude but to sneak linux in as a files server in many offices seems to be something worth working on.

I note that in the reinstall win98 wiped out my eudora mapi dlls. The justice deparetment does not know the half of it.

mailto:echarters@primus.ca
24.43.25.216

EC<:-}
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext