First, the SWAT issue. I have a RH 7.2 system recently installed, lots of RAM and VMware 3.1 installed. VMware did it's own SAMBA installation when I set it up. I have since downloaded the latest version, and removed the older version that came with VMware. Updated fine. When I run SWAT on this machine, it says SMB is not running even though I can start, stop and restart it from the command line. Says "OK" each time. I found a copy of smb in the /etc/init.d directory as well as the newly installed copy in /etc/rc.d/init.d Could these be conflicting as VMware services are sarting at boot time. If it was using the older version in the /etc/init.d directory could it be that this is the reason SWAT is saying the version I installed was not running? Second part of this question: if this is due to having VMware installed, how do I rectify the version issues? That is using the right version for SAMBA itself and still allow VMware to start it's services on boot. Second problem: I am able to see a /var/Shared folder on another Linux web server I have running SMABA (latest RH rpm version) just fine on my Win 2K and XP home edition machines on the smae workgroup. My Win Me machines (both the real thing and the one I run inside VMware) see the Linux machine and that it has shares but when I try to connect, it spins for a few moments and then asks me to supply a password only. It doesn't ask for the username. I am going to make an assumption here - (yes I know...) that Win Me is similar to 98/95 in that it attempts to log you onto the shares with the name you logged onto the local machine with? In which case, if I logged onto the WinMe machine as "Administrator", it will send "Administrator" as the logon to the samba box? I suppose further that there is no way around this except to create a user named "Administrator" on the SAMBA box? Am I even on the right path with these? I will try renaming the /etc/init.d version of smb to old_smb and restarting my machine. My guess is it will cause VMware to not boot with all it's functionality intact. Thanks folks. I did look back a few month in the Archives before asking these but didn't see anything on either of these specifically. Sean McHenry no-spam-smchenry@columbus.rr.com (remove the "no-spam-" -- Visit McHenry Technologies <http://www.mchenrytech.com> McHenry Technologies <http://www.mchenrytech.com> Hilliard, Ohio Powered by Red Hat Linux 7.2
followups: First, I installed the RedHat 7.2 rpm, I did not compile this version of SWAT or SAMBA. Both wer installed as part of the RPM. Checkeing the SAMBA 2.2.3a RPM with Query, it shows SWAT loaded as /usr/sbin/swat. Checking the /etc/xinet.d/swat file, it is looking for SWAT there. So that seems correct. I did notice "disable=yes" so I changed that to "disable=no" This however is due to my deleting and then reinstalling the RPM last night. Still the same issue. I can start smb from command line, it runs but SWAT reports it not running. SWAT does however see the nmb running. Very odd. I have this exact same rpm version installed on my server and on my workstation. Server sees everything correctly and is fully operational. The workstation has the VMware install however. NOTE: in the previous note I mentioned that there were 2 versions of smb loaded on the system. This is not correct. There was only the one version. It is /etc/rc.d/init.d/smb smbd is in /usr/sbin I see too that there is no inetd.conf file as this system is using xinetd. Nothing in those files pointing to anything swat related. Under the /etc/vmware directory there is a seperate smb.conf file but it has lines stating that other SAMBA servers can run without problems as the vmware version is bound to a NAT port of 192.168.67.1 my versions I have added are on a real network at 192.168.1.x I suppose I could try removing vmware for now. If all this works out I may not need it anyway. Perhaps there needs to be something written on how to add a samba server to a system with VMware already installed? This is confusing for me being new at all this. Thanks, By the way, as I compiled vmware, how do I get rid of it now? Sean -- Visit McHenry Technologies <http://www.mchenrytech.com> McHenry Technologies <http://www.mchenrytech.com> Hilliard, Ohio Powered by Red Hat Linux 7.2
Yep, I installed without any firewalls as I am behind a firewalled gateway. That shoulldn't be the issue here. I am trying to decide which I need more, SAMBA or VMware on the workstation. I may remove VMware, set up SAMBA seperatly and get it going then reinstall VMware without letting it install samba. I believe the only reason for installing smaba with VMware is to allow the Network Neighborhood to see other Win installations from inside the guest Windows OS. I can survive without this. As long as I can have access to the raw disk and write to my home directory from VMware, that would be all I need. Frankly, the only reason I even need VMware is to run Dreamweaver as I support a few web sites. This machine is a dual boot and I thought I should have access to Dreamweaver without having to reboot for a minor change to a site. I wish they could get it to run under WINE. Thanks, Sean -- Visit McHenry Technologies <http://www.mchenrytech.com> McHenry Technologies <http://www.mchenrytech.com> Hilliard, Ohio Powered by Red Hat Linux 7.2
Followed a suggestion to use the following at the term window: ps -fu root | grep smb (Thanks Joseph Loo) Reported: root 1493 1 0 02:30 ? 00:00:00 /usr/bin/vmware-smbd -D -l /dev/ So, I guess the samba version that is running is the one I installed with VMware. This would explain why SWAT keeps telling me smb isn't really running. SWAT is correct in that the version it wants to see, isn't running. The VMware installation is. This explains also why I can update the samba.conf file as much as I want and not notice any changes and why I can not connect from anywhere else. I will now work on either getting the VMware installed version to "lighten up" and let me in from outside, or, having VMware use the newer version I installed. Back to editing files by hand, if I can find them. I guess it is possible to have a VMware version and an RPM version on the same box as they seem to not recognize each other. Mostly I suppose due to VMware placing the renamed files in unusual places. I would like to see this written up someplace handy for future SAMBA and VMware users as an issue with VMware vs SAMBA installations. Thanks folks, I am open to suggestions... Sean McHenry -- Visit McHenry Technologies <http://www.mchenrytech.com> McHenry Technologies <http://www.mchenrytech.com> Hilliard, Ohio Powered by Red Hat Linux 7.2