similar to: port 445 on samba 2.2.8a

Hi Nicolas, On Thu, 1 Feb 2018 10:57:59 +0100, Nicolas Zuber via samba <samba at lists.samba.org> wrote: > I try to update two clustered samba file servers. Right now samba 4.7.0 > with ctdb is running on both of them. To update samba I stopped ctdb on > one of the servers, and compiled and installed samba 4.7.1 with: > > ./configure --with-cluster-support

Hi Nicolas, On Mon, 5 Feb 2018 13:43:33 +0100, Nicolas Zuber <n.zuber at physik.uni-stuttgart.de> wrote: > Am Fr 02.02.2018 um 10:27 schrieb Martin Schwenke: > > On Thu, 1 Feb 2018 13:11:58 +0100, Nicolas Zuber via samba > > <samba at lists.samba.org> wrote: > > > >> after starting the ctdb process and setting the log level to 5. If I set >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I just set up a CTDB-Cluster with two nodes. In /var/log/log.ctdb I saw the following error many times: - ---------- ERROR: samba tcp port 445, is not responding - ---------- the command "ctdb scriptstatus" is showing: - ---------- root at fs1:~# ctdb scriptstatus 11 scripts were executed last monitor cycle 00.ctdb

I have SAMBA 2.0.7 running on about 20 Solaris 9 servers around the US. One location is experiencing interruptions for Windows XP clients who map to the SAMBA server. There are no known changes to Solaris or SAMBA to explain the change. The problem is very random. I have seen postings that discuss how XP uses ports 139 and 445. Is there a way to block port 445 in SAMBA 2.0.7? The

I'm getting strange error when running rpcclient on localhost. rpcclient PRINTSERVER -A auth -d 3 -c "enumprinters" here's result: Initialising global parameters params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" Processing section "[global]" added interface ip=10.223.11.1 bcast=10.223.11.255 nmask=255.255.252.0 not adding duplicate

Because of security reasons, my school has blocked tcp port 445 and 139. This make it impossible to for my window xp desktop to the remote samba service on Linux. Although the samba sercie on Linux and change its port by a "-p" option. But windows always look for 445 and 139 port. I've tried a lot of ways to work it out including local port redirection but none of them works. Is

Hi Benedikt, On Thu, 16 May 2019 10:32:51 +0200, Benedikt Kaleß via samba <samba at lists.samba.org> wrote: > Hi everybody, > > I just updated my ctdb node from Samba version > 4.9.4-SerNet-Debian-11.stretch to Samba version > 4.9.8-SerNet-Debian-13.stretch. > > After restarting the sernet-samba-ctdbd service the node doesn't come > back and remains in state

hi list, I'm a bit of an old skool Samba user, have started using it back in the dark 0.9-ish days. To that end, the ports 137, 138 and 139 and burned deep into my neurons. I've just recently upgraded everything to 3.0.10 (the oldest Samba installation running was 2.2.3). I've seen a lot of garbage disappear from the Network Neighborhood, which is a good thing. One thing, however,

All Samba binaries have a --option parameter, so you could just add to your winbindd startup script/unit '--option=smb ports=445'. This would only change winbindd, and not smbd or other client tools. Andrew Bartlett On Tue, 2020-04-07 at 21:24 +0000, Raees Khan via samba wrote: > > > I will but changing that would block samba from listening for > connections on port 139.

Hello, I'm running redhat enterprise as 3.2 with the included samba 3.0.2-6.3E. I'm trying to make this a domain member server in a nt4 domain. I've successfully joined the domain only after using the net join -p 139 option to force samba to use port 139, otherwise it kept trying to communicate over port 445. (I was watching the syn packets with tethereal). Typing wbinfo -g comes

Running v3.0.2a-SUSE, joined to AD, all clients are XP.SP2 When smb.conf has "smb ports = 139", then %L is populated with the appropriate netbios alias name as selected by the end user, and everything works as expected. When "smb ports = 445" or is not specified, then %L is populated with the host name instead of the alias name. Is there a code patch for %L or an

Hello, I've have an installation where some clients run via a VPN tunnel and modem and that makes W2k clients to connect on port 445, but i need to have it running on port 139 as well so i start smbd for port 445 via inetd and nmbd and smbd on port 139 as daemons. But now for my problem, some local clients have problems when printing, they get permission denied, could that be due to this? And

Hi, i need some help. We have two Networks. A CTDB Cluster and one domain controller in the same network. All other domain controller are outside this network. They are both connected with a firewall / router. We activated netbios over tcp on the other domain controllers outside but it seems that when we remove the single internal domain controller ctdb will not start with the following error.

Hi... I have set up my smb.conf to use the print$ directive, and have shared 3 printers. I sucesfully added the printer drivers to the host, and can use them. But - opening up the printer connection from the windows host is slow, and causes the printer 'status' window to say 'initializing'. While that happens, my samba.log shows : 2003/07/29 16:44:40, 2]

On 06/12/14 20:34, Donelson Trophy wrote: > > > Thank you Hector. Despite my poor spanish, I can see that I need to > check what dependencies are loading with Sernet-samba. > > More tomorrow when I am at a better machine to communicate with the > forum on. > > Thanks. > > --- > > ------------------------- > > Bob Wooden of Donelson Trophy > >

Hi folks, I'm running several samba servers that use "security= server" and "password server" to point authentications to a WinNT pdc. Snooping at the network traffic, I find that the samba server initially tries to connect to the WinNT server through port 445 (which fails), then reverts to 139 (which succeeds). I know it's possible to use the "samba

Am Fr 02.02.2018 um 10:27 schrieb Martin Schwenke: > On Thu, 1 Feb 2018 13:11:58 +0100, Nicolas Zuber via samba > <samba at lists.samba.org> wrote: > >> after starting the ctdb process and setting the log level to 5. If I set >> the log level to 2 it shows that winbind and nmbd starts successfully >> and no complains about a failed smbd process (see log below).

I will but changing that would block samba from listening for connections on port 139. However, in my case I don't see any incoming traffic on port 139 rather the winbind daemon on my samba server tries to connect to the Active Directory Domain Controller on port 139. On Monday, April 6, 2020, 03:55:56 PM PDT, miguel medalha via samba <samba at lists.samba.org> wrote: In the

Hello everyone I am having an issue with one particular windows 10 PC not being able to map a samba share. When I map the network drive:*\\hostname\share* the window prompt to login pops up. I enter the correct username and password and after a minute I get this error: *The network path was not found. 0x80070035*. Looking at the windows 10 logs, I can see this message: *file and print

Thank you Hector. Despite my poor spanish, I can see that I need to check what dependencies are loading with Sernet-samba. More tomorrow when I am at a better machine to communicate with the forum on. Thanks. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [3] "Everyone deserves an award!!" On 2014-12-06 14:23, Hector