Advertisements

smbclient receiving error message: protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED

I have a Red Hat Enterprise Linux 7.5 server that is not connecting to a Windows share

root@linux:~ # cat /etc/*release
NAME=”Red Hat Enterprise Linux Server”
VERSION=”7.5 (Maipo)”
ID=”rhel”
ID_LIKE=”fedora”
VARIANT=”Server”
VARIANT_ID=”server”
VERSION_ID=”7.5″
PRETTY_NAME=”Red Hat Enterprise Linux”
ANSI_COLOR=”0;31″
CPE_NAME=”cpe:/o:redhat:enterprise_linux:7.5:GA:server”
HOME_URL=”https://www.redhat.com/”
BUG_REPORT_URL=”https://bugzilla.redhat.com/”

REDHAT_BUGZILLA_PRODUCT=”Red Hat Enterprise Linux 7″
REDHAT_BUGZILLA_PRODUCT_VERSION=7.5
REDHAT_SUPPORT_PRODUCT=”Red Hat Enterprise Linux”
REDHAT_SUPPORT_PRODUCT_VERSION=”7.5″
Red Hat Enterprise Linux Server release 7.5 (Maipo)
Red Hat Enterprise Linux Server release 7.5 (Maipo)

samba rebased to version 4.6.2

To improve security, the NT LAN manager version 1 (NTLMv1) protocol is now disabled by default. If you require the insecure NTLMv1 protocol, set the ntlm auth parameter in the /etc/samba/smb.conf file to yes.

The storage was upgraded so my RHEL 7.5 server is the client trying to connect to the Windows share. It is showing the message protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED

root@linux:~ # smbclient //storageserver/PUBLICO -U “setaoffice/username%PASSWORD” -c ‘prompt; cd CC_EFC_Inbound/Logs; mget *.log’
protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED

To solve the problem, I had to add -m SMB2 or -m SMB3 to the smbclient

root@linux:~ # smbclient //storageserver/PUBLICO -U “setaoffice/username%PASSWORD” -m SMB2 -c ‘prompt; cd CC_EFC_Inbound/Logs; mget *.log’
Kinit for username@SETAOFFICE to access storageserver failed: Cannot find KDC for requested realm
session setup failed: NT_STATUS_WRONG_PASSWORD

Advertisements

Control-M: The SMTP server did not respond in a timely manner. Please check the Port Number and the SMTP Server (Relay) Name.

Control-M application

Simple Mail Transfer Protocol Parameters Menu
———————————————-

Select one of the following options:

1 – SMTP Server (Relay) Name : mailBR.setaoffice.com
2 – Sender Email : controlm@setaoffice.com
3 – Port Number : 25
4 – Sender Friendly Name : ControlM – Production
5 – Reply-To Email : productioncontrolm@setaoffice.com
6 – Test SMTP Settings

s – Save Parameters

q – Quit

Enter option number —> [q]:6

Testing SMTP Settings…

The SMTP server did not respond in a timely manner.
Please check the Port Number and the SMTP Server (Relay) Name.

Press Enter to continue

Host mailBR.setaoffice.com was being resolved to a different IP address because it was in /etc/hosts file of the server

SAP return code XXX

R49 Basis System: Communication error, CPIC return code 020, SAP return code 223
223 – Network read error

R49 Basis System: Communication error, CPIC return code 017, SAP return code 236
236 – No connection to the gateway

R49 Basis System: Communication error, CPIC return code 020, SAP return code 456
456 – Timeout when establishing connection

R49 Basis System: Communication error, CPIC return code 019, SAP return code 728
728 – Conversation ID not found

RHEL 6 server receiving error mounting CIFS (Windows) share – mount error(112): Host is down

When mounting a CIFS (Windows) share, I’m receiving an error saying the host is down

root@linux:~ # mount /mnt/test
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

This is the share in /etc/fstab

root@linux:~ # cat /etc/fstab
//10.0.0.1/CIFS$ /mnt/test cifs _netdev,user=appuser,pass=1234,uid=21376,gid=252,file_mode=0775,dir_mode=0775,domain=windows

I’m running a RHEL 6.9 server

root@linux:~ # cat /etc/*release
LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Red Hat Enterprise Linux Server release 6.9 (Santiago)
Red Hat Enterprise Linux Server release 6.9 (Santiago)

This problem happened because the storage was upgraded and it is using SMB2. You need to have at least kernel 3.7 to have support for SMB2
SMB shares fail to mount with the SMB2 protocol

insserv: warning: script missing LSB tags and overrides | insserv: Stopping depends on and therefore on system facility `$all’ which can not be true!

When trying to enable xinetd to start on boot, insserv was throwing error message and not enabling it.

root@linux:~ # chkconfig –list xinetd
xinetd 0:off 1:off 2:off 3:off 4:off 5:off 6:off

root@linux:~ # chkconfig xinetd on
insserv: warning: script ‘K02OVTrcSrv’ missing LSB tags and overrides
insserv: warning: script ‘OVTrcSrv’ missing LSB tags and overrides
insserv: warning: script ‘esmrc’ missing LSB tags and overrides
insserv: Default-Start undefined, assuming default start runlevel(s) for script `esmrc’
insserv: There is a loop between service OVCtrl and esmrc if stopped
insserv: loop involving service esmrc at depth 2
insserv: loop involving service OVCtrl at depth 1
insserv: Stopping esmrc depends on OVCtrl and therefore on system facility `$all’ which can not be true!
insserv: exiting now without changing boot order!
/sbin/insserv failed, exit code 1

https://unix.stackexchange.com/questions/289667/unable-to-install-anything-using-apt-get-because-of-insserv

First of all, the problem is that you are stuck at the boot sequencing.

The boot sequencing method is decided during installation or upgrades. If there are no loops in the dependencies declared by the LSB headers of all installed init.d scripts and no obsolete scripts, the system is converted to dependency based boot sequence.

We have to check for

1. Loop in dependencies: Occurs when >
• There are missing LSB tags in some scripts or error in LSB tags like missing Required-Start: or Required-Stop: tags

• Some scripts depend on other scripts which depend on the system facility $all which cannot be true. Because the scripts depending on $all is loaded last at starting. Since it loads last, nothing can depend on it. Hence, messes up the dependency based boot sequence.

2. Obsolete scripts: Occur when

• Some packages being upgraded to newer versions which may not use a script in /etc/init.d/ and the maintainer may have missed the code to remove the old script. Not our mistake.

I edited file /etc/init.d/esmrc and added a LSB header after #!/bin/sh

root@linux:~ # vi /etc/init.d/esmrc
#!/bin/sh
### BEGIN INIT INFO
# Provides: esmrc
# Required-Start:
# Should-Start: $remote_fs $network $syslog
# Required-Stop:
# Should-Stop: $remote_fs $network $syslog
# Default-Start: 2 3 5
# Default-Stop: 0 1 4 6
# Short-Description : Enterprise Security Manager
# Description : Enterprise Security Manager (ESM) allows a computer to be
# monitored for compliance with security policy.
### END INIT INFO
#
# For HP-UX version 10.xx platforms the above line must be changed to
# ‘/sbin/sh’ by esmsetup and by the tune-up pack.
#
#*************************************************************************
###############################################################################
# Enterprise Security Manager (r)
###############################################################################

Linux LVM: File-based locking initialisation failed

Running a lvm command and you encounter the message File-based locking initialisation failed means that the filesystem is read-only

root@linux:~ # pvs
File-based locking initialisation failed

The directory /var/lock/lvm must be writable. So you have a /var or / filesystem read-only.

You can try to remount it as read-write or reboot the server

mount -o remount,rw /
reboot -d -n -f

Source: Running an LVM command returns “File-based locking initialisation failed” or “Locking type 1 initialisation failed”

Linux – shutdown: Unable to shutdown system

Booted the system adding init=/bin/bash at the end of the kernel line.

Entered Rescue system

Now when trying to restart the system, it appears the message shutdown: Unable to shutdown system

bash-4.1# shutdown -r now
shutdown: Unable to shutdown system
bash-4.1# reboot
shutdown: Unable to shutdown system

To reboot the server, you need to use the following command

bash-4.1# reboot -n -d -f

After update to SUSE Linux 11 SP4, it stuck on a black screen written grub>

After updating a Suse Linux 11 to SP4, I’ve booted the server and it was stuck on a black screen written grub>

To solve this problem it is needed to:
Boot using a Suse Linux 11 DVD
Select Rescue System
Choose a language
Login as root

# grub
find /boot/grub/stage1
root (hd0,0) -> type according to your system, found using find /boot/grub/stage1
setup (hd0)
quit

Reboot the server
reboot -d -n -f

NFS Stale file handle

My NFS client is linux and I’m having problems

root@linux:~ # cd /usr/sap/trans/SOLMAN
-bash: cd: /usr/sap/trans/SOLMAN: Stale file handle

Exporting /export/usr/sap/trans/SOLMAN to linux

root@nfsserver:~ # exportfs -o rw,no_root_squash,sync linux:/export/usr/sap/trans/SOLMAN

root@nfsserver:~ # showmount -e
Export list for nfsserver:
/export/usr/sap/trans/SOLMAN linux,linux01,linux02
/export/sapmnt/ND1/profile nfsserver
/export/sapmnt/ND1/global nfsserver
/export/sapmnt/ND1/exe nfsserver

Removing export to linux and then manually reexporting it again

root@nfsserver:~ # exportfs -u linux:/export/usr/sap/trans/SOLMAN
root@nfsserver:~ # exportfs -o rw,no_root_squash,sync linux:/export/usr/sap/trans/SOLMAN

ethtool eth0: 0x00000014 (20) link ifdown

Running UXMONbroker with bondmon module is complaining about eth0 interface

root@linux:~ # /var/opt/OV/bin/instrumentation/UXMONbroker -check bondmon
Tue Oct 16 09:39:45 2018 : INFO : UXMONbondmon is running now, pid=12124
Tue Oct 16 09:39:45 2018 : Major: slave eth0 of bonding device bond0 unknown
mv: `/dev/null’ and `/dev/null’ are the same file
Tue Oct 16 09:39:45 2018 : INFO : UXMONbondmon end, pid=12124

Checking eth0 status

root@linux:~ # ethtool eth0
Settings for eth0:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseKX/Full
10000baseKR/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: No
Advertised link modes: 1000baseKX/Full
10000baseKR/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: No
Speed: 10000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000014 (20)
link ifdown
Link detected: yes

Tried to stop and start the network interface

root@linux:~ # ifdown eth0
root@linux:~ # ifup eth0

Checking eth0 the link ifdown status is still there

root@linux:~ # ethtool eth0
Settings for eth0:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseKX/Full
10000baseKR/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: No
Advertised link modes: 1000baseKX/Full
10000baseKR/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: No
Speed: 10000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000014 (20)
link ifdown
Link detected: yes

Running UXMONbroker with bondmon module

root@linux:~ # /var/opt/OV/bin/instrumentation/UXMONbroker -check bondmon
Tue Oct 16 09:39:45 2018 : INFO : UXMONbondmon is running now, pid=12124
Tue Oct 16 09:39:45 2018 : Major: slave eth0 of bonding device bond0 unknown
mv: `/dev/null’ and `/dev/null’ are the same file
Tue Oct 16 09:39:45 2018 : INFO : UXMONbondmon end, pid=12124

Connected to console and restarted network services

root@linux:~ # service network restart

After the restart, running UXMONbroker with bondmon module doesn’t complain anymore

root@linux:~ # /var/opt/OV/bin/instrumentation/UXMONbroker -check bondmon
Tue Oct 16 10:18:06 2018 : INFO : UXMONbondmon is running now, pid=18048
mv: `/dev/null’ and `/dev/null’ are the same file
Tue Oct 16 10:18:06 2018 : INFO : UXMONbondmon end, pid=18048

%d bloggers like this: