similar to: samba server does not appear in network neighborhood

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'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 all, we have got 4 Samba Servers. All BDCs for "MYDOMAIN", except by SERVER3 that is a PDC. All of them have 3 physical Network interfaces, from which 2 are used by samba. Each of them has a several ip aliases, except by SERVER1 which has only primary ip numbers on its interfaces. When I try to join a new Windows client (XP SP3) to the domain. It asks our wins server for

Hello, I use Samba 3.5.11 from debian. I'm trying to add new Win7Pro to domain, but I still get error: "The specified domain either does not exist or could not be contacted". using wireshark I can see SMB_NETLOGON 279 SAM LOGON request from client SMB_NETLOGON 270 SAM Response - user unknown SMB_NETLOGON 279 SAM LOGON request from client SMB_NETLOGON 270 SAM Response - user unknown

Samba errors with smb QUERY_PATH_INFO, Error: STATUS_OBJECT_NAME_NOT_FOUNDFrom: Timothy D Newcomb Subject: Samba errors with smb QUERY_PATH_INFO, Error: STATUS_OBJECT_NAME_NOT_FOUND > Did you get an answer for this ? I am seeing it on an XP box and I have > the same problem..slow load time...in "my computer" Tim, No I didn't, thanks for the reply. I just figured that

hello I would like to join a Netapp fileserver to a Samba domain that uses an external Openldap server for authentication. Here's what I do and where it goes wrong (I've hidden the real ip addresses). I've also created a machine account for the Netapp server on the PDC.: What is the name of the Windows NT 4 domain? [WORKGROUP]: PCKLAS CIFS - Starting SMB protocol... Wed Jul 5

Hi, Running samba 3.4.0-3ubuntu5.1 on an Ubuntu 9.10 installation. I've previously been running ubuntu intrepid ibex (samba 3.2.3). Since the upgrade I've had issues with a device not finding any wokrgroups/domains when doing an nmb lookup. The device is a wireless music player that can make an SMB connection and has worked fine until the upgrade. When sniffing the network, I get a log

Hello, I already setup a samba server as PDC for windows client to logon and working fine now with the following config: - redhat 7.3 - samba 2.2.7a Then I try to access the samba share from Redhat 8, I can use smbclient to access the share without problem but I can't access the share with "KDE's Konqueror" (smb://NetbiosName/), it can show all shares, when I double one of

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 have own function wrote. I used an algorithm, which was written in Matlab. in matlab: ... gamma = inv(v)*g; ... #v = matrix of variable size, v=vv(k) => k=2 => dimension of v 2x2 #g = a line vector with 4 elements e.g. g=[1,0,2,0]; my rewritten r-file: ... gamma = solve(v)*g; ... which is my error? Who can help me? thank you in advance. Chris -- Lust, ein paar Euro nebenbei zu

Debian Lenny Samba 3.2.3 LOOX N560 with Windows Mobile 5 Hello, ?my PDA LOOX N560 could connect via WLAN to SAMBA under Etch. Meanwhile I upgraded to Debian Lenny and now may PDA cannot connect anymore to the server. Error 1223 or 1222. Connecting to XP-Clients via WLAN is okay. Connecting to Samba Wireshark tells me: malformed packet: No. ? ? Time ? ? ? ?Source ? ? ? ? ? ? ?

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

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

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

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

G'day. I'm using Slackware 7.1 and Samba 2.0.7 When using the tests from samba.org I get to test 3. In there if it fails to listen it says to make sure netbios-ssn is in listen. I scripted my session. Script started on Wed Feb 21 10:13:38 2001 root@Server2001:/home/ashley# smbclient -L Server2001 added interface ip=192.168.0.2 bcast=192.168.0.255 nmask=255.255.255.0 session request to

<earlier, David Rankin wrote to no avail:> Mates, I have been watching a developing problem over the past few weeks. Most likely a M$ patch to XP that has caused problems. What happens is that XP clients try to open the standard "File" -> "Open" dialog (like in word, or whatever) and the file open dialog hangs and stops responding for 15 seconds or so. I have