similar to: Help - Adding winXP pro clients to win95 and Samba 2.2.x setup

hello, Need advise I've been attempting to get a winXP system added into the network of win95/98 systems and a Samba 2.2.7 server (redhat 7.3) current version of Samba version 2.2.7a-security-rollup-fix the win95/98 systems work fine. the winXP has trouble .. 1) It can not see the samba server OR other systems in the network neighborhoods. (it CAN ping the IPs tho .. ) I've read

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

Hi again folks... Just when I thought I had everything working great with samba mounts on an AIX 4.3 machine (after a lot of testing with a Win95 box), I went to do something quickly on a NT 4.0 workstation. I had some intallation programs in the shared directory that I had used to install programs on the Win95. No problem. I ran over to my boss' NT 4.0 workstation, opened the shared

Hello! Ive just got the lovely job of converting and old Windows NT 4 fileserver to FreeBSD, ive set up samba before as a simple fileshare but this place requires roaming profile login from WinXP, Win98 and Win95 clients. My question is whether or not any of you people have any experience with this and might be able to give some tips on the way? I've tried fidling with it but i cant get

Hello. I've just compiled Samba-3.0.0 on Tru-64 5.1b (AKA Digital Unix, AKA OSF) with base security (no shadow passwords) using the native compiler and GNU make. In smb.conf I'm forcing NTLMv2 only: security = user encrypt passwords = yes lanman auth = No ntlm auth = No client NTLMv2 auth = Yes client lanman auth = No

Hi, I've found a problem with samba when printing from a client running win95 + DFS. The print fails with a segmentation fault. The problem is that Win95 does not return the proper file_fsp( smb_vwv0) when doing an IOCTL request.This causes the file_fsp call in reply_ioctl (smbd/reply.c) to fail cause a segmentation fault. I do not understand how samba work, but here is my working patch

----- Original Message ----- From: samba <samba@druid.beeline.msk.ru> To: Multiple recipients of list SAMBA-NTDOM <samba-ntdom@samba.org> Sent: Monday, 20 September, 1999 16:22 Subject: Password change from Win95 clients > Hello! > I'm using samba-2.0.5a on RedHat-6.0 in school network. There are so many > curious kids :) The network is dedicated for teachers only but

Here is other question which I have hard time trying to set up which I am not very successful with dispite reading the documentations and trying to configure it. Here is the setup which we have for our network. We have 3 Win95 Boxes which one has 2 printers attached to it which is basically the printer server. I would like to use that printer services from Linux. Two of the

I have become quite confused about the interaction of the kernel versions and the different versions of Samba and smbmount. I have just upgraded to a 2.2 kernel. 'make menuconfig' gave no choice by which to enable the Win95 bug workaround. At the same time, smbmount 2.0.5a, which seems to be the proper one for a 2.2 kernel (it's the latest provided by Debian, under the name

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.

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

Hi there, I've just tripped over a problem I thought only existed in WfWg3.11. On Win95 clients connecting to a 1.9.18p8 Samba server (IRIX 5.3) the first logon dialog box seems to have a problem with mixed-case passwords. If I have a lower case password, then I can just enter it in the Win95 'Microsoft Network' logon dialog at startup, and all the shares are reconnected. If I

Hi, I'm having some problems with Samba 1.9.16p11 on a Sun3/60 running NetBSD 1.2. I have a Win95 client and a couple of DOS clients on a single ethernet segment (it's at home :-). I've set up a simple configuration, intention was just to serve files from the Sun to the PC's. Everything works perfectly except authentication from the Win95 client. I can connect to the Samba shares

I'm running into a problem with Win95 clients and I hope someone has a fix for this. Our servers are Solaris boxes providing file services via both NFS and samba (1.9.16p11). The Win95 clients were recently upgraded to the latest version of FTP Software OnNet which makes the NFS stuff almost transparent to the users. I'm not sure how OnNet hooks in to Win95 but you could map a drive to

It probably has something to do with the fact Win 95 doesn't support encrypted passwords... Brett -----Original Message----- From: Cristian Mijea [mailto:cmijea@protvcluj.ro] Sent: Wednesday, May 22, 2002 3:44 AM To: samba@lists.samba.org Subject: [Samba] !!! HELP !!! samba and win95 I'm running a smb server on a redhat 7.2 system. everything works just fine except when I try to

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