similar to: Desperately needing help with Samba

Having trouble with Samba. The config file passes the test (testparm) The Server seems to be upa and running fine (smbclient -L localhost) But can't seem to connect to it from other computers (running 2000 or 98) They were able to connect once though. What should be listed on port 139 in services. We have : netbios-ssn Does this sound right? Appreciate any help/suggestions!! Regards, Andrew

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?

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,

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

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

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

Our Client software used samba protocol,If there is no firewall case , this protocol work properly from remote site.All of firwall configuration open ( this mean is all of port open ). Samba work very well, but if some constrain put in, it doesn't work. 1)I would like to know about port usage of samba protocol. I think snmpd, nmpd daemon used some port number. i can see /etc/service file.

I am out of the office until Tuesday Aug 6th. If you need immediate attention please contact Don Jemtrud at don@magnumlog.com or call 297-6205. >>> "samba@lists.samba.org" 08/04/02 08:26 >>> Send samba mailing list submissions to samba@lists.samba.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.samba.org/mailman/listinfo/samba or, via

Hi Tom, How are u? hehehe I have a question. I have 2 pc with redhat 9.0 configured with ipsec freeswan 1.99 (vpn) and i have to tranfer file from one to the othert one. I see that ftp tranfer have a throughtput is the double than a netbios tranfer... why??? I supposed the problem is the TOS.(/etc/shorewall/tos) and i modified the file like ftp... in this method. #SOURCE DEST

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

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

Samba not responding to broadcast calls from networked PCs. Short: My Redhat Linux 8.0 box is not replying to udp broadcasts, and I can't figure out why. Network: The offending Redhat 8.0 Linux Box (//DS) attempting to run Samba 2.2.7 Firewall Redhat 7.3 (//IW) successfully running Samba 2.2.4 Win98 (//MS) Win2k (//SL) <Not running at the time of these tests> Very long: I've

Sorry if this has been covered before. I setup a new Samba server using RedHat EL 3, and samba 3.0.2-6.3E (the version that comes with Redhat). We were seeing an intermittant 20 seconcd delay when grabbing a directory listing, but only from XP, win 2k was fine. I couldn't completely nail down when the delay occured but it seemed to be when the directory or share hadn't been accessed

Could you help a poor helpless guy how to get information to use samba under a linux virtual server? which port are used by samba? Pierre -- _______ | 0 0 | ------------00---O---00o----------------- Pierre Binet Service d'Etat a l'Aviation Civile Division Technique BP 6011 98702 Faa'a/Aeroport mail :binet_pierre@seac.pf tel :(00 689) 861261

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

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

When I try and load smbd I get this error in the log :- bind failed on port 139 socket_addr=0.0.0.0 (Address already in use) Closing connections 04/02/1998 14:02:01 Server exit (caught signal) I am using Slackware 3 with Linux kernel 2.0.33, and Samba-1.9.18p4. there is no problem with Netbios naming as I can see th Linux machine in Network Neighbourhood and my samba client seems to be

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

Hallo I'm using samba 2.2.8a rpm packet on a redhat 9.0 On the same machine I use iptables with standard policies with DROP With ports do I need to open for printing on from my windows pc to work Best Regards Jan madsen