search for: 139

Hi, I have the following problem while activating this rule entry using shorewall-shell: ACCEPT:notice:rul WAN:139.x.x.226 INT:139.x.x.153-139.x.x.156 udp 1024:65535 1024:65535 "-m iprange" in front of "--dst-range" is missing in the activation command. The logging entry (above) is set correct. Below is the debug output. Thanks Regards Günter + case $level in + /usr/sbin/iptables -A...

...uot;. Here's what I did: I have linux server running samba 2.2.8a and windows XP as client machine. @ In windows, disabled file and printer sharing and enabled LMHOSTS lookup. @ In windows, created lmhosts with '127.0.0.1 fakename' @ In widnows, ran ssh client with local forwarding. 139 localhost:139 @ In linux, I can telnet to 127.0.0.1 139 @ In windows, I can telnet to 127.0.0.1 139. If I run 'netstat -tn | grep 139' from ssh client, I get something like: $ netstat -tn | grep 139 tcp 0 0 127.0.0.1:139 127.0.0.1:2708 ESTABLISHED tcp...

...I am installing Samba 2.0.7. I have the services and inedt.conf files with the needed entries and have add a program check my entry. I get the following error in the log file and can not figure out what is wrong. [2001/01/17 12:31:59, 0] lib/util_sock.c:open_socket_in(863) bind failed on port 139 socket_addr=0.0.0.0 (Address already in use) [2001/01/17 12:50:46, 0] lib/util_sock.c:open_socket_in(863) bind failed on port 139 socket_addr=0.0.0.0 (Address already in use) [2001/01/17 12:54:43, 0] lib/util_sock.c:open_socket_in(863) bind failed on port 139 socket_addr=0.0.0.0 (Address alread...

I have a machine running redhat 6.2 and samba 2.0.6 that does a persistent mount to my Windows 2000 machine for the purposes of serving files via FTP. The samba connection occasionally times out it seems, I get the message smb_request: result -32, setting invalid smb_retry: new pid=20679, generation=12 and it generates a new connection I've got SO_KEEPALIVE active in the socket options in my

...d scheduler crond [ OK ] * Restarting OpenBSD Secure Shell server sshd ---- xend.log [2010-07-04 13:14:30 9855] DEBUG (XendDomainInfo:1891) XendDomainInfo.handleShutdownWatch [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices tap2. [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices vif. [2010-07-04 13:14:30 9855] DEBUG (DevController:144) Waiting for 0. [2010-07-04 13:14:30 9855] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vif/32/0/hotplug-status. [2...

...reveu: > Is this samba 3.x or 4.x? DC or member server? > > I found for samba 3.x it was better to not explicitly define any ports in > smb.conf. > > > > > > > On 01/16/15 13:25, Thiago Ten?rio wrote: > >> Hi, >> >> I need to enable smb port=139 to get the hostname from internal machines >> when working with full_audit and by default I can access my server using >> \\server or \\server.my.domain but when enabled smb port = 139 I have >> problem to access \\server.my.domain. >> >> The message says that I can...

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

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?

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

...o. 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 to use 139 instead of 445. I can not enumerate the groups and users from that server. I even had the samba/winbind system become a member of that domain but the only groups that will enumerate are those of...

Hi, I need to enable smb port=139 to get the hostname from internal machines when working with full_audit and by default I can access my server using \\server or \\server.my.domain but when enabled smb port = 139 I have problem to access \\server.my.domain. The message says that I can't access \\server.my.domain. The problem...

I have upgraded samba to 2.2.7a and cannot print to my printer attached to my BSD machine. I can use the share dirs, etc, but cannot print. My log file contains: [2003/03/17 16:17:19, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use [2003/03/17 16:18:02, 0] smbd/service.c:make_connection(252) 50163099sp (204.250.145.147) couldn't find service c [2003/03/17 16:20:46, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address alr...

...erver. I have set up a share and can successfully connect to that share with no ssh tunnel. I would like to tunnel SMB over SSH, so here is what I have tried: 1. Disabling Windows File Sharing with "net stop server". Then, using puTTY, I connect with my ports forwarded. I forward 80 and 139. "http://127.0.0.1" yields my web server's start page, so I know forwarding is working. When I "telnet 127.0.0.1 139" it connects to the SMB server successfully. "netstat -ano" reveals that 127.0.0.1:80 and 127.0.0.1:139 are listening with puTTY. However, trying t...

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/u...

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

Here's the output: Feb 9 15:51:26 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:40:2b:67:5b:a7:08:00 SRC=192.168.1.54 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=51248 DF PROTO=TCP SPT=1964 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 9 15:51:28 SSI001 kernel: SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:0f:ea:73:88:12:00:12:3f:a1:fd:1b:08:00 SRC=192.168.1.61 DST=192.168.1.2 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=2065 DF PROTO=TCP SPT=1136 DPT=445 WINDOW=65535 RES=0x00 SYN UR...

...Mandrake 9) When I tested my firewall at grc.com, Shields-Up informs me that ports 113 and 135 are closed and not ''stealthed'' When reading the faq on the Shorewall site I saw that shorewall rejects rather than denys connection requests on ''TCP ports 113, 135, 137 and 139 as well as UDP ports 137-139''. The file /etc/shorewall/common.def advises me not to edit the file but rather to create a new one. Can anyone give me an idea on how to do this so that the above ports deny request attempts. I guess this must be a fairly common question on the list, but...

I am running SUSE 12.0 I have had this problem on another machine months ago, but never solved it. I have done many searches, but have come up empty. When booted, port 139 is not open on IPv4. There os no 0.0.0.0:139listening. HOWEVER: :::139 is listening. SO I know it is open on IPv6. When I try to gain remote access through a share, the machine is not found. When I try to telnet to port 139, the connection is refused. To solve it, I have to manually restart sm...

I run samba 2.2.8a on my openbsd 3.4 box, installed from a package. All i need is the ability to mount disks form winxp boxes so i only run smbd, at 139/tcp. I tried scanning the box with nessus, and it came up with some results that got me curious. Since i dont know very much about the smb protocol I thought i should ask here. Have searched the archives but found only old posts, concering older versions. Whats a NULL session? what are domain a...

...-------- CPU states: 18.3% user, 0.0% nice, 81.7% system, 0.0% interrupt, 0.0% idle Mem: 336M Active, 3109M Inact, 210M Wired, 163M Cache, 214M Buf, 16M Free Swap: 10G Total, 8K Used, 10G Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 26348 criacao 1 139 0 40248K 8088K RUN 1 22:08 21.04% smbd 51011 junior 1 139 0 40588K 8112K RUN 1 1:57 18.75% smbd 50753 andrea 1 139 0 40244K 8060K CPU1 1 20:32 16.50% smbd 52143 criacao 1 139 0 40532K 8136K RUN 1 1:40 13.53% smbd 26798 adriano 1...