similar to: daytime service on port 13

I can run nmbd successfully, but smbd dies almost immediately when I run it, the smbd.log file has the message "bind failed on port 139 socket_addr = 0.0.0.0.". When I do a netstat -an | grep 139, it shows that tcp is listening on port 139. How do I resolve this conflict between tcp and smbd?

Hello everyone, I am having difficulties in setting up a tftp server on a Fedora 3.14.8-200.fc20.x86_64. Running tftp client to test the server functionality, a simple get from the terminal prompts 'Transfer timed out.' back. The version is tftp-hpa 5.2, with remap, with tcpwrappers, unfortunately I am not able to find any log in the system journal.? The server and related services appear

Im trying to enable the swat utility so that I can manipulate the smb.conf file. I have done this on my PowerMac G4 computer, and now Im trying to set it up on my iBook - but it gives me the following error, xinetd[pid]: bind failed (address already in use (errno = 48). service = swat xinetd[pid]: {init_services} no services. Exiting... I have no idea what is going on, Im doing

https://bugzilla.mindrot.org/show_bug.cgi?id=3729 Bug ID: 3729 Summary: the new sshd does not work under the supervision of inetd Product: Portable OpenSSH Version: 9.8p1 Hardware: ARM OS: Linux Status: NEW Severity: major Priority: P5 Component: sshd

I am running Samba 3.3.2 on Ubuntu 9.04 and /proc/version states "Linux version 2.6.28-15-server (buildd at yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18 20:09:37 UTC 2009". Recently, to support a new client on my home network (running Windows 7 RTM 32-bit), I modified my smb.conf file. The Windows 7 client had refused to connect to Samba with an error

I'm trying to connect to swat but can't. Just installed Samba 2.2.2-5 and edited /etc/services, even though I'm running Redhat 7.3 and use xinetd. /etc/xinetd/swat exists.... but I still cannot connect to http://localhost:901. Why??? Thanks for assist.

I moved an entire RH 6.2 server from one CPU to a new one using a tape backup/restore. Everything from the old server is working on the new server, but when SysV starts up smb, the nmbd daemon (2.0.6) exits with an error: create_subnets: No local interfaces! eth0 has already started according to the logs and console. Any ideas? Thanks. ______________________ Greg Kelley, IT Director SSA, EAA,

I just got a nice, shiny new machine at work, a Core 2 Duo, on which I just finished installing CentOS 5.2 with a fair number of packages, SeaMonkey 1.1.10, Adobe Reader 8.0, Adobe Flash 9.0, mplayer, mplayerplug-in (both from rpmforge), and I think that was it. Then I went and got the latest VMWare Server, 1.0.7, from VMWare, pulled down their rpm, installed it, and ran vmware-config.pl, which

Is it possible to build a dialplan in which shifting from daytime to nightime is not hour based but phone driven ???

I am interested in opinions regarding the use of xinetd versus the use of tcp wrappers. The two programs have similar functionality, but I find xinetd suits my needs better. The biggest problem is the age of xinetd, and AFAIK it is no longer being kept up. Are there any known security issues with xinetd? Another issue is that xinetd makes use of a non-standard inetd.conf layout, but

I sure did check the firewall and selinux as well. As an extreme testing major, they are both turned off. $ systemctl status firewalld firewalld.service - firewalld - dynamic firewall daemon ? ?Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled) ? ?Active: inactive (dead) sestatus? SELinux status: ? ? ? ? ? ? ? ? disabled Actually, now tftp transfers are denied $ tftp 127.0.0.1

Hello, I am trying to monitor a host in the Amazon EC2 cloud. Yet when I try to check NRPE from the monitoring host I am getting an SSL handshake error: [root at monitor1:~] #/usr/local/nagios/libexec/check_nrpe -H ops.jokefire.com CHECK_NRPE: Error - Could not complete SSL handshake. And if I telnet into the host on port 5666 to see if the FW port is open, the connection closes right away:

I have got now Redhat 7.0 and when I want to install Swat I need to edit the file /etc/inetd.conf but in Redhat 7.0 the file is named to /etc/xinetd.conf and /etc/xinetd.d can you help me ? (In Redhat 6.1 it worked alright) Greetz Rob op den kelder -------------- next part -------------- HTML attachment scrubbed and removed

I created a subversion repository on my new vps and i''m trying to setup my rails app there. However i keep getting this error: subversion/libsvn_subr/io.c:2516: (apr_err=13) svn: Can''t create directory ''/home/svnadmin/rapleaf/db/transactions/0-1.txn'': Permission denied How do i fix this? I know others have had this before, so i would appreciate some help.

I have the following situation: A Linux 2.4.22 server: Physical ethernet: lan1 - Ethernet port (Internet) lan2 - Ethernet port (Cisco Switch, Trunk port) Tunnel: tap1 - OpenVPN in tcp-server mode VLAN's: lan2.201 lan2.202 lan2.203 tap1.201 tap1.202 tap1.203 Bridges: br201 (lan2.201, tap1.201) br202 (lan2.202, tap1.202) br203 (lan2.203, tap1.203) On the other end, the same type of server:

Hi all, I have recently installed samba-2.2.7-3.7.3.i386.rpm,samba-common-2.2.7-3.7.3.i386.rpm, samba-client-2.2.7-3.7.3.i386.rpm and samba-swat-2.2.7-3.7.3.i386.rpm. After i installed all these, I start the SMB services and i enable swat, but when i tried to access SWAT from the browser, using : http://localhost:901 or http://127.0.0.1:901 it returns with " the document contain no data.

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

Hi There I need help on setting up swat 3.0.0 on RedHat 7.1. I've got xinetd installed but not inetd and can't find configuration to setup swat on xinetd. Do I need inetd and where do I get it from. New in the game so please be pasient Anton

The only docs I found on getting SWAT to run, showed editing the inetd.conf file. As this version of RH (7.3) only uses xinetd things don't fit exactly. I have gone through and did everything that one should do for inetd and it still will not work. I don't normally use the thing, but this client will need the more simplistic interface to add shares, etc.

Hi, I'm having a minor issue with swat on red hat 7.2. It won't let me make any changes to the samba server (adding shares, printers, and global definitions). The buttons to access these simply don't exist. I can view status, but I can't make any changes (not even restart the daemons). This works fine on my Debian system. The only real difference that I can think of is inetd