samba - Jan 2002 - Connecting to SCO Openserver with Windows 2000 Clients via samba

Hi all,
 
I hope someone out there can help me.
 
I have a network with SCO Openserver running samba to share files for
access by windows clients. We are currently using windows 95 clients
without any problems.
We want to upgrade to Windows 2000 and XP. We have setup a test machine
and attempted to connect to the Samba shares. We had problems connecting
so we changed the registry setting on the Windows 2000 workstation not
to use encrypted passwords. This allowed us to successfully map to the
Samba shares.
 
The problem I have is that everytime the Windows 2000 workstation is
restarted the mapped drive to the samba share prompts for a password. 
 
What I will ideally like is to have the drives mapped once and not have
to keep specifying the passwords again. I have used the save password
feature when mapping the drive.
 
I have thought of adding encrypt passwords = yes to the smb.conf file,
but do not fully understand the implications of this to the Windows 95
clients which are working at the moment.
 
Any suggestions will help.
 
Thanks in advance,
 
Pere

On Tue, 22 Jan 2002, Pere Raphael wrote:
> Hi all,
>
> I hope someone out there can help me.
>
> I have a network with SCO Openserver running samba to share files for
> access by windows clients. We are currently using windows 95 clients
> without any problems.
> We want to upgrade to Windows 2000 and XP. We have setup a test machine
> and attempted to connect to the Samba shares. We had problems connecting
> so we changed the registry setting on the Windows 2000 workstation not
> to use encrypted passwords. This allowed us to successfully map to the
> Samba shares.
>
> The problem I have is that everytime the Windows 2000 workstation is
> restarted the mapped drive to the samba share prompts for a password.
>
> What I will ideally like is to have the drives mapped once and not have
> to keep specifying the passwords again. I have used the save password
> feature when mapping the drive.
>
> I have thought of adding encrypt passwords = yes to the smb.conf file,
> but do not fully understand the implications of this to the Windows 95
> clients which are working at the moment.
>
> Any suggestions will help.
>
> Thanks in advance,
>
> Pere
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>
I had a very similar setup once. Windows 95 & 98 WS's with Samba on SCO.
I decided to upgrade one of the 98 boxes to 2000 Professional and didn't
have one problem. Worked beautiful. I also think I did have the encrypt
passwords=yes on the samba server. Im not sure what release the Windows 95
machines were running but it they also worked with the samba server.


Im not sure why the Windows 2000 box prompts for a password. Maybe since
it not encrypted, it wont save it for security sake !?!

It can't hurt to add encrypte passwords=yes in smb.conf. Just make you
back it up first.

After doing that, test the Windows 95 machines. Also make sure they have
the latest service packs.




Good luck.

Thank you,
Steve Maroney


Ps. How can you work with SCO ?  When I worked with it, I always spend
hours trying to find the most popular software that has been ported to
SCO. All because half the software I tried to compile from source, DIDN'T!
(Im not a C/C++ guru so I didn't know the errors were.

The TCP/IP stack is crap !

Better yet, it isn't being developed yet, I think. Since SCO was bought
out by Ransom Love, CEO of  Caldera Linux.

Steve,

I refer to your posting to the samba mailing list. Hope you don't mind my
direct reply.
> I had a very similar setup once. Windows 95 & 98 WS's with Samba on
> SCO. I decided to upgrade one of the 98 boxes to 2000 Professional and
> didn't have one problem. Worked beautiful. I also think I did have the
> encrypt passwords=yes on the samba server. Im not sure what release
> the Windows 95 machines were running but it they also worked with the
> samba server.
Samba works fine on SCO OpenServer - I'll vouch for that. In fact, it is
being integrated into the next OpenServer update due out soon.
>
> Im not sure why the Windows 2000 box prompts for a password. Maybe since
> it not encrypted, it wont save it for security sake !?!
>
> It can't hurt to add encrypte passwords=yes in smb.conf. Just make you
> back it up first.
That is "encrypt passwords = Yes", also make sure that if your MS
Windows
2000 login name is not exactly as is the Unix one you will need a map
file. Add "username map = /usr/local/samba/private/smbusers", the
format
for the file is:

	root = Administrator admin
	jimb = "James Brown" jamesb george

The above means that admin and Administrator will be root on Unix, and
"James Brown", jamesb, and george will be jimb on Unix.
> After doing that, test the Windows 95 machines. Also make sure they have
> the latest service packs.
> 
> Ps. How can you work with SCO ?  When I worked with it, I always spend
> hours trying to find the most popular software that has been ported to
> SCO. All because half the software I tried to compile from source,
> DIDN'T! (Im not a C/C++ guru so I didn't know the errors were.
I hope we have addressed this concern in the next OpenServer release. You
will find the GNU toolset on the SOSS CD. That is what many users refer to
as the Skunkware CD.
> The TCP/IP stack is crap !
Ouch! It has been around for a long time and is VERY stable. OpenServer is
being maintained, and so is the IP stack. We are doing a lot more than
just maintenance on this product and I am sure that the next update will
prove that. Do not expect any radical change in this IP stack though.
> Better yet, it isn't being developed yet, I think. Since SCO was bought
> out by Ransom Love, CEO of  Caldera Linux.
I would like to know the source of this idea. Caldera has a committment to
continued updates well into the foreseeable future (2-3 years). The long
term strategy is to recommend Open UNIX (was UnixWare) for high-end
back-end servers today, use OpenLinux Server elsewhere. The future is
going to be IA64 Linux.

Meanwhile, we have a commitment to over 1,000,000 installations to provide
ongoing support and to keep OpenServer alive while also providing a
migration path.

Open UNIX has OpenServer and OpenLinux application support. We are working
on OpenServer support on OpenLinux. Thus our users have a migration path.

All Caldera OS product will come with Samba as part of the core OS.
OpenLinux has always shipped with Samba. It will be added to the next
release of Open UNIX also.

If there is any way I can help please do not hesitate to contact me,
either at Caldera or at Samba.Org.

PS: The OpenServer samba package that is on the Samba FTP site was
produced by Ron Record who handles the Skunkware CD. It is an official
Caldera package that installs into the /usr/local/samba directory tree. If
you have a problem with it let me know. With the formal integration of
Samba into OSR5 these paths will change. You will also see some neat
features at install time that should help a lot of administrators to get
Samba working well.

PPS: I hope to see samba-2.2.3 out soon. As soon as that happens I will
post the official samba package for OSR5 to the samba FTP site. It will be
the integrated package designed for our next OS update.

Kind regards,
John T.
---
| John H Terpstra, Evangelist 
| Cell: +1 801 368 4066, Office: (650) 553 9371 
| E-mail: jht@caldera.com, jht@samba.org