similar to: printcap entries over 8 chars long

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

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

My Win95 clients are having intermittent problems running the logon script. I am running Samba 1.9.17alpha5 on DEC Unix 3.2G. In the client's log file (under logs/), I receive this message: Share violation on file (1,1,0,9375,kix/logon.bat) = 0 Now, I've tried the various options reaging locking, but the problems still persist. Relevant options from smb.conf: [global] logon

(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

>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

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'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

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

Rob, I hope you have referred to the example smb.conf file. We really cut our teeth on some of the example config settings. It is IMPERATIVE that nothing in the NETLOGON share should become locked - this breaks the logon process very badly! Some Win95 clients will always hang on logon if any files end up being locked in the netlogon share. For the record, here is an extract from

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a medium sized business that is interested in implementing * as their PBX system. They currently have a Panasonic system with Panasonic handsets that they are going to replace Asterisk with, as the current system is maxed out, and they don't even have voicemail capabilities. I have been considering using an Adtran Atlas 550 with FXO and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 OK, so I have a local extension that a phone can call to take it to voicemail. I don't want it to exit out to a fast busy tone, as I would rather it allow the user to simply continue on and call a new number (without having to physically release the line first). The [intern] context is where everything goes by default (sip.conf for example has

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I am using a TDM40B, and have managed to compile mpg123 and turned on MOH. Problem I am having is that it is choppy, staticy, and sounds like white noise pretty much. I have search the archives to see if this problem had been resolved, but I haven't found anything yet. Has anyone had this problem and resolved it? I am calling from

Does nayone have a collection of performance tips for heavily loaded samba servers? I have a server that routinely has 45-90 connections and just runs really poorly. We've thrown more memory at it w/ some benefit, but not significant. This is on a linux 2.0.35 based machine. Does anyone have any suggestions? -- Nathan ------------------------------------------------------------ Nathan