similar to: Win95/Samba problem: Can't log on first time, second time OK

Hi! We are running a Win95/Samba network at our school. The server is a Digital Venturis 575e running RedHat Linux 5.0 and Samba 1.9.18p7. The clients are Win95 machines. I have turned on user quotas for some users. On the Linux side, this works fine, but the Win95 client still thinks that it can use all available space on the server HD. That causes strange error messages for instance in Outlook

Hi, We try configure Netlogon/Profiles in Samba 1.9.18p7 to use in Win95, but the "login script" did not run in win95 login process. The net configuration is: Clients Win95 using Novell 4.2 and Microsoft in same time; Servers UNIX using Solaris 2.5.1 Server. The SMB.CONF is: ##START-OF-SMB.CONF # [global] workgroup = Samba-TEST local master = yes domain logons = yes

Hi Peter, i had a long, frunstrating web surfing yesterday night, searching for something that could apply to your case. I didn't find much at all, sorry. The only thing perhaps interesting to you could be this: http://us2.samba.org/samba/ftp/docs/htmldocs/printer_driver2.html This doc contains a section about migrating from 2.0.x to 2.2.x I think the problem lyes in the new way samba

Hi, I've been using Samba for a while in lots of places and this is the first time I've encountered this problem: I'm using 1.9.18p7 on solaris-2.6, there's a large PC network here with win95 and winNT machines all belonging to a different workgroup then the samba machine. There are no problems with the winNT clients. However, the win95 machines sometimes give the following

Did you change your "security" setting in your new Samba e.g. from "share" to "domain"? -----Original Message----- From: peter.a.bryant@mainroads.qld.gov.au [mailto:peter.a.bryant@mainroads.qld.gov.au] Sent: Friday, 14 March, 2003 7:00 AM To: samba@lists.samba.org Cc: John H Terpstra Subject: Re: [Samba] Win95 & Win98 - NOT WORKING - NT,2000, XP are ok (reposted)

Hi, I want to set up samba and win95 so that password checking is made via samba and also some login scripts are started. I have changed windows setup to login on NT-Domain with my samba's hostname as DOMAIN. I also have enabled wins support on win95. But after reboot, when I am asked for user,password and domain I always get an error message, directly after pressing the

Thanks for the suggestion Andrew, I was hopeful, but removing the writeable made no difference. Still prints from NT, 2000, XP but not from Win95, 98. Any other ideas? -peter. Andrew Bartlett <abartlet@samba.org> on 19/03/2003 07:05:29 PM On Wed, 2003-03-19 at 18:02, peter.a.bryant@mainroads.qld.gov.au wrote: > > > Please lend me some expertise... Sure! See below: >

Hi... I've gone through the DIAGNOSIS.txt document, and just about everything else I can think of, and am lost... I've installed Samba on one of my Sparc's here at the office, and am trying to connect to it from a Win95 machine, and it fails. If I try to use smbclient from a different Unix host, it connects fine. If we look at a Win/NT machine, the Sparc server comes up on the

Hello, could anyone give me a working configuration (only the 3 or 4 lines required for the desired settings) for our Win95 / WinNT4.0-Clients. Our samba server: 1.9.18p7 Our customers would drag and drop a file within the browsers from a local drive (for example C:) to a SAMBA-connetced network drive *WITHOUT* changing anything within the file name (length, case etc.). I would be glad to get

I can't create new folder in a czech Win95 explorer on a unix using samba 1.9.18p7. The problem is that Windows exporer uses for the creation new folder a name containing characters above 128. The explorer creates new folder in a two phases: the first It creates directory named Nov<A0> slo<A7>zka and next it gives to user posibility to change this name. Crazy !!? The first phase

Please lend me some expertise... Ok, I know suggesting a bug is a bit impolite, but I cannot find a solution for this and none of the helpful people who have responded have been able to help either... If I come off sounding a bit short it's just because I've tried many things to get these older clients printing. :-) Don't mean to annoy anyone. Appreciate any help! Have several

Hmmm... I've sent a couple of questions to the list recently, with no responses. Are my messages getting out? Since upgrading to 2.0.2, our Win95 boxes are having problems accessing shares. WinNT works perfectly. Win95 worked fine with 1.whatever, but now it can only see files that are actually in the share directory. It can see subdirectories of the share, but they appear as empty

Hi folks - I am having printing problems with our older machines. Printing is working okay for our Windows NT, 2000 and XP clients. However, with windows 95 & 98, the print job gets put into the Samba spool directory (path = /var/spool/lp/tmp/samba) but doesn't make it to the printer. The print files stay there in the directory - don't get removed. Samba version is 2.2.7a, on

Hi, This problem is driving me crazy.. I've read piles of FMs, but am stuck... is it the variable "domain logons = yes" which is causing me trouble? is it something else?? thx b --- [root@server samba]# more smb.conf [global] smb passwd file = /etc/samba/smbpasswd add user script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Accou nt' -s

I've run into a problem and would like to know if anyone else has experienced it. I'm trying to install and run an old 16 Bit Win$ Application on our LAN. - Install and run on Win95 works ok. - Install on a Novell 3.12 Server and run on a Win95 client works ok. - Install on a Samba 2.0.0 / SUSE 5.3 Server and run on the Win95 client gets me strange results. (Can be reproduced) Win95

Thanks to the four people who replied to my original posting (appended below, subject "Win95 problem"). I've made progress but have now hit a new problem. The solution to the original problem (How do you make a "standalone" client "log on to the network"?) was simply to tick the "Server Type/Log on to network" checkbox in the dialup properties.

I have 1.9.18p4 running on Linux 2.0.30 set to encrypt passwords and in user level security. All of the users registry; profile/s and personal data is stored in their [home] resource, all other shares to which the users have access are read-only and guest-access allowed. My Win95 boxes are set set to log into an NT domain with share level security and the primary login is to the Microsoft

Hello everybody, althought there are a lot of discussions on Samba's performance, I would like to share my results trying to connect Samba running on a Linux box to a Win95 workstation on a fast ethernet network. If any of you could have some ideas or suggestions , please mail me (cc: teo@flex.ro) because I am not (yet) on this mail list. First of all, may I present you : 1. THE SERVER -

Hello : One Win95 client, connected over a SLIP connection to an SCO Openserver 5.0 has been working fine until System Administrator has updated OS Version to Unixware 7.1.0. On this server (Unixware 7.1.0) , I've installed Samba 2.0.2 to access all Win9x shares. All shares on the LAN (connected via TP 10Mb cards) work fine, but when I print any job to Win95 client connected via SLIP

Hi-- Last night I shut down my network for the thunderstorms going through the area, and unplugged it all. When I booted up this morning, I had no Win95 connection to my samba server. My setup: Ubuntu 6.06 server, running samba 3.0.22. 3 Ubuntu workstations, 1 WinXP Pro, 2 Win95 boxes. The Ubuntu boxes mount the same directories as the Win boxes, using cifs. What I have tried: checking log