On Sat, 2002-03-23 at 17:49, Michael Oatman wrote: > Thanks George, > > I tried using webmin but I think I'd rather fully understand and tweak > config file settings, since I was better off pre-webmin in terms of > what the XP boxen could access. I haven't been able to get SWAT to > work since I installed webmin either. It is greyed out in the KDE > service configuration app, and I don't see it anywhere in > /etc/rc.d/init.d, so I tried root# /usr/sbin/swat -s /etc/samba/smb.conf & > and I still cannot connect to port 901 on any interface, including > 127.0.0.1.
what does ps -aux say also in setup->system services is swat enbabled > But then again, I've had problems with pretty much every GUI that came > with RH7.2, and I've been trying not to use any of them. Thrice bitten? > Woah, there, that's plenty much. > > Michael > > --- George Abdo <[EMAIL PROTECTED]> wrote: > > Michael, > > > > Here is a copy of my SMB.CONF file. It is working now because I was not joining >the domain > > correctly beforehands. > > > > In you case, seeing you're using a workgroup environment, you wouldn't worry about >Domain > > specific settings. > > > > I have found that it is better to edit the SMB.CONF file using one of the many >utilities > > available: SWAT or Webmin. They are both pretty good. SWAT also has explanations >about all the > > entries you can make. In general, if you use an unmodified .conf file from the >RH7.2 cds, you'll > > get all printers shared and all home directories shared as well. > > > > Hope this helps. > > > > Let me know if you have any problems. > > > > ---------- begin smb.conf ------------- > [snip] > > ------------ end of smb.conf file ------------- > > > > > > > > > > On Fri, 22 Mar 2002 07:53:15 -0800 (PST) > > Michael Oatman <[EMAIL PROTECTED]> wrote: > > > > > That may help if I run a Win2K AS PDC which I'm thinking about doing now... > > > I'm just running in a workgroup at the moment. > > > > > > My prob is that once I have browsed to the Linux shares (I can see them), > > > I cannot access the writeable ones (I *can* access the read-only ones). > > > It gives me an invalid user/pass error, even though I authenticated as > > > a valid user just prior. Maybe there's something wrong with my > > > mksmbpasswd command. I edited the file and took out lines for users > > > like root, bin, etc., so that only users allowed to samba were present. > > > Must I not edit the smbpasswd file? > > > > > > George, could you send your current smb.conf (without sensitive info) > > > for comparison's sake to [EMAIL PROTECTED]? > > > > > > TIA, Michael > > > [EMAIL PROTECTED] > > > > > > --- George Abdo <[EMAIL PROTECTED]> wrote: > > > > Michael, > > > > > > > > In response to your last comment about having to go to \\server\share to > > > > actually connect, after fixing my problem (see my previous email) I am able to > > > > go start->run->\\server and actually see all the shares in there. > > > > > > > > Hope this helps. > > > > > > > > George > > > > > > > > > > > > > > > > > Michael Oatman <[EMAIL PROTECTED]> wrote: > > > > > > > > > > I'm following this thread with interest since I seem to be having > > > > > similar probs getting Samba 2.2.1a to work on RH7.2. > > > > > > > > > > 1) Specifically, when I browse (using KDE's Konqueror -- neither > > > > > Gnome's > > > > > Nautilus nor mozilla seem to be able to smb://) to any one of our > > > > > WinXP > > > > > boxen (only type) on our internal network, I get a prompt for > > > > > user/pass > > > > > which I enter successfully, then get displayed all available shares > > > > > on > > > > > whichever box to which I browse. So I then click on a share name > > > > > (for > > > > > which I have access) and I get the error message: > > > > > Could not access > > > > > <WinXP box name> > > > > > Invalid user/password combination > > > > > This happens immediately after I clicked on a share for which I > > > > > successfully entered a valid user/pass combo. > > > > > Anyone know what's going on? > > > > > > > > > > 2) None of the WinXP boxen on our internal network can access any of > > > > > the > > > > > writeable shares on the RH7.2 box in a workgroup. The shares are > > > > > browsable, although no valid user/pass combos will authenticate > > > > > properly. > > > > > > > > > > This sounds like the same kind of problem George is having. Why > > > > > could > > > > > one not browse to \\servername in an attempt to get to > > > > > \\servername\sharename? > > > > > > > > > > TIA, Michael > > > > > [EMAIL PROTECTED] > > > > > > > > > > --- "Anthony E. Greene" <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > On Thu, 21 Mar 2002, George Abdo wrote: > > > > > > >Here is the smb.conf file. I have edited out some of the network > > > > > details for > > > > > > >privacy. > > > > > > > > > > > > > >A domian computer account has been created and added on the > > > > > domain. I can also > > > > > > >ping the SAMBA server by netbios name on the domain (ie I can do > > > > > ping -a georepc > > > > > > > and I get the correct reply) > > > > > > > > > > > > > >Thanks for yor help. > > > > > > > > > > > > > >---------- begin smb.conf ------------- > > > > > > >;*******************section global***************** > > > > > > >[global] > > > > > > >workgroup = DOMNAME \\our domain name > > > > > > >netbios name = GEORGEPC > > > > > > >server string = NT 4 Workstation > > > > > > >interfaces = eth0 > > > > > > >security = DOMAIN > > > > > > >encrypt passwords = Yes > > > > > > >update encrypted = Yes > > > > > > >password server = PDC.company.com.au \\our PDC FQDN > > > > > > > > > > > > The password server must use a netbios name, not the FQDN. > > > > > > > > > > > > Make sure that there is an acount on the Linux system and in the > > > > > Windows > > > > > > domain that matches the username and password that you are trying > > > > > to use to > > > > > > connect to the Samba shared resource. You must also name that > > > > > resource > > > > > > using the servername and the resource name when connecting from a > > > > > Windows > > > > > > machine: \\servername\sharename > > > > > > > > > > > > Using just the servername will not work. Each resource has it's own > > > > > > > > > > > connection permissions, so you must tell samba what resource you > > > > > are trying > > > > > > to connect to so that Samba can figure out if you are authorized. > > > > > > > > > > > > > > > > > > Tony > > > > > > > > _______________________________________________ > > Redhat-list mailing list > > [EMAIL PROTECTED] > > https://listman.redhat.com/mailman/listinfo/redhat-list > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Movies - coverage of the 74th Academy Awards > http://movies.yahoo.com/ > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
