search for: tulpn

...ualmin panel, and each time that I reboot Apache can't start: Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down I do: netstat -tulpn| grep :80 tcp 0 0 :::80 :::* LISTEN 1584/httpd killall -9 httpd And then Apache can start. But do you why thos problem in each reboot? I like to fix this problem. Thansks you. Ernesto

...root -g root -m 755 -d /var/log/samba end script exec /usr/local/samba/sbin/samba -D However, I am finding that this is not the case. From what I can tell, the script is doing something, just not anything useful (highlights denote difference between boot with conf file versus without). [netstat -tulpn on boot] tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 769/smbd tcp 0 0 10.52.2.91:53 0.0.0.0:* LISTEN 1076/named tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 1076/named tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 900/sshd tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 1076/named tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 769/smb...

...ontainer (ubuntu 18.04 too) as Domain Member with File Server (fs.smb.domain.tld). Administration through Windows OS will be done with a Qemu KVM. Bad thing is that I get : > Failed to bind to 0.0.0.0:53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED as dnsmasq is using port 53 : > netstat -tulpn | grep ":53" > tcp        0      0 192.168.122.1:53 0.0.0.0:*               > LISTEN      1283/dnsmasq > tcp        0      0 10.0.3.1:53 0.0.0.0:*               LISTEN      > 1062/dnsmasq > tcp6       0      0 :::53 :::*                    LISTEN      > 1161/samba: ta...

I have Samba4 4.1.14 (built from sources) installed at Ubuntu 14.04 LTS x32 and acting as Standalone server at the time. Here are 3 faces at Ubuntu: lo, lan and wan. There are lines: bind interfaces only = yes interfaces = lo lan0 in smb.conf But netstat -tulpn shows 0.0.0.0 binded address: tcp 0 0 192.168.0.254:139 0.0.0.0:* LISTEN smbd udp 0 0 192.168.0.255:137 0.0.0.0:* nmbd udp 0 0 192.168.0.254:137 0.0.0.0:* nmbd *udp 0 0 0.0.0.0:137 <http://0.0.0.0:137> 0.0.0.0:*...

...hlfeld at samba.org>: > Hello, > > Am 11.01.2015 um 14:55 schrieb CpServiceSPb .: > > Here are 3 faces at Ubuntu: lo, lan and wan. > > There are lines: > > bind interfaces only = yes > > interfaces = lo lan0 > > in smb.conf > > > > But netstat -tulpn shows 0.0.0.0 binded address: > > tcp 0 0 192.168.0.254:139 0.0.0.0:* > > LISTEN smbd > > udp 0 0 192.168.0.255:137 0.0.0.0:* > > nmbd > > udp 0 0 192.168.0.254:137 0.0.0.0:* > > nmbd > > *ud...

Sonny Rajagopalan wrote: > I receive a TCP ack back from that port (5060; owned by Asterisk) > --confirmed by wireshark on the Asterisk server. That's from Wireshark, but what is Asterisk seeing? If Asterisk doesn't show the connection or the traffic then something else is up (firewall, etc). Try to isolate things further, start from Asterisk itself. -- Joshua Colp Digium, Inc.

...ally high == on DC2 == showrepl: ==== INBOUND NEIGHBORS ==== ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610723, 'NT_STATUS_RPC_PROTOCOL_ERROR') cpu load is high DNS queries for my samba.company.com no longer work, but samba is listening on port 53, confirmed by netstat -tulpn == on DC1 == Seems to be in even worse shape: root at dc1:~# samba-tool drs showrepl s4_tevent: EPOLL_CTL_DEL EBADF for fde[0x11a6020] mpx_fde[(nil)] fd[8] - disabling ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to dc1.samba.company.com failed - drsException: DRS...

...ve_hosts: Attempting host lookup for name localhost<0x20> Connecting to ::1 at port 445 Connecting to ::1 at port 139 Connecting to 127.0.0.1 at port 445 Connecting to 127.0.0.1 at port 139 Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED) dnl at storestone:~$ sudo netstat -tulpn | egrep "53|88|135|137|138|139|389|445|464|636" tcp 0 0 0.0.0.0:464 0.0.0.0:* LISTEN 2255/kadmind tcp 0 0 0.0.0.0:48336 0.0.0.0:* LISTEN 1536/rpc.statd tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 15607/samba tcp6 0...

Sonny Rajagopalan wrote: > Is there a specific place where I can set logger to log incoming TCP > segments from L4? > > $ netstat -tulpn | grep asterisk | grep LISTEN: > > tcp 0 0 0.0.0.0:8088 <http://0.0.0.0:8088> > 0.0.0.0:* LISTEN 10313/asterisk > tcp 0 0 0.0.0.0:5060 <http://0.0.0.0:5060> > 0.0.0.0:* LISTEN 10313/asterisk > tcp...

...issue the command "systemctl reload sshd.service" I get the following error: "Unit sshd.service cannot be reloaded because it is inactive." It is obviously still running because I am connected over ssh to the machine and netstat shows it is listening. (vnewman pts3) # netstat -tulpn | grep ssh tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 29249/sshd tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 3012/sshd: root at pts (vnewman pts3) # If I reboot the machine, then everything is OK. Has anyone seen this behavi...

...<listen-socket> entry for SSL... but Icecast > > doesn't seem to want to listen on that port when the service comes up. > > Any idea why that might be? > > > Do you mean with different port than 8443, by exemple 8765 ?. If so, what is > the output of: > netstat -tulpn | grep ':8765' Yeah... I’m just trying 8443 ... and netstat shows nada for 8443 ... very strange.

...hat port when the service > > > > comes up. > > > > Any idea why that might be? > > > > > > > > > > Do you mean with different port than 8443, by exemple 8765 ?. If > > > so, what is > > > the output of: > > > netstat -tulpn | grep ':8765' > > > > Yeah... I’m just trying 8443 ... and netstat shows nada for 8443 ... > > very strange. > > > After restart the Icecast2 server ? ... Yeah... after the restart... the port doesn't appear. Does icecast2 play well with selinux?

Hello, ???? Having issues with a DC not responding to DNS requests. OS is Ubuntu 18.04.4 LTS. Samba version 4.12.2 compiled from source. Checking to see what is listening on port 53 reports; @soldc4:~# netstat -tulpn | grep ":53" tcp??????? 0????? 0 127.0.0.53:53 0.0.0.0:*?????????????? LISTEN????? 2935/systemd-resolv tcp6?????? 0????? 0 :::53 :::*??????????????????? LISTEN????? 2694/samba: task[dn udp??????? 0????? 0 127.0.0.53:53 0.0.0.0:*?????????????????????????? 2935/systemd-resolv udp6??????...

Hai Gaetan,   Can you post the output this this command : netstat -plaunt | egrep "ntp|bind|named|samba|?mbd" and iptables -S     @Rowland, https://wiki.samba.org/index.php/Samba_AD_DC_Port_Usage  might need a smal change.  test as followed The wiki line:  netstat -tulpn | egrep "samba|smbd|nmbd|winbind"  Now test my line and see the changes. this catches everything a DC might be running. netstat -plaunt | egrep "ntp|bind|named|samba|?mbd"     Greetz,   Louis   Van: Gaetan SLONGO [mailto:gslongo at it-optics.com] Verzonden: donderdag 31 mei...

....2015 um 14:55 schrieb CpServiceSPb .: >>> > Here are 3 faces at Ubuntu: lo, lan and wan. >>> > There are lines: >>> > bind interfaces only = yes >>> > interfaces = lo lan0 >>> > in smb.conf >>> > >>> > But netstat -tulpn shows 0.0.0.0 binded address: >>> > tcp 0 0 192.168.0.254:139 0.0.0.0:* >>> > LISTEN smbd >>> > udp 0 0 192.168.0.255:137 0.0.0.0:* >>> > nmbd >>> > udp 0 0 192.168.0.254:137...

Hai eveyone.   I know about the dns "things" in the past. DNS Islanding problems etc. This one is a bit hijacking the subject : “Horrible BIND9_DLZ DNS breakage after DC replaced and samba-tool domain demote --remove-other-dead-server”     I would like to suggest a smale change in how we suggest to setup samba ADDC dns things, and i do think this help in the setup of the AD

Morning all, I set up IceCast several years ago on centos 6. seemed easy, now I am trying to install it on Centos 7. For the life of me, I cant do it, I have read several STEP by steps on how to configure, but I am pounding my head against the wall, I am a Windows IT guy, thus I am looking for a step by step detail way of doing it. All the examples I find, fail at some point or another. Any

...body 3650 0.0 2.1 5660 5656 ? SL 22:03 0:00 heartbeat: read: bcast eth0 root 3653 0.0 0.2 61180 736 pts/1 S+ 22:04 0:00 grep heartbeat And verified that the box is listening on port 694 (the port that I have set for heartbeat): [root at VIRTCENT01:~]#netstat -tulpn | grep heartbeat udp 0 0 0.0.0.0:694 0.0.0.0:* 3649/heartbeat: wri udp 0 0 0.0.0.0:50550 0.0.0.0:* 3649/heartbeat: wri However although I have the port enabled in iptables: -A RH-Firewall-1-INPUT -m state --st...

...: PORT STATE SERVICE 443/tcp open https And the port 443 is being listened to.. [root at VIRTCENT02:~] #lsof -i :443 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME haproxy 1763 haproxy 6u IPv4 7586 TCP VIRTUAL.example.com:https (LISTEN) [root at VIRTCENT01:~] #netstat -tulpn | grep 443 tcp 0 0 192.168.1.200:443 0.0.0.0:* LISTEN 1752/haproxy But a page will not render in a web page. Unable to connect Firefox can't establish a connection to the server at virtual.example.com. And there is no activity i...

Hello, for many years i used an mailserver with dovecot V1 very satisfied! http://mailserver.decotrain.de/ One of the reasons to use dovecot was a simply configuration. Dovecot was the best choice for IMAP for me! Now i updated the server to Debian testing with dovecot 2.1.7. It's not possible for me to get a running authentication for virtual mail users! I recently found this mailing and