Hello,
I'm afraid this message is going to be a little long (188 lines,
not counting the headers). It is comprised, in fact, of two posts I
sent to the comp.protocols.smb newsgroup, from which I've not received
any replies. I'm hoping I can have better luck with the mailing list,
(to which I've just subscribed, so it's probably most appropriate
to send replies there...)
Please see appended below my signature (there are TWO messages there).
I hope someone can help...
--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca
Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------
From: Sylvain Robitaille (syl@alcor.concordia.ca)
Subject: Samba-3.0-alpha9 compilation problems
Newsgroups: comp.protocols.smb
Date: 2002-01-28 12:31:58 PST
Hello,
I'm trying to experiment with Samba-3.0, ultimately to have it work
within a heterogeneous Unix/Windows environment.
I've started working on a DEC/Compaq Unix (4.0g) system, using the
stock C compiler, but also have access to a Linux (2.2.18) system,
with Gcc-2.7.2.3 on which I can work. Ultimately, I'd like to have
Samba running on the DEC system, though.
I've been atempting to configure with Kerberos, SSL, Syslog, Quotas, and
Utmp (hrmmm... perhaps if I trim down the configuration, to see which
of these cause problems... more on that later), and so far on both
systems I'm having different problems getting a successful compilation.
On the DEC system, so far, I seem to be having problems with the OpenSSL
include files (these have been used successfully to compile Apache, so
the OpenSSL installation itself works correctly, though it may be too
old for Samba).
On the Linux system, even with a simple configuration, (no options), the
compilation fails at this point:
make distclean
./configure
make
...
Compiling lib/util_file.c
lib/util_file.c: In function `map_file':
lib/util_file.c:442: `MAP_FAILED' undeclared (first use this function)
lib/util_file.c:442: (Each undeclared identifier is reported only once
lib/util_file.c:442: for each function it appears in.)
(Hrmmm... I just noticed now that the make warns:
WARNING: you need to rerun autoconf
That's a bit of a concern; I haven't _installed_ autoconf on this
system... That may indeed be my problem on that system. I can only
guess that there must be an include file missing somewhere.)
Alright, If I strip out the SSL options from the configuration (and
still have krb5, syslog, quotas, and utmp) on the DEC system, I get a
successful compilation. Can someone please confirm if there is a
version dependancy for OpenSSL? (If this is documented somewhere I
should have looked, please be gentle in application of the LART!)
Out of curiosity, I've copied the source tree to my home system
(Linux-2.4.17 with gcc version 2.95.3 on a much slower system than those
I have at work), and started a test compilation. Though it's taking a
while to complete, so far it does seem to be compiling cleanly, without so
much as any warnings (except for the one about needing to rerun autoconf
on this system as well). I'll try it again with as many of the options
as I have support software installed on that system for (no Kerberos,
I'm fairly certain the OpenSSL I have there was used successfully to
compile Lynx some time ago, but it's an older version even than I have
on the systems at work...)
That compilation did indeed complete without any problems. There seems
to be some fundamental difference between compiling Samba-3.0 on
Linux-2.2.x and Linux-2.4.x. Is this a known state? Have I overlooked
some crucial documentation? Will I successfully complete my
installation on Samba on DEC Unix? Stay tuned for the continuing
story...
--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca
Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------
From: Sylvain Robitaille (syl@alcor.concordia.ca)
Subject: Re: Samba-3.0-alpha9 compilation problems
Newsgroups: comp.protocols.smb
Date: 2002-02-04 10:20:23 PST
On 28 Jan 2002 20:31:57 GMT, I wrote:
> I've started working on a DEC/Compaq Unix (4.0g) system, using the
> stock C compiler, but also have access to a Linux (2.2.18) system,
> with Gcc-2.7.2.3 on which I can work. Ultimately, I'd like to have
> Samba running on the DEC system, though.
Progress report:
As I mentioned in my previous post, compilation completed if I didn't
include OpenSSL support. That's probably fine for the time being,
though I imagine I'll want the possibility for encryption in production
use.
Now I can connect locally via smbclient, but I'm not getting it to
authenticate correctly. With no authentication, I can get it to list
the "shares" (my apologies for long lines):
: hermes[syl] ~; smbclient -L localhost
incorrect size for /local/pkg/samba/root-samba-3.0.alpha9/lib/upcase.dat - got
0 expected 131072
incorrect size for /local/pkg/samba/root-samba-3.0.alpha9/lib/lowcase.dat -
got 0 expected 131072
incorrect size for /local/pkg/samba/root-samba-3.0.alpha9/lib/valid.dat - got
0 expected 65536
creating lame upcase table
creating lame lowcase table
creating lame valid table
added interface ip=192.168.7.57 bcast=192.168.7.255 nmask=255.255.255.0
error connecting to 127.0.0.1:445 (Connection refused)
Password:
Doing spnego session setup (blob length=78)
Anonymous login successful
Domain=[IITS-SSG] OS=[Unix] Server=[Samba]
Sharename Type Comment
--------- ---- -------
public Disk Public Stuff
IPC$ IPC IPC Service (hermes (Samba-pre-3.0.0))
ADMIN$ IPC IPC Service (hermes (Samba-pre-3.0.0))
printer qms3 Printer
printer qms2b Printer
printer qms2 Printer
printer qms i Printer
printer hp405 Printer
printer ssg i Printer
Server Comment
--------- -------
HERMES hermes (Samba-pre-3.0.0)
Workgroup Master
--------- -------
IITS-SSG
I've also configured home directories to show up upon authentication:
[homes]
comment = Home Directories
browseable = no
valid users = %S
writable = yes
The problem is that I can't seem to get authentication to work, either
with or without Kerberos (my "with Kerberos" configuration includes
the
following in the global section of smb.conf):
realm = MYREALM.CA
ads server = hermes.mydomain.ca
security = ADS
encrypt passwords = yes
Can anyone shed some light on what I might be doing wrong?
Does anyone know what Smbclient is trying to connect to at port 445?
error connecting to 127.0.0.1:445 (Connection refused)
--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca
Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------
