similar to: test 3 help

Hi, I am having some troubles setting samba up nicely on my Slackware 7.1 machine. It is currently just a web/ftp server mainly for my personal use at home. I downloaded the tarball samba-2.0.7 and did everything to install it "properly." I edited services to include: netbios-ns 137/tcp # NETBIOS Name Service netbios-ns 137/udp netbios-dgm

Hello all I've just installed samba 3.0 alpha from cvs, on a red hat 8.0 linux station, and I have some strange behavior when I start the samba daemons : First there is no success / failure indication [root@linux-integ francois]# /etc/rc.d/init.d/smb start Starting SMB services: Starting NMB services: But the daemons seem to be running : [root@linux-integ francois]# netstat -a ... tcp

Hello samba people. I am having a odd problem related to winbindd. When I leave it running overnight on a quiet (not silent however) server I find that it generates a large number of CLOSE_WAIT state connections. 84 on a fairly quiet system in the last 18 hours. I can't seem to find any command that directly affects the number of CLOSE_WAITS. Below is my netstat listing. Any ideas would

I've setup samba on my slacware box. Here is my smb.conf: ###################################3 My SMB.CONF ###################################3 root@darkstar:/usr/local/samba/bin# cat ../lib/smb.conf [global] workgroup = home netbios name = darkstar [videos] path = /mnt/backup public = yes writable = yes ###################################3 My TESTPARM SMB.CONF

Hello, I would like to ask you if its possible to run Samba on an other port than 137-139? I tried once to edit the "/etc/services" File. The lines: ... netbios-ns 137/tcp netbios-ns 137/udp netbios-dgm 138/tcp netbios-dgm 138/udp netbios-ssn 139/tcp netbios-ssn 139/udp ... I changed it to: ... netbios-ns 6998/tcp netbios-ns 6998/udp netbios-dgm 6999/tcp netbios-dgm 6999/udp

Before wasting a lot of time going at this in the wrong list, I would like to confirm whether my thinking is on or off base with respect to source and destination ports. Samba is being blocked by fw2loc even though I have accept rules set up. I believe I can explain why, but I could be wrong. I think that for some reason, samba is sourcing stuff on the commonly used port 137, but trying to send

Hello, I am new to samba and i would to well secure it. In smb.conf, I entered the following lines : hosts allow = 192.168.0.2 127.0.0.1 hosts deny = 0.0.0.0/0 bind interfaces only = yes interfaces = eth0 lo I thought that it would only listens on the local machine and my internal Lan (which is on eth0 192.168.0.1) but nmbd seems to always listen on UDP/137 and UDP/138 (netbios-ns and

I've got Samba 2.0.6 set up for domain logons, and they kinda work. However, about 2 out of 3 times it doesn't work on the first try. Almost always, my log on succeeds if I continue trying, usually 2-5 more times. The workstation is Windows 98. I can't roll this out to my clients until I can get this to work every time, on the first try. I've looked through the list archives, and

I'm trying to get running an ethernet with two machines: a samba server running suse linux 6.4 and a client running windows 98. I follow the steps in the DIAGNOSIS.txt file, but I get stucked when executing 'net view \\SERVER' in the client. I have laready done everything it says in that file: 1) Set a lmhost file in the client. Just with this line: 192.168.0.1 ASTERIX #Asterix is

Hi all, I've recently setup samba 2.2.5 on a solaris 8 workstation and configured it to be a member of an NT domain. Everything is working correctly, with the exception that the samba server does not appear in the network neighborhood of the rest of the PC's in the domain. However, if you choose to "search for computers" and enter the netbios name of the server it is

I am getting errors when I try to start smbd which say that port 445 is already in use, but nothing else is using it. In the log, the full error is: -----start log.smbd---- [2004/02/02 11:03:53, 0] lib/util_sock.c:open_socket_in(662) bind failed on port 445 socket_addr = 0.0.0.0. Error = Address already in use ------end log.smbd----- In my /etc/services file, I have these entries:

(Please forgive the cross posting; I know many SuSE users subscribe to both the Samba and SuSE-e discussion groups and will get this message twice.) I had always been frustrated trying to get SuSE's Firewall2 to play nicely with Samba and support seamless network browsing. After much experimentation and a lot of Googling, I was finally able to get this working. By "working",

I need help. For over a year I have been running SAMBA 2.05a under RedHat 6.1 (kernel 2.2.x) without problem. Then a couple days ago a power glitch crashed my system (UPS not powerful enough any more). Now SAMBA is not running. Here are the symptoms: As RedHat is starting up, both smbd and nmbd are listed as successful. /var/log/messages indicates: Dec 30 13:19:45 we-24-126-201-41 smb: smbd

Does Samba allow me to mount NT (disks) file systems on my Unix (SGI) box? Randy -- Randy Fox Coryphaeus Software, Inc. Sr. Software Engineer 985 University Ave. Suite 31 rfox@coryphaeus.com Los Gatos CA, 95030 www.coryphaeus.com Tel: 408/395-4537 Fax: 408/395-6351

I have a Solaris box and Windows 2K box connecte through a hub, along with a DSL modem. I cannot get the two boxes to work via Samba, here is the relevant details. The status report from SWAT # Samba config file created using SWAT # from localhost (127.0.0.1) # Date: 2001/03/02 12:54:01 # Global parameters [global] netbios name = MARISOL server string =

Hi folks... I'm configuring Firewall in the server running Conectiva Linux 6.0 (Brazil) and I already configured to accept connections in the ports: netbios-ns 137/tcp # NETBIOS Name Service netbios-ns 137/udp netbios-dgm 138/tcp # NETBIOS Datagram Service netbios-dgm 138/udp netbios-ssn 139/tcp

AT&T Broadband blocks ports 137,138, and 139. They want to protect those Windows users that install File and Print Sharing from viruses and attacks. Mason Kidd > > Message: 2 > Reply-To: <bdefreese@cox.net> > From: "Barry deFreese" <bdefreese@cox.net> > To: <samba@samba.org> > Subject: RE: [Samba] using samba over AT@T broadband > Date: Mon,

I'm trying to get Samba up and running and having a terrible time. It says that I should be able to run nmap and see that 137 and 139 are open - which they are not. I have not added any restrictions in smb.conf, do not have a firewall running and I have increased the log level to 5 to see all of the messages. It says that it is talking on 137 but it kind of looks like it's not talking

Hi team, one small query, Is netbios-ns,netbios-dgm and netbios-ssn ports 137,138,139 need to be open to communicate with windows from linux. what was the use of these services??

Sirs, Thank you for any time that you take to read about my problem. I have a Linux (redhat) 8.0 mail server set up with; qmail dhcp / dns transparent proxy to internet - adsl HTML & our web pages (nothing special) SAMBA This problem has been with me since RedHat 7.3 and thir packaged samba. If I transfer a file from the mail (linux box) box to a win98se box it takes a