search for: 445

...0 0 DROP udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:135 0 0 DROP udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpts:137:139 0 0 DROP udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:445 0 0 DROP tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:135 0 0 DROP tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:139 0 0 DROP tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:...

...y ideas? Is this fixable on the server-side? Otherwise if that is not possible, fixable on the client-side while still permitting microsoft accounts? Packet dump (raw): https://www.vulnscan.org/tmp/cannotconnectsmb.pcap Packet dump (text) below: 1 0.000000 10.0.6.178 -> 10.0.0.7 TCP 66 49939→445 [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1 2 0.000049 10.0.0.7 -> 10.0.6.178 TCP 66 445→49939 [SYN, ACK] Seq=0 Ack=1 Win=29200 Len=0 MSS=1460 SACK_PERM=1 WS=128 3 0.002343 10.0.6.178 -> 10.0.0.7 TCP 60 49939→445 [ACK] Seq=1 Ack=1 Win=65536 Len=0 4 0.002514 10.0.6.178 -> 10.0...

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 ==============...

...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). > > Now the guesses get more esoteric. :-) > > What do you see if you run "ss -tlnp src :445" as root? > > I see smbd listening on both IPv4 and IPv6: > > LISTEN 0 50 > *:445 *:* > users:(("smbd",pid=2315,fd=36)) LISTEN 0 > 50 :::445 :::* > users:((&qu...

...chine shows the following: ... normal looking connections to obtain drivers - all look OK - no complaints.. .. then this - libsmb/namequery.c:name_query(415) Got a positive name query response from 10.1.1.111 ( 10.8.40.97 ) lib/util_sock.c:open_socket_out(898) error connecting to 10.8.40.97:445 (Connection refused) libsmb/namequery.c:name_query(415) Got a positive name query response from 10.1.1.111 ( 10.8.40.97 ) lib/util_sock.c:open_socket_out(898) error connecting to 10.8.40.97:445 (Connection refused) smbd/service.c:close_cnum(659) bd004580 (10.8.40.97) closed connection to serv...

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 th...

When I use smbclient to access an IOMEGA NAS server, smbclient tries to access port 445 for a full five minutes before timing out: [2004/02/20 17:48:24, 10] lib/gencache.c:gencache_get(262) Returning valid cache entry: key = NBT/NAS_120_1#20, value = 192.168.123.161:0, timeout = Fri Feb 20 17:53:22 2004 [2004/02/20 17:48:24, 5] libsmb/namecache.c:namecache_fetch(201) nam...

...out 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 "smb ports" configuration file entry is invalid for 2.0.7. I tried "smb -p 139 - D" and there is still traffic on port 445. Is there a way to block all TCP port 445 activity on the server side without having to learn...

...erver-side? Otherwise if that is > not possible, fixable on the client-side while still permitting > microsoft accounts? > > Packet dump (raw): https://www.vulnscan.org/tmp/cannotconnectsmb.pcap > > Packet dump (text) below: > 1 0.000000 10.0.6.178 -> 10.0.0.7 TCP 66 49939→445 [SYN] Seq=0 > Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1 > 2 0.000049 10.0.0.7 -> 10.0.6.178 TCP 66 445→49939 [SYN, ACK] Seq=0 > Ack=1 Win=29200 Len=0 MSS=1460 SACK_PERM=1 WS=128 > 3 0.002343 10.0.6.178 -> 10.0.0.7 TCP 60 49939→445 [ACK] Seq=1 Ack=1 > Win=65536 Len=0 > 4 0...

-----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 Status:OK Duration:0.031 Fri Dec 5 14:00:52 2014 01.reclock Status:OK Duration:0.125 Fr...

...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 [global] section of smb.conf try: smb ports = 445 The default is: smb ports = smb ports = 445 139 -- To unsubscribe from this list go to the following URL and read the instructions:? https://lists.samba.org/mailman/options/samba

...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). > > > > Now the guesses get more esoteric. :-) > > > > What do you see if you run "ss -tlnp src :445" as root? > > > > I see smbd listening on both IPv4 and IPv6: > > > > LISTEN 0 50 > > *:445 *:* > > users:(("smbd",pid=2315,fd=36)) LISTEN 0 > > 50 :::445...

...nothing changed on the server. Recently (Jan 27th) some of the Archlinux clients updated from a 4.8.x kernel to a 4.9.x kernel. Again, things ran fine. Then on Jan 30th around 2am the Archlinux clients using 4.9.x kernels and utilizing mount.cifs to access samba shares began thrashing on TCP port 445, causing high CPU load on the server. These machines now cause thrashing after 15-20 minutes whenever a share is mounted using mount.cifs. When it's thrashing, I see thousands of opened ports from a single client: # sockstat -4 | grep 10.0.1.87 | wc 10013 70091 740962 And on the client,...

....223.11.1 added interface ip=127.0.0.1 bcast=127.0.0.255 nmask=255.255.255.0 resolve_lmhosts: Attempting lmhosts lookup for name PRINTSERVER<0x20> resolve_hosts: Attempting host lookup for name PRINTSERVER<0x20> Connecting to host=PRINTSERVER share=IPC$ Connecting to 10.223.11.1 at port 445 error connecting to 10.223.11.1:445 (Connection refused) Connecting to 10.223.11.1 at port 139 lsa_io_sec_qos: length c does not match size 8 cmd = enumdrivers However, I get the result correctly. If I run it without debugging parameter I get no error messsage. Can anybody tell me why? Or what sho...

...ot; was "shared" and the firewall was configured to allow a connection for "file and printer sharing" only for our download machine. Now when we do: smbclient '\\Testmachine\Example' -U 'Administrator%xxx' -d 3 it logs ... Connecting to 131.215.XXX.YYY at port 445 timeout connecting to 131.215.XXX.YYY:445 Connecting to 131.215.XXX.YYY at port 139 Doing spnego session setup (blob length=16) ... There's a longish delay between the first and second lines. (Of course xxx is a real password and XXX.YYY were real numbers in the original.) Now here's wher...

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 ports" parameter to control which ports the samba server listens on, but this seems to have no effect on which ports are used to talk to the password server. I'd like to tell the samba s...

...LY 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 UNICAST_SUBNET, then proceeds to try and sync with it over port 445. The connection to port 445 works JUST FINE. I get connected, the connection to IPC$ happens just fine and the return from the cli_NetServerEnum calls for Domains and everything else complete fine. The problem is the returned lists are empty !!! Debug logs show: "sync with HOMEOFFICE(172.16.10...

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 undocumented %parm to use instead to get the alias name as selected by the client (not the hosting server name)?? The reason I ask is because Netbios is still respondin...

...retch 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 "UNHEALTHY". I can find that in the syslog: May 16 11:25:40 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445 May 16 11:25:40 ctdb-lbn1 ctdb-eventd[13184]: monitor event failed May 16 11:25:42 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445 May 16 11:25:42 ctdb-lbn1 ctdb-eventd[13184]: monitor event failed May 16 11:25:46 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not listeni...

...an-13.stretch. > > After restarting the sernet-samba-ctdbd service the node doesn't come > back and remains in state "UNHEALTHY". > > I can find that in the syslog: > > May 16 11:25:40 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not > listening on TCP port 445 > May 16 11:25:40 ctdb-lbn1 ctdb-eventd[13184]: monitor event failed > May 16 11:25:42 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not > listening on TCP port 445 > May 16 11:25:42 ctdb-lbn1 ctdb-eventd[13184]: monitor event failed > May 16 11:25:46 ctdb-lbn1 ctdb-eventd[13184]: 50...