Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm brand new to Linux, but have been building PCs and tinkering with networks since DOS 1.1, so I'm good where I'm familiar but way out of my comfort zone with Linux (OpenSuSE - & SAMBA).
I've got OpenSuSE 11.0 installed on a dedicated machine with SAMBA (version unsure, but it came with the OpenSuSE 11.0) also installed. I'm able to see the two WinXP boxes from the Server (OpenSuSE/SAMBA), and have access to files on the XP boxes from the server. I can SEE the server from the XP machines, but cannot get access because it asks for a login User-ID & password. But, tho the admin UID/PW works on the server, it's refused from the XP boxes.
Is there a login client for WinXP that will connect me to the shared folder(s) on the server?
Is there something I need to do (set up other user, maybe) to get access?
Can I map a drive on my WinXP boxes to the shared folder(s) on the Server (after I can get access, of course)?
I know this may seem like I'm asking someone else to do the work, but I've spent about $80 on a pair of books, and it's almost like they're written in Chinese or Hebrew, and I'm terribly lost in resolving this issue.
As soon as I've got this fixed, I'm going to RAID 4 (250 gb) drives and them move all our data off the two XP boxes and eventually replace XP with Linux. All 3 boxes are brand new, just built, not even 2 weeks run time on them.
If anyone has any motorcycle questions, feel free to ask me! ;+)
Thanks,
David
Last edited by DarkFlame; 11-29-2008 at 09:42 PM.
Reason: To add version info
I'm brand new to Linux, but have been building PCs and tinkering with networks since DOS 1.1, so I'm good where I'm familiar but way out of my comfort zone with Linux (OpenSuSE - & SAMBA).
I've got OpenSuSE 11.0 installed on a dedicated machine with SAMBA (version unsure, but it came with the OpenSuSE 11.0) also installed. I'm able to see the two WinXP boxes from the Server (OpenSuSE/SAMBA), and have access to files on the XP boxes from the server. I can SEE the server from the XP machines, but cannot get access because it asks for a login User-ID & password. But, tho the admin UID/PW works on the server, it's refused from the XP boxes.
Is there a login client for WinXP that will connect me to the shared folder(s) on the server?
Is there something I need to do (set up other user, maybe) to get access?
Can I map a drive on my WinXP boxes to the shared folder(s) on the Server (after I can get access, of course)?
I know this may seem like I'm asking someone else to do the work, but I've spent about $80 on a pair of books, and it's almost like they're written in Chinese or Hebrew, and I'm terribly lost in resolving this issue.
As soon as I've got this fixed, I'm going to RAID 4 (250 gb) drives and them move all our data off the two XP boxes and eventually replace XP with Linux. All 3 boxes are brand new, just built, not even 2 weeks run time on them.
If anyone has any motorcycle questions, feel free to ask me! ;+)
Thanks,
David
Hmm.... I think the problem is that you don't have samba password files associated with the users yet. This can be solved by doing the following.
Code:
smbpasswd [username]
you will then be promopted to enter a password for the user. one you have entered in a password they should be good to go. Yes you can most certainly map a drive to your linux server. I actaully setup a custom script on my windows client to map the drives. I also setup my windows username and password so it won't prompt me for a username and password (I think. I am pretty sure I did not place the user and pass in the script.) Can't remember since I am not actually on my pc but I can verify that tomorrow.
Last edited by jstephens84; 11-30-2008 at 12:01 AM.
For Windows XP, an account for the "machine" using it's NETBIOS name plus a "$" is required on the Samba Server in the OS (Linux) and in the Samba password file (smbpasswd).
For example, if the XP machine is named “buckeye”, then the machine account name that you setup on the Linux machine would be “buckeye$”.
Without this account previously setup on the server, it is impossible for the client XP machine to "join" the domain nor access any of the Samba resources.
Also, I've figured out how to RUN "SMBPASSWD," but am not able to setup a "machine account." I'm sure it's a syntax error, but can't seem to get it to create the machine account, much less change the password.
You don't setup machine accounts. You setup user accounts. But what I think they were refering to by machine accounts was usernames on the workstation. so the syntax is
Code:
smbpasswd [username]
enter password:
reenter password:
You don't setup machine accounts. You setup user accounts. But what I think they were refering to by machine accounts was usernames on the workstation. so the syntax is
Code:
smbpasswd [username]
enter password:
reenter password:
Your reference to SMBPASSWD got me back to working with it some more, trying to figure out what I was missing. I had actually already created a UID & PW that matched my WinXP logon, but it wasn't working, not working and very frustrating. Then, the epiphany ...
I've solved it, fully being ASTID ("Another Stupid Thing I Did")!!!
I had everything right, exactly right, with one tiny exception. I logged in as my Admin UID & PW and created the user that is the same name as my WinXP Login & password. Doing it from my Admin UID & PW was the mistake. I needed to do it as ROOT!!! Once I logged in as ROOT & executed the "SMBPASSWD -a username" command (where username=my WinXP Login), I'm able to get access to the RAID5 array. Access - view but not change. I had to change permissions for the "user" group so that each member could alter the drive, and I'm up and running.
It is the ASTIDs that require the most energy to solve, but which have the most simple solutions. I knew there was some little thing I was doing wrong and that fixing it would bring much joy from the fruits of my labors.
NOW, I can start moving data off our local drives to the RAID5 array drive, and then can remove the IDE drives from our brand new boxes and install SATA drives - maybe even going to OpenSuSE on the desktop machines. Now, if I could just figure out how to fix Firefox so that it is recognized as the latest IE version - so that my wife can pay our bills on those secure websites that will only work with IE7 (or some such version).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.