similar to: winbind with ports 445/139 blocked

Displaying 20 results from an estimated 20000 matches similar to: "winbind with ports 445/139 blocked"

2007 Nov 30
2
blocked ports 445 and 139 make printer-shares very slow
Hi, do ports 445 and 139 (incoming) have to be open for the samba server's IP on WinXP client side (all WinXP clients are using netbios over TCP/IP)? F-Secure 7.10 blocks all incoming microsoft-ds (445) and netbios-ssn (139) by default, which ends up in very slow printer-shares behaviour (for example opening the properties or the spool window of a samba-printer takes up to 30 seconds). For
2003 Jun 03
2
Problem with HTTP traffic (very slow)
I have two machines running 4.8-RELEASE ... both sitting on the same switch, same hardware, same everything really. One gets 200k/s using wget / curl / w3m to a http address the other gets 6k/s to the same address. On the slow http machine I get 200k/s via scp or ftp to the same address it's just web traffic that is slow (note web traffic to all other locations is 4 - 6k/s as well). I've
2008 Oct 31
2
Friday Halloween Edition Oct 31 12 Noon EDT
Morning! This may be the "day of the dead" in some regions, but we expect the usual lively discussion today at 9AM PDT, 11 Central, 12 Noon EDT, 4PM UK and Portugal, 5PM Paris, $deity-forsaken hour down under. This Sunday, I believe the USA falls back to Standard time. Future VUC are still at 12 Noon EST. Info site: http://voipusersconference.org PSTN (724) 444-7444 enter 22622# 1#
2007 Jul 10
1
Migrating subscription lists
I thought this would be relatively straightforward....I would create .subscriptions by doing an ls -1 of ~/mail. I'm running into some problems. 1) the ~/mail directories haves directories in them for 5% of the accounts! AFAIK, our mail sevice has always been UWIMAP with mbox format INBOXes, and it was my understanding that the mbox format is flat and NOT hierarchical and thus I'd
2006 Apr 27
1
Filename too long
This is the rsync version I am using. rsync version 2.5.5 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 64-bit system inums, 64-bit internal inums I have a file with a looooong name which I rsync from PC1 to PC2. (redhat-9) I am getting the
2016 Jul 09
4
Option configure
Hello, Am 09.07.2016 um 09:14 schrieb Rowland penny: >> What is the purpose of the option >> * >> **--with-**systemd** >> ****Enable****systemd****integration* >> >> To configure Samba (build). >> > > It is there so that there is also the '--without-systemd' option. > > one turns on systemd integration, the other (thank your deity)
2018 Jun 13
0
No ports 445/139 & smbclient shows NT_STATUS_CONNECTION_REFUSED
Hi all, I'm maintaining a small AD system on a computer called "ad" in our small charity, and it has been working fine for a year or so. However, "ad" is very rickety so we got a proper server purchased and now I'm trying to move the AD system over.  I've set up the new server called "org-ad" with Debian 9 and followed the instructions here
2004 Jun 30
3
Manually installing syslinux?
I am wondering if it is possible to install syslinux manually, without the actual syslinux utility. Basically I have a little linux distro that uses syslinux. I have an automated upgrade system that also updates the bootloader before rebooting. I currently compile syslinux (and mtools) statically, so that the new syslinux will not depend on any libraries on the old software version (since they
2004 Jul 13
2
Port 445 & Port 139 banned
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
2020 Apr 06
2
How to force Winbind to use port 445 to talk to Windows Active Directory
We have Samba4 installed on CentOS 7.3 and it is integrated with Windows AD for user authentication. Everything is working fine, but we see a lot of Firewall denies on port 139. Upon investigation, I found that Winbindd on my Linux machine is trying to connect to AD on port 139. I ran winbind -i -d 3 and noticed that Winbind tries connecting to Windows AD on port 445 as well port 139. I would
2020 Apr 07
2
How to force Winbind to use port 445 to talk to Windows Active Directory
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
2020 Apr 07
0
How to force Winbind to use port 445 to talk to Windows Active Directory
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.
2003 Nov 10
1
Forcing Samba & Winbind to use port 139
Hello. I have a situation where I need to communicate with an NT server that is behind a firewall, the admins of which will not allow port 445 traffic to pass through. With the setup I have, smbmount and smbclient literally take minutes to issue back a response from said server unless I issue '-p 139', in which case I get a response almost instantly. My larger issue is getting winbind
2002 Aug 29
1
Starting an both port 139 and 445
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
2002 Oct 03
5
Port 139 versus Port 445
I've noticed that my W2K clients connect to Samba much more quickly if I run it on port 445 instead of 139. However, my WNT clients then won't connect at all. I read somewhere that it was possible to forward the requests on port 139 to port 445. Anyone know how to do this or how to listen to both ports simultaneously? Thanks, Jason Joines Open Source = Open Mind
2002 Sep 07
2
UNICAST cross-subnet browsing, Port 445 vs. 139, and Win2k
I have been having a heck of a time getting cross subnet browsing to work properly. After MANY hours hunting through source and debug logs, I have FINALLY found the source of my browsing issues. My Samba nmdb properly becomes the LMB for my segment on a WAN. I VPN to my servers at the home office and Samba attempts to sync with the DMB. nmbd properly locates the DMB via WINS over the
2011 Jul 13
1
Problem adding an usb device
I install an XP on xen, and it worked fine, but i want to add a usb device in the machine. so i use the methods in http://www.virtuatopia.com/index.php..._domainU_Guest while, first i wanted to use the dynamic method, which is the second one, but it failed, because when i get into the machine, ctrl+alt+2 didn''t bring me to a console interface other than nothing. so I tried the first
2016 Jul 08
2
Option configure
Hello! What is the purpose of the option * **--with-**systemd** ****Enable****systemd****integration* To configure Samba (build).
2002 Apr 29
3
ports ''closed'', not ''blocked''???
Using Shorewall v1.2, and testing the firewall using scan.sygate.com, I am informed that several ports (web (80), ident (113) and DCE locator (135) are ''closed'' rather than ''blocked''. All other ports show as blocked or ''stealthed''. I haven''t set up any rules or policies that have anything to do with 80, 113 or 135. Is this
2007 Jan 25
1
TCP Bad checksum packets on ports 445
Hello, I'm observing slowdown on my network, so I started some tcpdump sessions to see what is happening on my main box, which hosts a samba PDC server, DNS, NTP and SSH servers. viewing those sessions with ethereal, I see that approx 10% of the net traffic is bad packets. Those Packets are tagged 'Bad Checksum'. The whole packets come from the server to the clients, from port