similar to: Problem executing logon script - PLEASE HELP!

Ok, I'm a dumb-ass today. I failed to see the "available = no" in the service entry. Sorry for wasting your time. Rob Naccarato "Civilized men are more discourteous than savages Sys Admin because they know they can be impolite without Sheridan College having their skulls split, as a general thing." Oakville, Ont. Canada

I've found these errors in my log.smbd file: Invalid snum 17 for admin 1998/12/03 10:35:48 xxxxxx (xx.xx.xx.xx) couldn't find service admin This occurs when attempting to connect to a share from a Win95 system. This is the share definition from smb.conf: [admin] available = no browsable = no path=/usr/SHERNET.32/groups/admin read only = yes write

>Date: Tue, 8 Dec 1998 11:00:42 -0500 (EST) >From: Rob Naccarato <rob@sheridanc.on.ca> >To: samba@samba.org >Subject: Can't connect to shares w/2.0beta3 on OSF1 > > >I was running 1.9.18p10 on a test DEC Unix 4.0d box here and I decided to >give 2.0beta3 a try. For some reason, I cannot connect to any of the >server's >shares or even get a list of

Peter> My problem is browsing printers that names are more than Peter> 8 chars long. Any printer that is longer than 8 chars (in the Peter> printcap file) does not show up when browsing. Peter> Anybody else affected by this? Is there a fix? Jim> I had considered "fixing" the code but then I wondered whether I would run Jim> into DOS's 8.3 filenaming convention

Hello all, We seems to have a bit of a problem with Windows 95 machines logging on to our network. I hope someone can shed some light on this. Current configuration: 2 servers. Once handles authentication and application serving while the other provides home directory services only. We have about 150 Windows 95 clients. The two servers are DEC Alpha 2100A and DEC Alpha 2000. Both are

(Samba version 1.9.18p4) I want to set up my environment thusly: - 2 workgroups, each composed of multiple subnets. - Each workgroup has a DMB and a WINS server (Samba only - no NT) - The two workgroups should collate browse lists so that clients on either workgroup can browse and connect to hosts on the opposite workgroup. I've read the documentation in BROWSING.txt and it does not appear

I've been seeing these in my logs files ever since I upgraded to 1.9.18p10 and turned on oplock support for users' home directories: --snip -- 1998/10/07 10:05:44 oplock_break: receive_smb timed out after 30 seconds. 1998/10/07 10:05:44 oplock_break failed for file Start Menu/Open Office Document.lnk (fnum = 14, dev = 808446, inode = 45cb8). 1998/10/07 10:05:44 oplock_break: client

I have a server here with 4 network interfaces (DEC Unix). All the Win95 clients are on the same 4 subnets as these 4 interfaces. One thing I noticed the other day is that the majority of the clients do not connect to the server's interface on the same subnet as the client. This is making unecessary use of our router. I'm wondering how I can force the clients to connect to the local

We have a requirement here to set up what we call a "shared area". This is nothing more than a directory on a Unix server (Digital Unix) that allows a group of users read and write access to the directory. The shared area needs to be accessible from Win95 clients. A big restriction that we want is: - when a user opens a file, others should not be able to write to that file. So, the

Just wondering when the next release of Samba is coming out with support formultiple WINS servers. If there are patches available to 1.9.18p8 that enable this support now, I'll take it. Rob Naccarato "In a perfect world, everyone would use Sys Admin Linux and drive a Saturn" Sheridan College Oakville, Ont. Canada

We've noticed this behaviour when Win95 crashes and the next person tries to logon (we are using roving profiles, samba 1.9.18p10): - user logs in to win95 - user crashes client - boot client - user tries to logon, but it takes *forever* and eventually returns a "the domain password you suppiled is not correct, or access to your logon server has been denied" error - user tries

I'm still having some problems with 1.9.18p10 on a DEC Unix 4.0e machine (this machine was upgraded from 4.0d last week). The smbds can take up to 20% of the cpu at various times. Anyways, I've been through all this before with the mailing list and a number of people who have attempted to help me out. Thanks to all of you. But, I have some more info which may or may not be useful.

Over the last summer we took our home dir / applications servers for the 330 Win95 PCs that they service and attempted to replace them with a single AlphaServer 8200 (Digital Unix (OSF/1), Samba, 4GB RAM, 2x525Mhz cpus). The results were *not* good. In fact, it was terrible. We have since gone back to using the original 3 machines. My suspision is that the clients are making way too many

I was running 1.9.18p10 on a test DEC Unix 4.0d box here and I decided to give 2.0beta3 a try. For some reason, I cannot connect to any of the server's shares or even get a list of it's services (via Start->Run->\\server) from Win95 clients. It asks for a password and no matter what I put in there I get "The password is not correct. Try again." I configured Beta3 a la:

G'day, When I connect to extension 600 to do an echo test, I can see my microphone sending, but the echo is simply digital garbage. I know it's not my Messenger client or anything like that, as I use it regularily with Messenger. I am using a linux box with RH9 and using a soundcard. I have a pretty stock install, so if someone know where to look for either alsa settings or anything I

Hi , We ran the classicupgrade today and have come across an issue with sysvol. The users are getting access denied message when accessing sysvol/netlogn. Other shares are ok. The administrator can access the sysvol and netlogin root at dozer5-ad:/var/lib/samba# ls -al total 67 drwxr-xr-x 6 root root 11 May 10 17:33 . drwxr-xr-x 32 root root 32 May

Hi Well we are now using HP instead of Dell and have hit a major hurdle. We dont seem to be able to kix any of these boxes. I have been most recently trying on a dl585 and the issue appears to be that the kix kernel does not detect any nic. Its strange as the box can be installed using iso's and the nic appears as eth0: Broadcom NetXtreme II BCM5706 1000Base-T (A2) PCI-X 64-bit 100MHz

Hi all, We have Samba 3 up to and including 3.0.9 working fine using LDAP for the backend. XP and 9X logons work fine. On upgrading to newer versions (inc. 3.0.11, 3.0.14a and tried 3.0.20), in the same configuration, 9X logons stop working properly - they authenticate, but fail to get information such as groups and user's full name. XP still works fine. We use KIX for our logon

Hi, What's does a group like 'CPB\unix_group.2147483404' mean? I get al sorts of group when I run the following kix-script that are recognizable and some that are not. Why? running samba-2.2.3a with domainname CPB. ================ groups.kix ====================== $index = 0 DO $group = ENUMGROUP($index) ? $group $index = $index + 1 UNTIL Len($group) = 0

Hi all, In trying to upgrade Samba here, I have built various versions from 3.0.11 to 3.0.14a using various versions of gcc and the Sun compiler (this is on Solaris SPARC) and had the following problem in all cases. Running the built samba as a logon server, I find that WinXP clients work fine but Win9X clients have some difficulties. The problem is that the Win9X logon script can't