similar to: Connecting to [homes] ... yes, another password question

Displaying 20 results from an estimated 5000 matches similar to: "Connecting to [homes] ... yes, another password question"

1999 Aug 25
4
Client on dos
I need to use a samba server (linux redhat 6.0 ) from a diskless dos machine ( has a floppy drive for booting) . So i need a very little tcp-ip stack for dos and a client for a NT server on dos so that they will be small enough to be on a 1.44 system floppy. Is that possible ? Paul
2003 Nov 14
4
Setting up Samba
Hi to you all, I'm setting up a network to where I have Linux and W2k Active Directory.I have Redhat 8.0 and i want it to see and access file between the two OS'S. I downloaded the latest samba binaries 3.0.2 and edit the smb.conf.How do i know if my linux will act as a samba server? Should i select "everything" when i load redhat again or should i just continue what i have
1999 Oct 26
2
Getting RH6.0/Samba2.0.5a to join NT domain
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, With SMB and NMB services stopped, I issue: smbpasswd -j DOMAIN -r PDC with these results: cli_net_auth2: Error NT_STATUS_NO_TRUST_SAM_ACCOUNT cli_nt_setup_creds: auth2 challenge failed modify_trust_password: unable to setup the PDC credentials to machine PDC. Error was: NT_STATUS_NO_TRUST_SAM_ACCOUNT. 1999/10/25 <timestamp>:
1999 Aug 23
1
NT4SP5 Encryption and mksmbpasswd
Hi all, Reading through ENCRYPTION.txt it says to do the following: cat /etc/passwd | mksmbpasswd.sh >/usr/local/samba/private/smbpasswd However, on my Samba-2.05a install (onto RH 6.0), /usr/local/samba doesn't exist. Instead, all the files listed in ENCRYPTION.txt and WinNT.txt are in the /usr/bin directory. Amongst other things, this means I can't set the recommended security
2004 Sep 10
4
question about using rsync with inetd
Hello, we would like to use rsync (2.6.2 manualy patched and recompiled) in daemon mode spawned by inetd (Solaris 5.8 Environment). /etc/services: rsync 1234/tcp #RSYNC daemon /etc/inet/inetd.conf: rsync stream tcp nowait publish /usr/bin/rsync rsyncd --daemon --port 1234 . Alas, this does not seem to work, there is the following error message in the log file:
2000 May 31
1
netbios-ns/udp: Server failing (looping)
Hi, I've downloaded samba-2.0.7-hppa1.1-hp-hpux11.00.tar.Z and installed it on a HP K380 HP-UX 11.00 server. After starting the services I receive the following messages in the syslog and therefore can't get it to work: May 31 01:54:45 gemtst inetd[5462]: netbios-ns/udp: Service enabled May 31 01:54:45 gemtst inetd[5462]: bootps/udp: bind: Address already in use May 31 01:54:45 gemtst
2001 Mar 29
3
INETD Question.
I'm currently running version 2.0.7 of samba(CIFS9000). I have HPUX 11.x installed on the samba server. When I try to run this from inetd it doesn't work. I can run a startup script that runs the smbd as a daemon and it works fine. But if I try to run it from inetd it won't start. The previous version of Samba 1.9.18p10 that I had on this server worked fine. Is this a bug in
1997 Jan 12
9
dos-attack on inetd.
Hi. I don''t know if this one is known, but I can''t recall seeing anything about it. If it is old news I apologize. I discovered a bug in the inetd that comes with NetKit-B-0-08 and older. If a single SYN is sent to port 13 of the server, inetd will die of Broken Pipe: write(3, "Sun Jan 12 21:50:35 1997\r\n", 26) = -1 EPIPE (Broken pipe) --- SIGPIPE (Broken pipe) ---
2003 Jun 08
2
sub-directory 'hung' ...
'K, not sure how/what to debug here ... doing a grep of svr1.postgresql.org in /proc/*/status shows all the processes 'stuck' in inode ... /proc/38750/status:inetd 38750 2072 2072 2072 -1,-1 noflags 1055120147,191009 0,0 0,592 inode 0 0 0,0,0,2,3,4,5,20,31 svr1.postgresql.org /proc/38752/status:inetd 38752 2072 2072 2072 -1,-1 noflags 1055120154,886433 0,0 0,637 inode 0 0
1997 Dec 04
1
SUMMARY: netbios-ns address already in use?
My original message follows... Well, it would seem that my problem was that nmbd was somehow running as a daemon. Looking at the process IDs the first nmbd had a parent process of 1, not as the ID of inetd. I don't know HOW that happened, the only place nmbd is referenced is inetd.conf. I killed the main nmbd process, sent a HUP signal to inetd, nmbd started again and I haven't had a
2004 May 10
5
rate limiting sshd connections ?
Does anyone know of a way to rate limit ssh connections from an IP address ? We are starting to see more and more brute force attempts to guess simple passwords "/usr/sbin/inetd -wWl -C 10" is nice for slowing down attempts to services launched via inetd. Is there an equiv method for doing this to sshd? Running from inetd has some issues supposedly. ---Mike
1998 Oct 01
1
inetd and Solaris
Environment: Solaris 2.5.1 Samba 1.9.18p3 We run samba from inetd (no special reason - just how its been done in the past). Then on one server we got masses of Samba daemons running (up to 40 as a time trying to run - load average 40+!), giving following complaints: Sep 28 14:39:06 zeus.brunel.ac.uk smbd[10728]: standard input is not a socket, a ssuming -D option Sep 28 14:39:06
1998 Feb 25
1
netbios-ssn/tcp: unknown service
Sorry if this is such a basic question but I couldn't find anything about this in the FAQs/HowTos/Digest. I've compiled samba-1.9.18p3 on SunOS4.1.3_U1. When I tried to run smbd via inetd.conf (SIGHUP), I always get the following on the console. inetd[590]: netbios-ssn/tcp: unknown service I've edited the /etc/services to add: netbios-ssn 139/tcp And the /etc/inetd/conf with
2000 Aug 21
1
strange nmbd behaviour..............
Hello people.... Ok I am having a strange problem with samba and more specificaly the nmb daemon. I run smbd and nmbd as daemons from the /etc/services and /etc/inetd.conf so they run from inetd. But when I check the status with SWAT it tells me that nmbd is not running. So I have to issue the command nmbd -D manualy. Why? my setting on /etc/services and /etc/inetd.conf are exactly like the
2014 Jan 30
1
Issue with running tftpd-hpa in inetd mode?
On 01/30/2014 10:25 AM, Jeffrey Hutzelman wrote: > > Correct. Like most UDP-based inetd services, tftpd is intended to be > run in 'wait' mode. When the first request arrives, inetd starts the > service but does not read the incoming packet (it can't, because it has > no way to pass it along to the server). After that, inetd ignores that > socket until the server
2005 Sep 22
1
Question on Samba Service
Hi, For no particular reason, my Samba service didn't start yesterday, when I went to start it by going in the /usr/local/samba/sbin and then typing SMBD I got an error "permission denied" and something about the port 139 (sorry I don't have the whole error message) No changes were made on the box. I started looking over the web and I found an something out something to
2014 Jan 30
2
Issue with running tftpd-hpa in inetd mode?
Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary OS, VOS (at stratus.com). We've always runs the old legacy tftpd from inetd, so I wanted to continue doing so with tftp-hpa. It seems to work okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that has this at the end: /* * Now that we have read the request packet from
2013 Sep 16
1
Upgrading samba 2.2.8a to 3.6.15 on Solaris 9 --> 3.6.15 brings all inetd services down
Hi samba friends, I'm upgrading our Samba 2.2.8a server to 3.6.15 on a Solaris 9 box, we need to do this as all our latest Mac OS X 10.8 clients cannot map to the 2.2.8a network share, and need the newer Samba (well known issue for mountain lion). I've compiled 3.6.15 and this seemed to go ok, no obvious errors were shown during .configure make and make install, and smbd -V gives
2004 Jan 09
2
inetd & etc
Hello. I know that it is recommended to run smbd as a standalone daemon and to avoid inetd. Can you please tell me why inetd is discouraged and what problems it imposes? Also, I have one user who is having problems accessing her personal files on a MacOSX 10.3.2 via smb. Any ideas what may be causing it? Judy Lin NACS-DCS
2003 Dec 29
2
USER environment
Browsing in the 2003-September archives, I found out how to start dovecot from inetd (using imap-login instead of imap). Still I've got a few problems. I prefer not using inetd, but that seams impossible (see my 1st email). And telnetting to port 143 results in an immediate connection close. Hmmm, I'll continue exploring the archives. Regards Evert