Re: [CentOS] CentOS-Samba question
On Mon, Jun 2, 2008 at 10:16 AM, John R Pierce [EMAIL PROTECTED] wrote: win9X has horrible network username habits...you need to determine what username its running as... dirty trick, log off, and the username should be in the login prompt, just hit enter to relogin with the same username and the same blank local password.. on the SAMBA server, create that username as a linux user, AND `smbuser -a username`, assign it a smb password. when win98 prompts for a password, thats the username it will use, you get no choice, and win98 should be able to 'save' that password (if you check said box on the login prompt), which causes it to be saved to a username.pwd file (I think thats the name of the password cache). More progress: It occurred to me that somewhere along the line I had not given my CentOS guest user smb access, so I ran smbpasswd and set the guest password to match its login password. When I went back to W98, I tried to add the network printer - it recognized the name (\\mhrichter\MPP1100) and asked for a password. I gave it the guest password, and it proceeded to try to install it. I put in the CD, went through all the (right) moves to install the driver, and then the moment of truth: W98 said I had to reboot. I knew I was in trouble. I rebooted, and, lo and behold, the printer was suddenly offline and unavailable (there was no change to the CentOS host or the printer at all). I deleted the printer to start over, but this time W98 said the printer was offline when I input the name and the password. W98 still can't see the network or any of the shares in the Network Neighborhood, but at least I can reach for it by name. Any doors or windows in this wall? Thanks. mhr PS: I have always said that I don't really hate Window$, I just prefer working in and on Unix/Linux. I don't think that's true any more, although I must say that of all the versions of Window$ I've ever used, XP is the least objectionable. PPS: Yes, this is Window$ XP Pro (but I think it's still SP1), and 98 SE. It's still Window$, a Micro$oft product, which really says it all. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
MHR wrote: On Mon, Jun 2, 2008 at 10:16 AM, John R Pierce [EMAIL PROTECTED] wrote: win9X has horrible network username habits...you need to determine what username its running as... dirty trick, log off, and the username should be in the login prompt, just hit enter to relogin with the same username and the same blank local password.. on the SAMBA server, create that username as a linux user, AND `smbuser -a username`, assign it a smb password. when win98 prompts for a password, thats the username it will use, you get no choice, and win98 should be able to 'save' that password (if you check said box on the login prompt), which causes it to be saved to a username.pwd file (I think thats the name of the password cache). More progress: It occurred to me that somewhere along the line I had not given my CentOS guest user smb access, so I ran smbpasswd and set the guest password to match its login password. When I went back to W98, I tried to add the network printer - it recognized the name (\\mhrichter\MPP1100) and asked for a password. I gave it the guest password, and it proceeded to try to install it. I put in the CD, went through all the (right) moves to install the driver, and then the moment of truth: W98 said I had to reboot. I knew I was in trouble. I rebooted, and, lo and behold, the printer was suddenly offline and unavailable (there was no change to the CentOS host or the printer at all). I deleted the printer to start over, but this time W98 said the printer was offline when I input the name and the password. W98 still can't see the network or any of the shares in the Network Neighborhood, but at least I can reach for it by name. Any doors or windows in this wall? It might be easier to give up.* For years, I had a single inkjet printer on my modest home network, physically connected to this machine. It works great once setup until something changes. (Versions of Windows and/or versions and/or flavors of Linux on another box.) A while back, I added a laser printer, choosing one that could go either parallel, USB or ethernet. I got out my crimpers, made a network cable and haven't looked back. What a pleasure! It was a breeze to set up and it's alway visible to any computer on the network. The point is, unless your time is virtually worthless, you might think about a print server. Netgear, D-link and Linksys all make them. BTW, my laser printer is a Brother HL-5250 DN and I'm pretty happy with it. Thanks. mhr PS: I have always said that I don't really hate Window$, I just prefer working in and on Unix/Linux. I don't think that's true any more, although I must say that of all the versions of Window$ I've ever used, XP is the least objectionable. PPS: Yes, this is Window$ XP Pro (but I think it's still SP1), and 98 SE. It's still Window$, a Micro$oft product, which really says it all. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- POLITICS n. Strife of interests masquerading as a contest of principles --Ambrose Bierce ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
Robert wrote: It might be easier to give up.* For years, I had a single inkjet printer on my modest home network, physically connected to this machine. It works great once setup until something changes. (Versions of Windows and/or versions and/or flavors of Linux on another box.) A while back, I added a laser printer, choosing one that could go either parallel, USB or ethernet. I got out my crimpers, made a network cable and haven't looked back. What a pleasure! It was a breeze to set up and it's alway visible to any computer on the network. The point is, unless your time is virtually worthless, you might think about a print server. Netgear, D-link and Linksys all make them. BTW, my laser printer is a Brother HL-5250 DN and I'm pretty happy with it. Those mini print servers would save you a lot of time by the sound of it, if it's just the printer sharing that's the problem. Or if distance is not an issue, it could possibly be directly connected to one of the windows machines and shared from there. However, that would result in you having to leave the windows box on all the time for the printing to be enabled. Well, that's my 2 cents worth anyway, hope it helps. -Ross- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
I have a couple of partial solutions. For the remote Windows XP boot: 1) The firewall (ZoneAlarm) was blocking all pings. Why? I have no idea. According to its program data, ping was enabled for local and internet access, and the allow server fields were unset (meaning that it was supposed to ask). I solved this by turning off ZoneAlarm. 2) I still could not get through to the server, so I poked around on the web. I kept getting a ICMP host mhrichter unreachable - admin prohibited,) and I found one QA that suggested flushing the iptables, so I did. Voila - the shares and printers are now available across the network. Unfortunately, this did nothing to help the remote Windows 98 boot, which still can't see the network server or its resources. Also unfortunately, the 98 boot is the more important one to have printer access. (Don't ask.) Any other ideas? Thanks. mhr ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] CentOS-Samba question
Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MHR Sent: Sunday, June 01, 2008 6:34 PM To: CentOS mailing list Subject: Re: [CentOS] CentOS-Samba question On Sun, Jun 1, 2008 at 5:20 AM, John [EMAIL PROTECTED] wrote: If you logged on from the Windows Guest Account then you know it is authenticating by the guest or nobody account that's on the Samba Server. The previous config file I that I stuck in the mail for you will work on a Windows Client machine providing there is sufficient name and ip address translation. It will authenticate against the samba server nobody account. IE, as in provide anonymous user name and password authentication so the user will not have to enter a password. That is to get you going on the right path. From there you will need to incorporate some type of user mode authentication. You don't want the whole world to access it. Clarification: my XP guest is my VMWare Windows XP guest OS running on top of my CentOS host. I use a known account to logon from the XP guest OS to the CentOS host and all works just fine, except that I changed something last night, or recently, and the guest XP can no longer see the host machine in the workgroup. This is a very minor problem, unless there's some connection we aren't talking about yet. . OK, you don't need to just open the Workgroup. All you really need to do is just add the share on the Samba server. Actually, I think it was when either 5.0 or 5.1 came out that the sample config file you sent, with a few minor differences, was posted and I have a copy on my machine. I used that, in part, to construct the config file I am using. Today, I am trying to test with the remote XP machine, and the results get weirder (to me). I can now see the CentOS server in the XP's network under the workgroup, but I can't open the host for access to either the shares or the printers. I can still ping the server, I can even open a putty window to it and login just fine. But, now, I can no longer ping the XP machine from my server (!!!) at all. I am running zonealarm (free) on the XP machine and am wondering if there might be a problem there. Reason I mention this is that ZA used to allow control of access by program and by machine, but now it only offers program control (which really stinks - any other free Win$$$ firewalls worth a hoot out there?). So I can't even tell if my server is getting blocked by the firewall any more. Foo. Mhr - Actually my opinion on that is is to trash the ZoneAlarm Firewall. Use the firewall that came with windows. It actually works just as good. That is if there is someone that knows how to config it. For your sake. The heck of it Disable all firewalls in all clients and servers your using and see what type of access you have to the sambaserver. See your fighting two firewalls at once on your DomU and DomO. If I remember right ports 138 and 139 have to be open on the Win98 clients they will work over NetBios where as xp will work over TCP/IP. JohnStanley ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
On Mon, Jun 2, 2008 at 12:25 AM, MHR [EMAIL PROTECTED] wrote: I have a couple of partial solutions. : Unfortunately, this did nothing to help the remote Windows 98 boot, which still can't see the network server or its resources. Also unfortunately, the 98 boot is the more important one to have printer access. (Don't ask.) It was late last night and I forgot to include any useful information here. The 98 boot has an automatic (no password) logon. As I said, I can't use the Network Neighborhood to see anything on the server - in fact, it can't even see the workgroup, even after I double checked all the setting. However, I can attempt to attach to resources, but, e.g., when I try to attach to my mpp1100 printer, it posts a password input window for resource \\mhrichter\IPC$, but I can't figure out which password, and none of the ones I tried works. On the server side, I have (something like) this for my smbusers (I'm going from memory here, but it's not too hard): # root = administrator admin mark = mark guest = esther ruth guest smbguest nobody = pcguest (Yes, I have root access from the samba clients disabled.) The default login account is esther, but the passwords for guest and mark don't work, and no password also does not work. When I get home, I'll add an account for esther on the server, fix up the smbusers file and see what happens. Another anomaly - when I was logged into the XP boot as mark, I could not connect to the printer without specifying a password (with the connect as another user dodge), even though the passwords on both machines are the same. Ok, back to work. :-) Thanks, everyone, especially John. mhr ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
John R Pierce wrote: MHR wrote: The 98 boot has an automatic (no password) logon. As I said, I can't win9X has horrible network username habits...you need to determine what username its running as... dirty trick, log off, and the username should be in the login prompt, just hit enter to relogin with the same username and the same blank local password.. on the SAMBA server, create that username as a linux user, AND `smbuser -a username`, assign it a smb password. when win98 prompts for a password, thats the username it will use, you get no choice, and win98 should be able to 'save' that password (if you check said box on the login prompt), which causes it to be saved to a username.pwd file (I think thats the name of the password cache). It's username.PWL. Boot to dos or if you can stand it - safe mode delete the users file. I remember doing that often for folks who constantly foobared their login. -- Toby Bluhm Alltech Medical Systems America, Inc. 30825 Aurora Road Suite 100 Solon Ohio 44139 440-424-2240 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
On Mon, Jun 2, 2008 at 10:16 AM, John R Pierce [EMAIL PROTECTED] wrote: win9X has horrible network username habits...you need to determine what username its running as... dirty trick, log off, and the username should be in the login prompt, just hit enter to relogin with the same username and the same blank local password.. on the SAMBA server, create that username as a linux user, AND `smbuser -a username`, assign it a smb password. when win98 prompts for a password, thats the username it will use, you get no choice, and win98 should be able to 'save' that password (if you check said box on the login prompt), which causes it to be saved to a username.pwd file (I think thats the name of the password cache). does that make sense? Well, sort of, but we are talking about Micro$oft and Window$$$ here :-) Now that I've had some rest, that's pretty much what I was going to try next. Wish me luck! Thanks. mhr ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
MHR wrote: The 98 boot has an automatic (no password) logon. As I said, I can't use the Network Neighborhood to see anything on the server - in fact, it can't even see the workgroup, even after I double checked all the setting. However, I can attempt to attach to resources, but, e.g., when I try to attach to my mpp1100 printer, it posts a password input window for resource \\mhrichter\IPC$, but I can't figure out which password, and none of the ones I tried works. win9X has horrible network username habits...you need to determine what username its running as... dirty trick, log off, and the username should be in the login prompt, just hit enter to relogin with the same username and the same blank local password.. on the SAMBA server, create that username as a linux user, AND `smbuser -a username`, assign it a smb password. when win98 prompts for a password, thats the username it will use, you get no choice, and win98 should be able to 'save' that password (if you check said box on the login prompt), which causes it to be saved to a username.pwd file (I think thats the name of the password cache). does that make sense? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
On Sat, May 31, 2008 at 5:55 PM, John [EMAIL PROTECTED] wrote: I think your reading the wrong guide, try this one and this has traversed on long enough. Almost Two weeks now. 1) This has been going on, on and off, for a lot longer than two weeks. 2) I was hoping that it would be considered long enough when the problem is solved. 3) My samba configuration is only a part of the problem, and it works for my Windows XP guest, even with all the tweaks I've added/used. The problem also has (a lot) to do with the Windows configuration, which may not be perfect, since I used the wrong guide to set it up and check it, but nothing here even addresses that. But thank you for your opinion. Samba 3 By Example: http://us3.samba.org/samba/docs/man/Samba3-ByExample/ Samba 3 How To: http://us3.samba.org/samba/docs/Samba3-HOWTO.pdf http://us3.samba.org/samba/docs/man/Samba3-HOWTO/ These were where I started out, and how I got what I have to work with my WXP guest in the first place. I was using the other guide as an additional resource - it /is/ on the samba site, after all, and they don't appear to have a step-by-step guide for samba 3+. Thanks. mhr ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
I just found something interesting. I brought up my XP guest, and it had no trouble at all connecting to the shares, but it couldn't open the workgroup at all and the printer had become disconnected. I could not reconnect through the workgroup (duh), but if I just input the network name, the printer came up just fine. So: I can connect to my shares from the XP guest, and I can connect to my printer from the XP guest, I just can't open the workgroup (this is relatively new, like, since I began messing with the smb.conf file in the last two weeks). Don't know exactly what that means, but I haven't given up yet. Tomorrow I'll dig in more on the remote machine and see where that all takes me. Any helpful suggestions still welcome :-) mhr ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] CentOS-Samba question
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MHR Sent: Sunday, June 01, 2008 4:01 AM To: CentOS mailing list Subject: Re: [CentOS] CentOS-Samba question On Sat, May 31, 2008 at 5:55 PM, John [EMAIL PROTECTED] wrote: I think your reading the wrong guide, try this one and this has traversed on long enough. Almost Two weeks now. 1) This has been going on, on and off, for a lot longer than two weeks. 2) I was hoping that it would be considered long enough when the problem is solved. 3) My samba configuration is only a part of the problem, and it works for my Windows XP guest, even with all the tweaks I've added/used. The problem also has (a lot) to do with the Windows configuration, which may not be perfect, since I used the wrong guide to set it up and check it, but nothing here even addresses that. But thank you for your opinion. Samba 3 By Example: http://us3.samba.org/samba/docs/man/Samba3-ByExample/ Samba 3 How To: http://us3.samba.org/samba/docs/Samba3-HOWTO.pdf http://us3.samba.org/samba/docs/man/Samba3-HOWTO/ These were where I started out, and how I got what I have to work with my WXP guest in the first place. I was using the other guide as an additional resource - it /is/ on the samba site, after all, and they don't appear to have a step-by-step guide for samba 3+. Thanks. Mhr - Hrmm. The Samba 3 guide covers all Samba Versions 3 and greater. There are only minimal differences between the versions. Some options are being phased out though so keep that in mind. Do this just for kicks. Take your samba config file and rename it. Take what I posted in email to you and use it for the main samba config fig file. You will only need to change the directory paths to match yours. Try one share at a time. You should be able to access it (the samba server share) with any windows xp user account, wether it's a guest account or not. You will need the correct chmod and chown with the -R option on the shared folder. Sometime when using the GUI in changing the folder and file permissions, it want allow Recursiveness to the folder thus use the shell command to do it. johnstanley. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] CentOS-Samba question
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MHR Sent: Sunday, June 01, 2008 5:40 AM To: CentOS mailing list Subject: Re: [CentOS] CentOS-Samba question I just found something interesting. I brought up my XP guest, and it had no trouble at all connecting to the shares, but it couldn't open the workgroup at all and the printer had become disconnected. I could not reconnect through the workgroup (duh), but if I just input the network name, the printer came up just fine. --- If you logged on from the Windows Guest Account then you know it is authenticating by the guest or nobody account that's on the Samba Server. The previous config file I that I stuck in the mail for you will work on a Windows Client machine providing there is sufficient name and ip address translation. It will authenticate against the samba server nobody account. IE, as in provide anonymous user name and password authentication so the user will not have to enter a password. That is to get you going on the right path. From there you will need to incorporate some type of user mode authentication. You don't want the whole world to access it. So: I can connect to my shares from the XP guest, and I can connect to my printer from the XP guest, I just can't open the workgroup (this is relatively new, like, since I began messing with the smb.conf file in the last two weeks). Don't know exactly what that means, but I haven't given up yet. Tomorrow I'll dig in more on the remote machine and see where that all takes me. Any helpful suggestions still welcome :-) Mhr -- OK, you don't need to just open the Workgroup. All you really need to do is just add the share on the Samba server. Here we go like this; Tools | Map Network Drive or Right Click My Computer and Select Map Network Drive. What I believe you concern is about Browsing the Network? You don't need to Browse the network in order to connect to the shares. But you will have to add each share you have on the samba server to the windows clients. Now if your really concerned about eyeball browsing the network (I am not making fun of you either) Go To Start | Run |, and in the run command box type net use \\samba_server_name_here\. Then they should, I say should again be in Network Neighborhood. Also the your Win98 client may need to set up with an LMHOSTS file and using NetBios/tcpip. They can be configured to use the Samba servers WIN Server to provide hostname to ip address translation. It would really be justafiable to have a DNS Server on the network to do the translation. Another thing that comes to mind is that the Win98 clients are not authenticating against the given user account. Now why is that? If I recall right there is an issue with password encryption. I believe it's mentioned in the earlier stated links I gave you and that would be in one of the downloadable PDF Files. Wish you Luck, JohnStanley ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
On Tue, May 27, 2008 at 5:17 PM, MHR [EMAIL PROTECTED] wrote: On Tue, May 27, 2008 at 4:51 PM, Christopher Chan [EMAIL PROTECTED] wrote: Try adding 'guest ok = yes' to the printer share configuration. I will - thanks. I did - no change. ...I think you need to pick a bit more on Windows networking...more reading of the books/documentation provided with samba should help. Okay, I went through the Samba Guide at http://us3.samba.org/samba/docs/using_samba. I read chapters 1, 2 3 fairly thoroughly, and I'm going through 12 (troubleshooting) now. One small problem is that this is for Samba 2.2 and I'm on 3.0.25. Be that as it may Let me start up front with this: both Windows boots can ping the CentOS Samba Server. Neither one can see it in their M$ Network. I went through chapter 3 step by step for both the W98 and WXP boots, and I can't see my C5.1 from W98 at all, and I can't see anything that's on the C5.1 from WXP. I started going through the troubleshooting chapter, and I got up to this point with W98: 'net use * \\mhrichter\tmp' hangs for about a minute, then comes back with an Error 59 - unknown error. In the log, I see this (I did it twice): [EMAIL PROTECTED] samba]# cat mhrichter.log [2008/05/31 10:54:03, 1] smbd/service.c:make_connection_snum(1033) mhrichter (192.168.0.100) connect to service tmp initially as user nobody (uid=99, gid=99) (pid 19903) [2008/05/31 10:54:07, 1] smbd/service.c:close_cnum(1230) mhrichter (192.168.0.100) closed connection to service tmp [EMAIL PROTECTED] samba]# grep nobody /etc/passwd nobody:x:99:99:Nobody:/:/sbin/nologin nfsnobody:x:4294967294:4294967294:Anonymous NFS User:/var/lib/nfs:/sbin/nologin [EMAIL PROTECTED] samba]# In case you don't remember, the tmp share is configured thus: [tmp] comment = Temporary file space path = /tmp writeable = yes guest ok = yes So, in theory, anyone should be able to see it, read and write to it, etc. (Yes, I know there's a potential space problem here, but these machines are all on a private subnet, I'm the only one who has a clue how to really make use of them, and there's about 35GB left on /, including /tmp.) This particular problem is not addressed in the guide, so I'm stuck (again). I'll be trying the WXP boot in a few minutes, where my logon /should/ work (but doesn't) and I'll see what turns up in the log for that. But, in the mean time, any ideas? Thanks. mhr ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] CentOS-Samba question
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MHR Sent: Saturday, May 31, 2008 2:57 PM To: CentOS mailing list Subject: Re: [CentOS] CentOS-Samba question On Tue, May 27, 2008 at 5:17 PM, MHR [EMAIL PROTECTED] wrote: On Tue, May 27, 2008 at 4:51 PM, Christopher Chan [EMAIL PROTECTED] wrote: Okay, I went through the Samba Guide at http://us3.samba.org/samba/docs/using_samba. I read chapters 1, 2 3 fairly thoroughly, and I'm going through 12 (troubleshooting) now. -- I think your reading the wrong guide, try this one and this has traversed on long enough. Almost Two weeks now. Below included is also a work (BASIC) Configuration file to get you going. Then you will need to go on and experiment from there. This configuration below will work with a forced user = use_name. Or change the security mode to user and create accounts on the samba server for the windows clients. Those accounts **HAVE** to mach the Window user and password logons! Please read the comented sections. Hope All This Helps and the Formatting Stays, JohnStanley Samba 3 By Example: http://us3.samba.org/samba/docs/man/Samba3-ByExample/ Samba 3 How To: http://us3.samba.org/samba/docs/Samba3-HOWTO.pdf http://us3.samba.org/samba/docs/man/Samba3-HOWTO/ # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command testparm # to check that you have not made any basic syntactic errors. # #--- # SELINUX NOTES: Pay Attention Here # # If you want to use the useradd/groupadd family of binaries please run: # setsebool -P samba_domain_controller on # # If you want to share home directories via samba please run: # setsebool -P samba_enable_home_dirs on # # If you create a new directory you want to share you should mark it as # samba-share_t so that selinux will let you write into it. # Make sure not to do that on system directories as they may already have # been marked with othe SELinux labels. # # Use ls -ldZ /path to see which context a directory has # # Set labels only on directories you created! # To set a label use the following: chcon -t samba_share_t /path # # If you need to share a system created directory you can use one of the # following (read-only/read-write): # setsebool -P samba_export_all_ro on # or # setsebool -P samba_export_all_rw on # # If you want to run scripts (preexec/root prexec/print command/...) please # put them into the /var/lib/samba/scripts directory so that smbd will be # allowed to run them. # Make sure you COPY them and not MOVE them so that the right SELinux context # is applied, to check all is ok use restorecon -R -v /var/lib/samba/scripts # #-- # #=== Global Settings = [global] #Below line is an Option... socket options = TCP_NODELAY # --- Netwrok Related Options - # # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH # # server string is the equivalent of the NT Description field # # netbios name can be used to specify a server name not tied to the hostname # # Interfaces lets you configure Samba to use multiple interfaces # If you have multiple network interfaces then you can list the ones # you want to listen on (never omit localhost) # # Hosts Allow/Hosts Deny lets you restrict who can connect, and you can # specifiy it as a per share option as well # workgroup = Workgroup server string = Samba Server Version %v ; netbios name = MYSERVER ; interfaces = lo eth0 192.168.0.1/24 192.168.0.254/24 ; hosts allow = 127. 192.168.0. 192.168.0. # --- Logging Options - # # Log File let you specify where to put logs and how to split them up. # # Max Log Size let you specify the max size log files should reach # logs split per machine log file = /var/log/samba/%m.log # max 50KB per log file, then rotate max log size = 50 # --- Standalone Server Options # # Scurity can be set to user, share(deprecated) or server(deprecated) # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. #When commented out Samba reverts to share mode ah ha! security = share # passdb backend = tdbsam # --- Domain Members Options # # Security must be set to domain or ads (Active Directory Server) # # Use the realm option only with security = ads
Re: [CentOS] CentOS-Samba question
On Sun, May 25, 2008 at 3:38 AM, Christopher Chan [EMAIL PROTECTED] wrote: Do they should up if you run the command below in the Linux host? smbclient -L //localhost I'm guessing you meant show up and yes, everything looks normal, but only if I use a -U option with a known user. Is there a way to allow printer access without a user login? Not even the home share? Have you created a machine account for the XP guest? Not sure what a machine account is - there is a user account on the host that has the same user name and password as the one on the guest. Thanks. mhr ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
MHR wrote: On Sun, May 25, 2008 at 3:38 AM, Christopher Chan [EMAIL PROTECTED] wrote: Do they should up if you run the command below in the Linux host? smbclient -L //localhost I'm guessing you meant show up and yes, everything looks normal, but only if I use a -U option with a known user. Is there a way to allow printer access without a user login? Try adding 'guest ok = yes' to the printer share configuration. Not even the home share? Have you created a machine account for the XP guest? Not sure what a machine account is - there is a user account on the host that has the same user name and password as the one on the guest. ...I think you need to pick a bit more on Windows networking...more reading of the books/documentation provided with samba should help. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
On Tue, May 27, 2008 at 4:51 PM, Christopher Chan [EMAIL PROTECTED] wrote: Try adding 'guest ok = yes' to the printer share configuration. I will - thanks. ...I think you need to pick a bit more on Windows networking...more reading of the books/documentation provided with samba should help. Definitely - I'm working on that in my copious (gales of laughter) spare time, along with the other two or three hundred projects :-) mhr ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-Samba question
MHR wrote: My main system is a CentOS 5.1 64-bit desktop with gobs of disk and a couple of printers attached that work just fine. I have it set up with samba so my VMWare guest Windows XP can access most of the files and the printers. But, when I try to connect to the printers from a remote machine that has a Win98/WinXP dual boot, I can't see the printers at all. Do they should up if you run the command below in the Linux host? smbclient -L //localhost Both 98/XP can ping the host by IP address or by name (I've updated the host on both and the lmhost file on the 98 boot), but the 98 boot can't see the network at all, and the XP boot can't see anything on my CentOS box, although it at least sees that the box is there. Not even the home share? Have you created a machine account for the XP guest? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] CentOS-Samba question
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MHR Sent: Saturday, May 24, 2008 4:00 PM To: CentOS mailing list Subject: [CentOS] CentOS-Samba question My main system is a CentOS 5.1 64-bit desktop with gobs of disk and a couple of printers attached that work just fine. I have it set up with samba so my VMWare guest Windows XP can access most of the files and the printers. But, when I try to connect to the printers from a remote machine that has a Win98/WinXP dual boot, I can't see the printers at all. Both 98/XP can ping the host by IP address or by name (I've updated the host on both and the lmhost file on the 98 boot), but the 98 boot can't see the network at all, and the XP boot can't see anything on my CentOS box, although it at least sees that the box is there. Here's my smb.conf: # Global parameters [global] workgroup = MARKHOME domain master = yes preferred master = yes server string = Samba Server printcap name = /etc/printcap cups options = raw log file = /var/log/samba/%m.log max log size = 50 password server = none username map = /etc/samba/smbusers socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 wins support = yes dns proxy = no idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /bin/false winbind use default domain = no [homes] comment = Home Directories valid users = %S path = /home/%u create mask = 664 directory mask = 775 writeable = yes browseable = yes [tmp] comment = Temporary file space path = /tmp writeable = yes guest ok = yes [printers] comment = All Printers path = /var/spool/samba browseable = yes printable = yes What am I missing? Thanks. Mhr -- Simple Configuration... Your Global is wrong. This is for sane simple Printing! Read the samba howto's on samba.org. [global] printing = bsd load printers = yes [printers] path = /var/spool/samba printable = yes public = yes writable = no ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
