davidl@cn.ca wrote:
> A "service" on an NT 4 server cannot connect to a samba
> share on my linux machine. The specific versions are given
> below. From the NT machine I have no problem as the administrator
> to login to samba server and view the target share. The
> supplier's service however cannot seem to do the same. The
> service does have a config for a user/password but as it gives
> no verbose error message I am stuck. Also the supplier(Bentley)
> is about as useful as the IRS - in their opinion I should be
> using NT and that's the end of the story. I disagree :)
> The service starts automatically at boot time but even if I
> stop and then restart it after I have logged into the share
> I have no luck.
>
> Does anyone have any ideas ? From what I have gleamed from the
> John Blair book I have setup share level authentication. I have
> also applied the patch to NT to use plaintext passwords.
Don't use share level auth. Use user auth with encrypted
passwords and add a username/password logon to the Linux
box that matches the username/password of the service.
This does work with Samba and has for about 4 years or
so (as I did the original work to fix this when I was
making the Vantive service on NT use a Samba drive so
I could get at the log files I needed :-). It's just
a matter of configuring it correctly. Use the Samba logs
if the Bently logs are no use.
Once you have this working I'd recommend you send a
tech note to Bently explaining how to do this. Many
app vendors don't support Samba due to ignorance. If
they saw it increased the compatibility (and hence
demand :-) of their products they might get more
accommodating.
AutoDesk has been very good about doing this, and AutoCAD
now works well against a Samba server.
Regards,
Jeremy Allison,
Samba TEam.
--
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------
