Sponsored Content
Full Discussion: Dancing a samba is easier :(
Special Forums Cybersecurity Dancing a samba is easier :( Post 9009 by Andy Hibbins on Sunday 21st of October 2001 02:35:16 AM
Old 10-21-2001
Hi,

Have you got encrypted passwords set up on both machines and have you added the required smbusers and passwords:?

Swat can be started via inetd or xinetd, inetd's config is /etc/inetd.conf whilst xinetd uses /etc/xinetd.d/swat to control swat, can you check that the swat line isn't commented out in /etc/inetd.conf or diusabled in /etc/xinetd.d/swat.

You might also find it useful to check your samba log files, in RH they are in /var/logs/samba.


Hopefully this will give you somewhere to start troubleshooting.
Andy :Smilie
 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Help make script much easier

Is there any method to realise this in one command? Thanks in advance (2 Replies)
Discussion started by: GCTEII
2 Replies

2. What is on Your Mind?

Easier solution to transfer blu-ray and DVD to iPad

Easier solution to transfer blu-ray and DVD to iPad with just one mouse click Because of its 9.7-inch 1024×768 high resolution multi-touch screen, iPad is convenient and comfortable for users to read newspapers, magazines, books, view photos, experience the web, touch emails, and watch any... (0 Replies)
Discussion started by: Molica
0 Replies

3. UNIX for Dummies Questions & Answers

SSH - please make my life easier

I know this is probably a really stupid question, with a really stupidly simple answer. So I've got a Mac, and I have to do a bunch of work via SSH on a Solaris workstation owned by my university. I've already got keys set up, and my ~/.ssh/config file set up as follows: Host prime ... (6 Replies)
Discussion started by: oboewan
6 Replies

4. Solaris

samba issue: one samba share without password prompting and the others with.

Hi All, I've been trying to configure samba on Solaris 10 to allow me to have one share that is open and writable to all users and have the rest of my shares password protected by a generic account. If I set my security to user, my secured shares work just fine and prompt accordingly, but when... (0 Replies)
Discussion started by: ideal2545
0 Replies

5. UNIX for Dummies Questions & Answers

An easier way to move character from field to a new line

Hi ! Is there a more convenient way to do the following: When, in $2, there is more then one letter (separated by ","), it returns the letter on the second position to a new line in $2 with the same content in $1 and $3 as the line this letter comes from. infile: aaaaa A,B 1,2,3,4,5... (6 Replies)
Discussion started by: lucasvs
6 Replies

6. Shell Programming and Scripting

Consolidate several lines of a CSV file with firewall rules, in order to parse them easier?

Consolidate several lines of a CSV file with firewall rules Hi guys. I have a CSV file, which I created using an HTML export from a Check Point firewall policy. Each rule is represented as several lines, in some cases. That occurs when a rule has several address sources, destinations or... (4 Replies)
Discussion started by: starriol
4 Replies
RECONF-INETD(8) 					  System Administration Utilities					   RECONF-INETD(8)

NAME
reconf-inetd - utility to update /etc/inetd.conf and restart inetd SYNOPSIS
reconf-inetd [--verbose] reconf-inetd --sanity-check=fragment [... fragment] DESCRIPTION
reconf-inetd is a maintainer tool that updates inetd.conf. Such updates are based on xinetd.conf-like configuration fragments in /usr/share/reconf-inetd (where server packages install their fragments) and /usr/lib/reconf-inetd (where reconf-inetd keeps track of which inetd.conf entries have been added by itself). reconf-inetd identifies every inetd.conf entry based on the combination of three fields: service name, protocol, and server path. This allows multiple inetd.conf entries for the same service, eg. for IPv4 and IPv6 versions, as well as for different upstreams (eg. proftpd versus ftpd-ssl). reconf-inetd will not add inetd.conf entries for services whose server path is non-existent, or whose combination of protocol, service name and server path matches an existing inetd.conf entry. reconf-inetd does not support internal services. OPTIONS
-h, --help show this help message and exit -c FRAGMENTS_TO_CHECK, --sanity-check=FRAGMENTS_TO_CHECK test the validity of the xinetd.conf-like configuration fragments, as specified by a space-separated list of files -v, --verbose explain what happens -V, --version show version and exit FILES
reconf-inetd declares a file-based dpkg trigger on /usr/share/reconf-inetd. Shadow fragment files are stored in /var/lib/reconf-inetd. A log file is kept at /var/log/reconf-inetd.log FRAGMENT STRUCTURE
reconf-inetd fragments are a much simplified version of xinetd.conf(5) fragments. They have this structure: service <service_name> { <attribute> = <value> <value> ... ... } Of the wide range of fields foreseen by xinetd.conf(5), reconf-inetd honors only these fields: socket_type protocol (optional, except for RPC and unlisted services) port (optional, except for unlisted non-RPC services) wait user server server_args (optional) If the protocol field is omitted and the service is listed, reconf-inetd will assume the protocol of the first matching entry from /etc/services. That will be tcp or udp, which currently implies IPv4, so if the intention is IPv6, then tcp6 or udp6 should be explicitly specified in the protocol field. Unlike, regular xinetd fragment files, reconf-inetd fragment files must have only one service per file. A package that provides more than one service must install a separate fragment file for each service. This is the case to allow for removal of individual services, by simply removing the related file. /usr/share/reconf-inetd fragments are not configuration files; they're just input to reconf-inetd. Local admin configuration should be applied to inetd.conf tcpd-configured service fragments will typically have server set to /usr/sbin/tcpd and server_args will start with the path to the actual server executable. Follows a reproduction of valid atrribute values from xinetd.conf(5): socket_type Possible values for this attribute include: stream stream-based service dgram datagram-based service raw service that requires direct access to IP seqpacket service that requires reliable sequential datagram transmission protocol determines the protocol that is employed by the service. The protocol must exist in /etc/protocols. If this attribute is not defined, the default protocol employed by the service will be used. port determines the service port. wait This attribute determines if the service is single-threaded or multi-threaded and whether or not xinetd accepts the connection or the server program accepts the connection. If its value is yes, the service is single-threaded; this means that xinetd will start the server and then it will stop handling requests for the service until the server dies and that the server software will accept the connection. If the attribute value is no, the service is multi-threaded and xinetd will keep handling new service requests and xinetd will accept the connection. It should be noted that udp/dgram services normally expect the value to be yes since udp is not connection oriented, while tcp/stream servers normally expect the value to be no. user determines the uid for the server process. The user attribute can either be numeric or a name. If a name is given (recommended), the user name must exist in /etc/passwd. This attribute is ineffective if the effective user ID of xinetd is not super-user. server determines the program to execute for this service. server_args determines the arguments passed to the server. FRAGMENT EXAMPLES
Here is an example fragment: service finger { socket_type = stream protocol = tcp6 wait = no user = nobody server = /usr/sbin/fingerd } and it's tcpd-enabled version: service finger { socket_type = stream protocol = tcp6 wait = no user = nobody server = /usr/sbin/tcpd server_args = /usr/sbin/fingerd } BUGS
Known issues and missing features are listed in /usr/share/doc/reconf-inetd/TODO HISTORY
reconf-inetd is a replacement for update-inetd. The motivation for and design of reconf-inetd is detailed at the Debian Enhancement Pro- posal 9, at http://dep.debian.net/deps/dep9/, a copy of which is locally available at /usr/share/doc/reconf-inetd/dep9.html AUTHOR
reconf-inetd was designed, documented and implemented by Serafeim Zanikolas <sez@debian.org> SEE ALSO
inetd.conf(5), xinetd.conf(5), inetd(8), update-inetd(8), deb-triggers(5) reconf-inetd 1.120603 June 2012 RECONF-INETD(8)
All times are GMT -4. The time now is 06:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy