Re: [Samba] Samba installation discrepancies
Eric Evans wrote: Samba colleagues, I promise to limit my postings to this list to one message per day from now on, and to keep my messages focussed on very specific technical issues. I think I have gotten over my initial panic at the weirdly broken Samba installation and am now in a troubleshooting mode. The drama of all my Samba 3 difficulties now seems to be due to a faulty Samba installation. Symptoms are: bin/nmbd -V and bin/smbd -V both return version 2.2.7a, even though I did a complete installation of version 3.0.22 and the installation (including the 'make install') ran completely through to its completion with no error messages. Also, nmbd is currently running but smbd is not running. And when I try to run smbclient I get the messages read_socket_with_timeout: timeout read. read error = Connection reset by peer. session request to PLEIADES failed (Read error: Connection reset by peer) read_socket_with_timeout: timeout read. read error = Connection reset by peer. session request to *SMBSERVER failed (Read error: Connection reset by peer) My environment is Solaris 8. Has anyone else had any difficulty getting Samba 3 to install properly on Solaris 8? Thanks very much, Eric Oh, yeah, you can use chkconfig to see what services (e.g., winbindd, nmbd, smbd, etc) are running and to set them to turn on automatically at bootup. Eric Hines -- Victorious warriors win first and then go to war, while defeated warriors go to war first and then seek to win. --Sun-Tzu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba installation discrepancies
Eric Evans wrote: Samba colleagues, I promise to limit my postings to this list to one message per day from now on, and to keep my messages focussed on very specific technical issues. I think I have gotten over my initial panic at the weirdly broken Samba installation and am now in a troubleshooting mode. The drama of all my Samba 3 difficulties now seems to be due to a faulty Samba installation. Symptoms are: bin/nmbd -V and bin/smbd -V both return version 2.2.7a, even though I did a complete installation of version 3.0.22 and the installation (including the 'make install') ran completely through to its completion with no error messages. Also, nmbd is currently running but smbd is not running. And when I try to run smbclient I get the messages read_socket_with_timeout: timeout read. read error = Connection reset by peer. session request to PLEIADES failed (Read error: Connection reset by peer) read_socket_with_timeout: timeout read. read error = Connection reset by peer. session request to *SMBSERVER failed (Read error: Connection reset by peer) My environment is Solaris 8. Has anyone else had any difficulty getting Samba 3 to install properly on Solaris 8? Thanks very much, Eric Which installation package did you use? The one from samba.org, by the Samba team, uses a default directory structure optimized purely for Samba. It's a standard structure, and it's usable just fine with any OS. However, there also are Samba rpm (etc) packages that are built by the various OS folks that are optimized for their OS and use a directory structure that these folks think is better (/e.g./, Novell builds an rpm for Samba to run on SuSE that they think is a better directory structure). Aside from directory structure, all the sambas of a given version are identical--only the rpm packages differ and only by where each sends its files. However, the differing/conflicting directory structures can lead to problems like this. Suggest you explore your Solaris 8 and locate the files for Samba 2.2.7a (I assume that's your original installation) and the files for the Samba3 you thought you installed. Your Samba3 installation probably is a solid installation; however: I suspect your original version was optimized for Solaris, and your upgrade version may have come from samba.org. If that's the case, I suggest you find the rpm (or the installation package type that Sun uses) that's been built for Solaris 8 and install that, as the easiest way out of this. Eric Hines -- Victorious warriors win first and then go to war, while defeated warriors go to war first and then seek to win. --Sun-Tzu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Sorry for all the messages, I'm just trying to get a few answers here
I'm new to Samba, too, but here's my two cents worth on your questions: Eric Evans wrote: snip Please let me summarize the points that I'm confused about: 1. Why do I need to use wins support in my smb.conf? I don't see the point of this since it seems to me we are not using WINS. WINS is Windows Internet Naming Service. It's how MS machines find out who they are, when that matters, as it does when you're running a PDC. When you weren't this didn't matter, but with a PDC, you need WINS server IP in your Windows machines, and you need wins support = yes in your smb.conf. 2. If I don't have access to the DHCP server to modify its configuration, how can I accomplish Craig's suggestion of putting the IP address of my Samba server in the WINS server list on the DHCP server, and how can I define the node type? Surely there must be other Samba users who don't have configuration access to their DHCP server. How do they deal with this? AFAIK, you don't need both WINS and DHCP, just one or the other. Both doesn't hurt (as long as the IP addresses don't conflict with each other), but you should be able to do fine with WINS--put your WINS server's IP address (i.e., the address of your Samba server, since it's typically the WINS server in this kind of environment) in your Windows PCs' locations as suggested earlier. By the way, what does your nsswitch.conf file say on this? It should have a line in it that says something like hosts: files dns wins Hosts: is required, or the line won't work, and wins is necessary or your network services won't be able to deal with wins resolutions. The others are necessary, too, but they're not relevant to the present problem. 3. Why is my windows client trying to send to a WINS server anyway? See 1. above. 4. The [homes] share, at least in Samba 2, always had a special meaning. It was always interpreted by Samba as mapping to the user's home directory. Does Samba 3 no longer give this special meaning to the [homes] share? The [homes] share has the same meaning in S3 as in S2. However, before a user can get to his/her [homes] share via a PDC, s/he has to log in (which is transparent to the user, once everything is running properly--s/he has already logged in, when s/he logged into his/her PC). Not only is it necessary for your Samba server to join the domain, but the PC must, also. The Windows PC can only be joined to the domain (and this must be done explicitly for the PC) by an administrator or someone with administrator privileges. In lots of LANs, the PC user has these privileges, but this is poor security practice. 5. PDC or BDC was not necessary in Samba 2 to connect to the [homes] directory. Why is it necessary in Samba 3? Are there any other special shares in Samba that one MUST have PDC or BDC access in order to use? See 4. above. A PDC/BDC isn't necessary under Samba 3 to connect to a homes share. What's different in S3 is the ability to set Samba up as a P/BDC. Setting up Samba as a P/BDC improves security for the LAN, and it's this P/DC and increased security that complicates a bit the process of getting connected. snip Best wishes, Eric Hope this helps. Eric Hines -- Victorious warriors win first and then go to war, while defeated warriors go to war first and then seek to win. --Sun-Tzu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Updating to Samba 3
John H Terpstra wrote: On Friday 07 July 2006 19:27, Craig White wrote: On Fri, 2006-07-07 at 16:54 -0700, Huck wrote: This link may be of some assistance to those updating from Samba 2. http://www.phptr.com/articles/article.asp?p=419048rl=1 Since the official Samba documentation is authoritative and actually covers this subject, pointing to another 3rd party for reference is likely to cause confusion...especially when a confused administrator hasn't consumed the official documentation to begin with. Craig Well, actually, the PHPTR link points to an older copy of the official documentation. Best advice for newbies is to point them at: http://www.samba.org/samba/docs/Samba3-ByExample.pdf The PDF is easier to read for many, but the HTML link is preferred by others. http://www.samba.org/samba/docs/Samba3-ByExample.html Craig, You've been fielding a lot of activity for a while now - you know the ropes. Advanced users should consult the HOWTO, and a newbie would easily get lost in the wild woods there. Despite that, most newbies apparently want to master brain surgery before they ever attempt the basics. Cheers, John T. But, but, if we master the brain surgery right off the bat, doesn't this have the basics subsumed in it, and wouldn't this, then, be a more efficient use of everyone's time? The journey of a thousand steps would be immeasurably shortened if we could only skip all that middle part and go right to the last step :^) Eric Hines -- Victorious warriors win first and then go to war, while defeated warriors go to war first and then seek to win. --Sun-Tzu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbd not starting
Burton B Williams wrote: Hey all, I recently installed fedora core 5 and then installed samba. I however encountered a problem. The smbd thread would not start. Can anytone shead some light on why this might have happened. In the original installation of the OS I installed samba. However I encountered that same problem. The smbd would not start. I then tried installing samba from the source and still the same problem. I check the path of the smbd and it gave me the OS default path. I tried forcing the installation path but still the same problem. Any thoughts on the matter would be appreciated Thank you. -B Sorry for the direct post You might try chkconfig --list smb (check the man page for the exact syntax) to check the status of your smb. Then try chkconfig --add smb (again, checking the man page; I'm writing these commands from hazy memory). Chkconfig is a useful utility for managing a number of services. Eventually, you might find it useful for nmbd and winbindd, also. Eric Hines -- Those who are afraid to take the next step will have wasted their entire previous journey. --Baron Manfred von Richthofen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbd not starting
I've never used webmin, but SWAT will construct a syntactically correct smb.conf. Of course, that just means that samba won't crash when you start it; it does not guarantee that what you've configured correctly from a syntax perspective actually will accomplish anything. You can check the config file, also, with testparm, which will check that the sections are built correctly, and then let you see them explicitly. Eric Hines Adam Williams wrote: I *believe* that swat and/or webmin has smb.conf checking utility to make sure there are no errors in it. You may want to look into starting those and having it check smb.conf for errors. Burton B Williams wrote: Hey all, I recently installed fedora core 5 and then installed samba. I however encountered a problem. The smbd thread would not start. Can anytone shead some light on why this might have happened. In the original installation of the OS I installed samba. However I encountered that same problem. The smbd would not start. I then tried installing samba from the source and still the same problem. I check the path of the smbd and it gave me the OS default path. I tried forcing the installation path but still the same problem. Any thoughts on the matter would be appreciated Thank you. -B -- Those who are afraid to take the next step will have wasted their entire previous journey. --Baron Manfred von Richthofen -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] What is the meaning of the output from smbstatus?
Jeremy Allison wrote: On Sun, Apr 30, 2006 at 12:28:59PM +0200, Volker Lendecke wrote: On Sat, Apr 29, 2006 at 01:02:12PM -0700, Jeremy Allison wrote: If you need auditing on logon/logoff you can get this info from the logs, and we're in the process of adding an audit mechanism (hi Gunther :-) into smbd. Can we really audit logoff? Doh ! Yeah, the client never sends that... :-). True. Jeremy. What!? You guys aren't escaped MS programmers? There's no interminable exchange of networking messages concerning the logoff? I gotta go, now. You sure? Yeah, I'm sure. OK, buh-bye. Bye. You coming back? Maybe. OK. -- I don't give 'em hell. I just tell the truth on 'em, and they think it's hell. ---Harry Truman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Stable Network Down
jamrock wrote: EHines [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I eventually cleared the problem by rebooting the Samba server--everything is running properly, now. However, rebooting seems excessive. In future, what sorts of things typically go wrong to produce this type of failure? For what should I be looking? Thanks Eric Hines Did you apply an updates to the computer recently? I updated OOo to 2.0.2, but that has to be a coincidence. Eric Hines -- I don’t give ‘em hell. I just tell the truth on ‘em, and they think it’s hell. —Harry Truman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Fwd: Re: [Samba] can't connect to swat]
Sorry for the direct post Eric Hines Original Message Subject:Re: [Samba] can't connect to swat Date: Sun, 16 Apr 2006 08:51:45 -0500 From: EHines [EMAIL PROTECTED] To: Larry Weldon [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] Larry Weldon wrote: On Sun, 2006-04-16 at 21:27 +1000, Jeffrey wrote: ...I have enabled swat in inetd.conf. But I can't connect to http://x.x.x.x:901 from client PC using web browser. I can't speak directly to inetd as I use xinetd but if you can connect from the smb server using http://localhost:901 you should also try it from the server using the server's local IP. Most likely you don't have the inetd only_from option set or it just reads: only_from = 127.0.0.1 If your LAN is 10.64.64.0/24 you should make it: only_from = 127.0.0.1 10.64.64.0/24 or something like that. Larry I have my swat file set to only_from = localhost Then logging in with http://localhost:901 should work OK. Incidentally, the swat file in an xinetd setup is typically located in /etc/xinetd.d. I know very little about inetd environments, but there's a pretty good discussion of swat enabling in O'Reilly's _Using Samba_ (Ts, Eckstein, Collier-Brown), beginning on pg 52. This discussion includes the inetd environment. Eric Hines -- I don’t give ‘em hell. I just tell the truth on ‘em, and they think it’s hell. —Harry Truman -- I don’t give ‘em hell. I just tell the truth on ‘em, and they think it’s hell. —Harry Truman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Stable Network Down
Hi, I've had a stable Samba-run LAN, with some active shares, for several months, with my PC and laptop also gaining access to the Internet through the Samba server. However, this morning, when I booted up my Samba server, I had no LAN--neither my PC nor my laptop could connect to any share. However, both still had access to the Internet. I confirmed that smb, named, winbindd, et al., were running on the Samba server, and I could find nothing wrong, with a search limited by my limited knowledge. Associated with this problem (at least in time), I could not log in to SWAT: http://localhost:901 simply sat and churned for several minutes, until I canceled the attempt. I eventually cleared the problem by rebooting the Samba server--everything is running properly, now. However, rebooting seems excessive. In future, what sorts of things typically go wrong to produce this type of failure? For what should I be looking? Thanks Eric Hines -- I don’t give ‘em hell. I just tell the truth on ‘em, and they think it’s hell. —Harry Truman -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] net drive mapping not working in login script
I'm shotgunning here, since I'm not much more experienced than you, but
I think setting login script to netlogon/%U.bat makes Geraldine, for
instance, run the script geraldine.bat.bat. Try using netlogon/%U
(although I'm not sure this construction works).
Eric Hines
Chris Boyd wrote:
No they are in the /var/lib/samba/netlogon/ directory...see
ls -la /var/lib/samba/netlogon/
total 21
drwxr-xr-x 2 root root 200 Apr 7 14:20 .
drwxr-xr-x 6 root root 680 Apr 7 14:15 ..
-rwxr-xr-x 1 root root 179 Apr 7 12:10 aillin.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 geraldine.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 kay.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 reception.bat
-rwxr-xr-x 1 root root 181 Apr 7 12:09 robin.bat
I've tried chmod 755, changing the {netlogon} in smb.conf:
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
login scipt = netlogon/%U.bat
write list = root
admin users = root
guest ok = Yes
browseable = No
doesn't work for some reason.
Chris Boyd
Systems Engineer
USIT
19-21 Aston Quay
Dublin 2
Ireland
Tel: +353 1 6021670
Fax: +353 1 6771602
www.usit.ie
E [EMAIL PROTECTED] 04/07/06 2:00 PM
You haven't placed your scripts in the .../netlogon directory; you've
placed them, it seems from your ls listing, in your .../netlogon/scripts
directory. You need to correct your [netlogon] path.
Eric Hines
Chris Boyd wrote:
To answer craig. I've corrected the dos syntax in the login scripts but they don't seem to be running.
Here's the whole smb.conf
snip
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
write list = root
admin users = root
guest ok = Yes
browseable = No
ls -la /var/lib/samba/netlogon/
total 21
drwxr-xr-x 3 root root 224 Apr 7 12:13 .
drwxr-xr-x 6 root root 680 Apr 7 12:16 ..
-rwxr--r-- 1 root root 179 Apr 7 12:10 aillin.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 geraldine.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 kay.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 reception.bat
-rwxr--r-- 1 root root 181 Apr 7 12:09 robin.bat
drwxr-xr-x 2 root root 80 Apr 6 12:05 scripts
Chris Boyd
Systems Engineer
USIT
19-21 Aston Quay
Dublin 2
Ireland
Tel: +353 1 6021670
Fax: +353 1 6771602
www.usit.ie
snip
--
The mode in which the inevitable comes to pass is through effort.
--Justice Oliver Wendell Holmes, Jr
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] net drive mapping not working in login script
Not to put too fine a point on the matter (I'm out of ideas, now,
anyway), but did you notice Ed's suggestion of the lower case u: %u?
Samba distinguishes between %U and %u. His solution also blows my
thought about the extra .bat suffix out of the water.
Eric Hines
Chris Boyd wrote:
I dont know it seems no matter where I put the script or path it doesn't seem to run. I'm wondering if it's something on the XP side?
Any ideas?
Chris Boyd
Systems Engineer
USIT
19-21 Aston Quay
Dublin 2
Ireland
Tel: +353 1 6021670
Fax: +353 1 6771602
www.usit.ie
Ed Kasky [EMAIL PROTECTED] 04/07/06 2:56 PM
I have the following config that works well for me:
logon script = %u.bat
and under /shared/netlogon I have [user].bat for each user as we are
a small operation...
HTH
Ed
At 06:24 AM Friday, 4/7/2006, EHines wrote -=
I'm shotgunning here, since I'm not much more experienced than you,
but I think setting login script to netlogon/%U.bat makes Geraldine,
for instance, run the script geraldine.bat.bat. Try using
netlogon/%U (although I'm not sure this construction works).
Eric Hines
Chris Boyd wrote:
No they are in the /var/lib/samba/netlogon/ directory...see
ls -la /var/lib/samba/netlogon/
total 21
drwxr-xr-x 2 root root 200 Apr 7 14:20 .
drwxr-xr-x 6 root root 680 Apr 7 14:15 ..
-rwxr-xr-x 1 root root 179 Apr 7 12:10 aillin.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 geraldine.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 kay.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 reception.bat
-rwxr-xr-x 1 root root 181 Apr 7 12:09 robin.bat
I've tried chmod 755, changing the {netlogon} in smb.conf:
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
login scipt = netlogon/%U.bat
write list = root
admin users = root
guest ok = Yes
browseable = No
doesn't work for some reason.
Chris Boyd
Systems Engineer
USIT 19-21 Aston Quay
Dublin 2
Ireland
Tel: +353 1 6021670
Fax: +353 1 6771602
www.usit.ie
E [EMAIL PROTECTED] 04/07/06 2:00 PM
You haven't placed your scripts in the .../netlogon directory;
you've placed them, it seems from your ls listing, in your
.../netlogon/scripts directory. You need to correct your [netlogon] path.
Eric Hines
Chris Boyd wrote:
To answer craig. I've corrected the dos syntax in the login
scripts but they don't seem to be running.
Here's the whole smb.conf
snip
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
write list = root
admin users = root
guest ok = Yes
browseable = No
ls -la /var/lib/samba/netlogon/
total 21
drwxr-xr-x 3 root root 224 Apr 7 12:13 .
drwxr-xr-x 6 root root 680 Apr 7 12:16 ..
-rwxr--r-- 1 root root 179 Apr 7 12:10 aillin.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 geraldine.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 kay.bat
-rwxr--r-- 1 root root 179 Apr 7 12:10 reception.bat
-rwxr--r-- 1 root root 181 Apr 7 12:09 robin.bat
drwxr-xr-x 2 root root 80 Apr 6 12:05 scripts
Chris Boyd
Systems Engineer
USIT 19-21 Aston Quay
Dublin 2
Ireland
Tel: +353 1 6021670
Fax: +353 1 6771602
www.usit.ie
snip
--
The mode in which the inevitable comes to pass is through effort.
--Justice Oliver Wendell Holmes, Jr
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
. . . . . . . . . . . . . . . . . .
Randomly Generated Quote (758 of 1045):
Often things ARE as bad as they seem!
-
This email message is intended only for the addressee(s)
and contains information that may be confidential and/or
copyrighted. If you are not the intended recipient please
notify the sender by reply email and immediately delete
this email. Use, disclosure or reproduction of this email
by anyone other than the intended recipient(s) is strictly
prohibited. USIT has scanned this email for viruses and
dangerous content and believes it to be clean. However,
virus scanning is ultimately the responsibility of the recipient.
-
--
The mode in which the inevitable comes to pass is through effort.
--Justice Oliver Wendell Holmes, Jr
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
