Working Version of Samba & Error
Kunal Matharu
My installation of Samaba 3.5.6 is still a huge struggle.
<==The Struggle ==>
Thank you for all the help so far, my main goal is to stay on the
default LAN which is 192.168.0.200 and not the maintenance LAN.
With my smb.conf interfaces set to 192.168.0.200 and running both
nmbd and smbd my output results to:
<====>MY EMSA DISPLAYS: <====>
Status: STARTED
PPID............ ( 0,380) BPID................... ( 1,355)
Proto State Laddr Lport Faddr Fport
SendQ RecvQ
TCP LISTEN 0.0.0.0 139 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 445 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 627 0.0.0.0 *
0 0
TCP LISTEN 192.168.0.202 80 0.0.0.0 *
0 0
TCP LISTEN 192.168.0.200 80 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 9991 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 9023 0.0.0.0 *
0 0
TCP ESTAB 192.168.0.200 9023 24.202.3.71 60324
0 0
TCP ESTAB 192.168.0.200 9023 24.202.3.71 60323
0 0
TCP ESTAB 192.168.0.200 9023 24.202.3.71 60322
0 0
TCP ESTAB 192.168.0.200 9023 24.202.3.71 60321
0 0
TCP ESTAB 192.168.0.200 9023 192.168.10.200 1086
0 0
TCP ESTAB 192.168.0.200 9023 192.168.10.200 1084
0 0
TCP ESTAB 192.168.0.200 9023 192.168.10.200 1078
0 0
TCP ESTAB 192.168.0.200 9023 192.168.10.200 1076
0 0
TCP ESTAB 192.168.0.200 9023 192.168.10.200 1070
0 0
TCP ESTAB 192.168.0.200 9023 192.168.10.200 1068
0 0
TCP ESTAB 192.168.0.200 9991 66.131.129.138 2622
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCPIP Status PROCESS \ISOFT.$ZTC0
Status: STARTED
PPID............ ( 0,380) BPID................... ( 1,355)
Proto State Laddr Lport Faddr Fport
SendQ RecvQ
TCP LISTEN 0.0.0.0 111 0.0.0.0 *
0 0
TCP LISTEN 192.168.0.202 80 0.0.0.0 *
0 0
TCP LISTEN 192.168.0.200 80 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 ftp 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 finger 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 echo 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 telnet 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 9002 0.0.0.0 *
0 0
TCP ESTAB 192.168.0.200 telnet 192.168.10.199 55751
2254 0
TCP ESTAB 192.168.0.200 telnet 192.168.10.199 55591
0 0
TCP ESTAB 192.168.0.200 telnet 192.168.10.199 51221
0 0
TCP ESTAB 192.168.0.200 telnet 192.168.10.199 51215
0 0
TCP ESTAB 192.168.0.200 telnet 192.168.10.200 2043
0 0
TCP ESTAB 192.168.0.200 telnet 192.168.10.200 1082
0 0
TCP ESTAB 192.168.0.200 telnet 192.168.10.200 1080
0 0
TCP ESTAB 192.168.0.200 telnet 192.168.10.200 1074
0 0
TCP ESTAB 192.168.0.200 telnet 192.168.10.200 1072
0 0
TCP ESTAB 192.168.0.200 telnet 192.168.10.200 1066
0 0
TCP ESTAB 192.168.0.200 ftp 66.131.252.118 55466
0 0
UDP 0.0.0.0 111 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
TCP CLOSED 0.0.0.0 * 0.0.0.0 *
0 0
Total Errors = 0 Total Warnings = 0
<====>WITH MY NMBD LOG CONSISITING OF: <====>
[2010/11/23 15:07:38, 0] /usr/local/Floss/samba-3.5.6/source3/nmbd/
nmbd.c:857(main)
nmbd version 3.5.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2010/11/23 15:07:38.301567, 0] /usr/local/Floss/samba-3.5.6/
source3/
nmbd/nmbd.c:885(main)
standard input is not a socket, assuming -D option
[2010/11/23 15:07:38.553387, 0] /usr/local/Floss/samba-3.5.6/
source3/
lib/util_sock.c:875(open_socket_in)
bind failed on port 137 socket_addr = 192.168.0.255.
Error = Network is unreachable
[2010/11/23 15:07:38.553843, 0] /usr/local/Floss/samba-3.5.6/
source3/
nmbd/nmbd_subnetdb.c:118(make_subnet)
nmbd_subnetdb:make_subnet()
Failed to open nmb bcast socket on interface 192.168.0.255 for
port 137. Error was Network is unreachable
[2010/11/23 15:07:38.554240, 0] /usr/local/Floss/samba-3.5.6/
source3/
nmbd/nmbd.c:963(main)
ERROR: Failed when creating subnet lists. Exiting.
<====>AND MY SMBD CONSISTING OF: <====>
[2010/11/23 15:07:37, 0] /usr/local/Floss/samba-3.5.6/source3/smbd/
server.c:1119(main)
smbd version 3.5.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2010/11/23 15:07:38.140612, 0] /usr/local/Floss/samba-3.5.6/
source3/
smbd/server.c:1165(main)
standard input is not a socket, assuming -D option
[2010/11/23 15:07:38.770876, 0] /usr/local/Floss/samba-3.5.6/
source3/
lib/util_sock.c:839(open_socket_in)
open_socket_in(): socket() call failed: Address family not
supported
[2010/11/23 15:07:38.783897, 0] /usr/local/Floss/samba-3.5.6/
source3/
smbd/server.c:499(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address family not supported
[2010/11/23 15:07:38.792441, 0] /usr/local/Floss/samba-3.5.6/
source3/
lib/util_sock.c:839(open_socket_in)
open_socket_in(): socket() call failed: Address family not
supported
[2010/11/23 15:07:38.792729, 0] /usr/local/Floss/samba-3.5.6/
source3/
smbd/server.c:499(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address family not supported
<=>However when I change my setting to the maintenance LAN with my
interfaces set to 192.231.36.10 i have different results: <=>
<====>MY EMSA DISPLAYS: <====>
Status: STARTED
PPID............ ( 0,328) BPID................... ( 1,325)
Proto State Laddr Lport Faddr Fport
SendQ RecvQ
TCP LISTEN 0.0.0.0 139 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 445 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 22 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 5988 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 9991 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 9990 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 telnet 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 ftp 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 finger 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 echo 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 9002 0.0.0.0 *
0 0
UDP 192.231.36.255 138 0.0.0.0 *
0 0
UDP 192.231.36.10 138 0.0.0.0 *
0 0
UDP 192.231.36.255 137 0.0.0.0 *
0 0
UDP 192.231.36.10 137 0.0.0.0 *
0 0
UDP 0.0.0.0 138 0.0.0.0 *
0 0
UDP 0.0.0.0 137 0.0.0.0 *
0 0
UDP 0.0.0.0 162 0.0.0.0 *
0 0
Total Errors = 0 Total Warnings = 0
<====>WITH MY NMBD LOG CONSISITING OF: <====>
[2010/11/23 15:20:33, 0] /usr/local/Floss/samba-3.5.6/source3/nmbd/
nmbd.c:857(main)
nmbd version 3.5.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2010/11/23 15:20:33.568113, 0] /usr/local/Floss/samba-3.5.6/
source3/
nmbd/nmbd.c:885(main)
standard input is not a socket, assuming -D option
[2010/11/23 15:20:56.143982, 0] /usr/local/Floss/samba-3.5.6/
source3/
nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
***** Samba name server OSMLANX is now a local master browser for
workgroup WORKGROUP on subnet 192.231.36.10 *****
<====>AND MY SMBD CONSISTING OF: <====>
[2010/11/23 15:20:33, 0] /usr/local/Floss/samba-3.5.6/source3/smbd/
server.c:1119(main)
smbd version 3.5.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2010/11/23 15:20:33.381753, 0] /usr/local/Floss/samba-3.5.6/
source3/
smbd/server.c:1165(main)
standard input is not a socket, assuming -D option
[2010/11/23 15:20:33.911577, 0] /usr/local/Floss/samba-3.5.6/
source3/
lib/util_sock.c:839(open_socket_in)
open_socket_in(): socket() call failed: Protocol not supported
[2010/11/23 15:20:33.924377, 0] /usr/local/Floss/samba-3.5.6/
source3/
smbd/server.c:499(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Protocol not supported
[2010/11/23 15:20:33.935664, 0] /usr/local/Floss/samba-3.5.6/
source3/
lib/util_sock.c:839(open_socket_in)
open_socket_in(): socket() call failed: Protocol not supported
[2010/11/23 15:20:33.935961, 0] /usr/local/Floss/samba-3.5.6/
source3/
smbd/server.c:499(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Protocol not supported
Here in the maintenance LAN the nmbd works fine however the errors in
the smbd for both default and maintenance LAN are consistent. Any
idea how to work around these errors? I have checked the source code
but not much help.
Joachim Schmitz
> I was wondering if anyone has Samba up and running and what version?
> My installation of Samaba 3.5.6 is still a huge struggle.
I replied to an an earlier message, 2 days ago, but that didn't make it to
the news servers, not sure why?
> <==The Struggle ==>
>
> Thank you for all the help so far, my main goal is to stay on the
> default LAN which is 192.168.0.200 and not the maintenance LAN.
> With my smb.conf interfaces set to 192.168.0.200 and running both
> nmbd and smbd my output results to:
>
> <====>MY EMSA DISPLAYS: <====>
> Status: STARTED
> PPID............ ( 0,380) BPID................... ( 1,355)
> Proto State Laddr Lport Faddr Fport
> SendQ RecvQ
> TCP LISTEN 0.0.0.0 139 0.0.0.0 *
> 0 0
> TCP LISTEN 0.0.0.0 445 0.0.0.0 *
> 0 0
These are "NETBIOS Session Services" and "SMB over TCP"
use -D option to avoid thie message. Or start via inetd (but, due to a bug
in inetd, triggered by samba-3.5.6, this is not a good idea, here the clean
exit of an smbd also kills inetd, root cause is understood and a fix is in
the works).
> [2010/11/23 15:07:38.553387, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> lib/util_sock.c:875(open_socket_in)
> bind failed on port 137 socket_addr = 192.168.0.255.
> Error = Network is unreachable
> [2010/11/23 15:07:38.553843, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> nmbd/nmbd_subnetdb.c:118(make_subnet)
> nmbd_subnetdb:make_subnet()
> Failed to open nmb bcast socket on interface 192.168.0.255 for
> port 137. Error was Network is unreachable
Here it fails to talk to broadcast. Not sure why.
How is $TCP0 setup?
What is it's real netmask?
Ist it TCP6SAM ot TCPIP?
> [2010/11/23 15:07:38.554240, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> nmbd/nmbd.c:963(main)
> ERROR: Failed when creating subnet lists. Exiting.
>
> <====>AND MY SMBD CONSISTING OF: <====>
>
> [2010/11/23 15:07:37, 0] /usr/local/Floss/samba-3.5.6/source3/smbd/
> server.c:1119(main)
> smbd version 3.5.6 started.
> Copyright Andrew Tridgell and the Samba Team 1992-2010
> [2010/11/23 15:07:38.140612, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> smbd/server.c:1165(main)
> standard input is not a socket, assuming -D option
See above
> [2010/11/23 15:07:38.770876, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> lib/util_sock.c:839(open_socket_in)
> open_socket_in(): socket() call failed: Address family not
> supported
> [2010/11/23 15:07:38.783897, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> smbd/server.c:499(smbd_open_one_socket)
> smbd_open_once_socket: open_socket_in: Address family not supported
> [2010/11/23 15:07:38.792441, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> lib/util_sock.c:839(open_socket_in)
> open_socket_in(): socket() call failed: Address family not
> supported
> [2010/11/23 15:07:38.792729, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> smbd/server.c:499(smbd_open_one_socket)
> smbd_open_once_socket: open_socket_in: Address family not supported
Does this stack use IPv6?
> <=>However when I change my setting to the maintenance LAN with my
> interfaces set to 192.231.36.10 i have different results: <=>
>
> <====>MY EMSA DISPLAYS: <====>
>
> Status: STARTED
> PPID............ ( 0,328) BPID................... ( 1,325)
> Proto State Laddr Lport Faddr Fport
> SendQ RecvQ
> TCP LISTEN 0.0.0.0 139 0.0.0.0 *
> 0 0
> TCP LISTEN 0.0.0.0 445 0.0.0.0 *
> 0 0
See above
I guess in this stack inetd runs and opens all these Samba ports?
Try to be consistent and either use inetd to start Samba on both stacks or
on neither (and for 3.5.6 and 3.0.37 I'd recomend the later, and due to the
inetd bug mentioned earlier it might be your only choice anyway)
Only Swat needs to be run via inetd, and in the unsercure demo mode (-a
option), so it may be a good idea to run it on the maintenance LAN only,
where not everyone has access.
> UDP 0.0.0.0 162 0.0.0.0 *
> 0 0
> Total Errors = 0 Total Warnings = 0
>
> <====>WITH MY NMBD LOG CONSISITING OF: <====>
>
> [2010/11/23 15:20:33, 0] /usr/local/Floss/samba-3.5.6/source3/nmbd/
> nmbd.c:857(main)
> nmbd version 3.5.6 started.
> Copyright Andrew Tridgell and the Samba Team 1992-2010
> [2010/11/23 15:20:33.568113, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> nmbd/nmbd.c:885(main)
> standard input is not a socket, assuming -D option
see above, but aren't you using inetd to start samba on this stack?
> [2010/11/23 15:20:56.143982, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
> ***** Samba name server OSMLANX is now a local master browser for
> workgroup WORKGROUP on subnet 192.231.36.10 *****
Hmm, maybe not. Here apparentls nmbd has no problem with the broadcast.
Investigate into the differences in the setup of the two TCP/IP stacks
> <====>AND MY SMBD CONSISTING OF: <====>
>
> [2010/11/23 15:20:33, 0] /usr/local/Floss/samba-3.5.6/source3/smbd/
> server.c:1119(main)
> smbd version 3.5.6 started.
> Copyright Andrew Tridgell and the Samba Team 1992-2010
> [2010/11/23 15:20:33.381753, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> smbd/server.c:1165(main)
> standard input is not a socket, assuming -D option
see above
> [2010/11/23 15:20:33.911577, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> lib/util_sock.c:839(open_socket_in)
> open_socket_in(): socket() call failed: Protocol not supported
> [2010/11/23 15:20:33.924377, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> smbd/server.c:499(smbd_open_one_socket)
> smbd_open_once_socket: open_socket_in: Protocol not supported
> [2010/11/23 15:20:33.935664, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> lib/util_sock.c:839(open_socket_in)
> open_socket_in(): socket() call failed: Protocol not supported
> [2010/11/23 15:20:33.935961, 0] /usr/local/Floss/samba-3.5.6/
> source3/
> smbd/server.c:499(smbd_open_one_socket)
> smbd_open_once_socket: open_socket_in: Protocol not supported
Hmm, do you have an /etc/protocols (as a symbolic link to
/G/system/ztcpip/protocol)?
> Here in the maintenance LAN the nmbd works fine however the errors in
> the smbd for both default and maintenance LAN are consistent. Any
No they are not really consistent, "Address family not supported" vs.
"Protocol not supported" are different.
> idea how to work around these errors? I have checked the source code
> but not much help.
Bye, Jojo
wbreidbach
wrote:
>
> Erfahren Sie mehr »- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -
I have Samba running on 2 interfaces, so 2 SMBD processes are running.
One interface is old IPV4, the other one is using IPV6, but the subnet
is running in INET (IPV4) mode.
I am sharing the /home, the /G and the /tmp directories. There are
still problems with Guardian editfiles (Code 101), but everything else
is running fine.
I have MS-word, -Excel and html documents on the NonStop (as OSS-
files) and it just behaves like a Windows-machine.
I do not have an NMBD running and I have started SMBD directly. Using
inetd I experienced some problems with inetd dying unexpectedly.
The system is an NS1202 running H06.20.
Joachim Schmitz
<snip>
> Using
> inetd I experienced some problems with inetd dying unexpectedly.
Yes, this is a bug in inetd, root cause understood and fix in the works
> The system is an NS1202 running H06.20.
And likely to be released with H06.22/J06.11, together with the official HP
supported Samba.
Bye, Jojo
wbreidbach
wrote:
Just to make it a bit more easy, here is the start-sequence for smbc
running on $ztcp0:
export SOCKET_TRANSPORT_NAME=\$ZTCP0
add_define =tcpip^process^name class=map file=\$ztcp0
SAMBA=/usr/local/samba3.5/sbin/smbd
CONFIG=/usr/local/samba3.5/lib/smb_ztcp0.conf
RUN="run -jobid=0 -term=/G/zhome -cpu=0"
echo "Starting Samba ..."
$RUN $SAMBA -s $CONFIG
And this is the Samba config-file /usr/local/samba3.5/lib/
smb_ztcp0.conf
interfaces = 192.231.250.10/255.255.0.0
encrypt passwords = yes
debug level = 0
[root]
path = /
read only = yes
[tmp]
path = /tmp
read only = no
[home]
path = /home
read only = no
[guardian]
path = /G
read only = no
This starts Samba on the servicenet. Please note that the adresss and
the subnetmask in the configfile have to match those of the appropiate
subnet.
Joachim Schmitz
And to keep these files consistent in their common pargs, you could use the
'include' directive, e.g.:
$ cat /usr/local/samba3.5/lib/smb_ztcp0.conf
[global]
interfaces = 192.231.250.10/16
guest ok = yes
include /usr/local/samba3.5/lib/smb-common.conf
$ cat /usr/local/samba3.5/lib/smb_ztc0.conf
[global]
interfaces = 16.58.0.61/21
guest ok = no
include /usr/local/samba3.5/lib/smb-common.conf
$ cat /usr/local/samba3.5/lib/smb-common.conf
[global]
Kunal Matharu
Thank for the suggestions, but where does the -D option be placed to
avoid those errors? Also i am not using the inetd file i am running
the smbd and nmbd as standalone. Also i have placed the following
suggestions as in order with my ip
export SOCKET_TRANSPORT_NAME=\$ZTCP0
add_define =tcpip^process^name class=map file=\$ztcp0
SAMBA=/usr/local/samba3.5/sbin/smbd
CONFIG=/usr/local/samba3.5/lib/smb.conf
RUN="run -jobid=0 -term=/G/zhome -cpu=0"
echo "Starting Samba ..."
$RUN $SAMBA -s $CONFIG
And this is the Samba config-file /usr/local/samba3.5/lib/
smb_ztcp0.conf
interfaces = 192.231.36.10/255.255.0.0
encrypt passwords = yes
debug level = 0
[root]
path = /
read only = yes
[tmp]
path = /tmp
read only = no
[home]
path = /home
read only = no
[guardian]
path = /G
read only = no
However i get these errors :
[2010/11/26 16:31:45, 0] /usr/local/Floss/samba-3.5.6/source3/smbd/
server.c:1119(main)
smbd version 3.5.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2010/11/26 16:31:45.271728, 0] /usr/local/Floss/samba-3.5.6/source3/
smbd/server.c:1165(main)
standard input is not a socket, assuming -D option
[2010/11/26 16:31:45.662472, 0] /usr/local/Floss/samba-3.5.6/source3/
lib/util_sock.c:839(open_socket_in)
open_socket_in(): socket() call failed: Protocol not supported
[2010/11/26 16:31:45.689838, 0] /usr/local/Floss/samba-3.5.6/source3/
smbd/server.c:499(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Protocol not supported
[2010/11/26 16:31:45.710732, 0] /usr/local/Floss/samba-3.5.6/source3/
lib/util_sock.c:839(open_socket_in)
open_socket_in(): socket() call failed: Protocol not supported
[2010/11/26 16:31:45.711044, 0] /usr/local/Floss/samba-3.5.6/source3/
Joachim Schmitz
As part of starting smbd
> Also i have placed the following
> suggestions as in order with my ip
>
> export SOCKET_TRANSPORT_NAME=\$ZTCP0
> add_define =tcpip^process^name class=map file=\$ztcp0
> SAMBA=/usr/local/samba3.5/sbin/smbd
> CONFIG=/usr/local/samba3.5/lib/smb.conf
> RUN="run -jobid=0 -term=/G/zhome -cpu=0"
> echo "Starting Samba ..."
> $RUN $SAMBA -s $CONFIG
e.g. here
$RUN $SAMBA -D -s $CONFIG
Are you sure inetd does not runing against $ZTPC0 and that it's indet.conf
does not cotain the entries for smbd and nmbd?
Also as I asked earlier:
Do you have an /etc/protocols (as a symbolic link to
/G/system/ztcpip/protocol)?
Does it contain enteries for ip, tcp, udp, ipv6?
Bye, Jojo
Kunal Matharu
wrote:
Currently in my inetd.conf file everything is commented out so nothing
is starting up through inetd, so therefore smbd and nmbd entries do
not run. Also there is a symbolic link from /etc/protocols to /G/
system/ztcpip/protocol, the following protocols entries are setup to
ip 0 IP # internet protocol, pseudo protocol number
tcp 6 TCP # transmission control protocol
udp 17 UDP # user datagram protocol
ipv6 41 IP # internet protocol for v6
In Investigate into the differences in the setup of the two TCP/IP
stacks, the following ports are missing in the $ZTC0.
TCPIP Detailed Status PROCESS \ISOFT.$ZTCP0
Status: STARTED
PPID............ ( 0,358) BPID................... ( 1,412)
Proto State Laddr Lport Faddr Fport
SendQ RecvQ
TCP LISTEN 0.0.0.0 139 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 445 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 9991 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 5988 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 9990 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 22 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 ftp 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 finger 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 echo 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 9002 0.0.0.0 *
0 0
TCP LISTEN 0.0.0.0 telnet 0.0.0.0 *
0 0
UDP 0.0.0.0 162 0.0.0.0 *
0 0
Thank you for your help once again!
Joachim Schmitz
<snip>
> Currently in my inetd.conf file everything is commented out so nothing
> is starting up through inetd, so therefore smbd and nmbd entries do
> not run.
And you restarted inetd after the last changed to inetd.conf?
> Also there is a symbolic link from /etc/protocols to /G/
> system/ztcpip/protocol, the following protocols entries are setup to
> ip 0 IP # internet protocol, pseudo protocol number
> tcp 6 TCP # transmission control protocol
> udp 17 UDP # user datagram protocol
> ipv6 41 IP # internet protocol for v6
>
> In Investigate into the differences in the setup of the two TCP/IP
> stacks, the following ports are missing in the $ZTC0.
>
> TCPIP Detailed Status PROCESS \ISOFT.$ZTCP0
>
> Status: STARTED
>
> PPID............ ( 0,358) BPID................... ( 1,412)
> Proto State Laddr Lport Faddr Fport
> SendQ RecvQ
> TCP LISTEN 0.0.0.0 139 0.0.0.0 *
> 0 0
> TCP LISTEN 0.0.0.0 445 0.0.0.0 *
> 0 0
These 2 are ports that Samba uses, so it does run here.
> TCP LISTEN 0.0.0.0 9991 0.0.0.0 *
> 0 0
> TCP LISTEN 0.0.0.0 5988 0.0.0.0 *
> 0 0
> TCP LISTEN 0.0.0.0 9990 0.0.0.0 *
> 0 0
> TCP LISTEN 0.0.0.0 22 0.0.0.0 *
> 0 0
SSH, probavly the comforte STN
> TCP LISTEN 0.0.0.0 ftp 0.0.0.0 *
> 0 0
FTPSERRV
> TCP LISTEN 0.0.0.0 finger 0.0.0.0 *
> 0 0
> TCP LISTEN 0.0.0.0 echo 0.0.0.0 *
> 0 0
> TCP LISTEN 0.0.0.0 9002 0.0.0.0 *
> 0 0
> TCP LISTEN 0.0.0.0 telnet 0.0.0.0 *
> 0 0
TELSERV
> UDP 0.0.0.0 162 0.0.0.0 *
> 0 0
>
> Thank you for your help once again!
However this is not what I mean by differences in setup. I mean the
configuration of the 2 TCP/IP stacks, their routes, subnets etc.
Bye, Jojo
Kunal Matharu
We have made a lot of progress through $ztcp0 however we are trying to
lean towards the default LAN $ztc0
TCPIP Info SUBNET \ISOFT.$ZTC0.*
Name Devicename *IPADDRESS TYPE *SUBNETMASK
SuName QIO *R
#SN1 \ISOFT.L1002B 192.168.0.200 ETHERNET
%HFFFFFF00 ON N
#SN1 \ISOFT.L1002B 192.168.0.201 ETHERNET
%HFFFFFF00 ON N
#SN1 \ISOFT.L1002B 192.168.0.202 ETHERNET
%HFFFFFF00 ON N
#LOOP0 127.0.0.1 LOOP-BACK
%HFF000000 OFF N
>TCPIP Info ROUTE \ISOFT.$ZTC0.*
Name Subnet Destination Netmask Gateway Type
Metric
#RT1 #LOOP0 127.0.0.1 255.255.255.255 127.0.0.1 H
0
#RT2 #SN1 192.168.0.0 255.255.255.0 192.168.0.200
0
#RT3 #SN1 192.168.0.200 255.255.255.255 192.168.0.200 H
0
#RT4 #SN1 192.168.0.201 255.255.255.255 192.168.0.201 H
0
#RT5 #SN1 192.168.0.202 255.255.255.255 192.168.0.202 H
0
#GW #SN1 0.0.0.0 0.0.0.0 192.168.0.1 G
1
#DA1_104 #SN1 192.168.0.1 255.255.255.255 192.168.0.1 H
1
>TCPIP Listopens PROCESS \ISOFT.$ZTCP0
Openers PPID BPID PLFN BLFN Protocol Lport
$ZSSP0 1,366 7 0 TCP 22
$ZCMOM 1,335 7 0 TCP 5988
$ZTMUX 1,375 3 0 UDP 162
$ZTA00 0,288 0 0 TCP 445
$ZTA00 0,288 0 0 TCP 139
Joachim Schmitz
I can see from this that $ZTCP0 is a conventional TCPIP process (there OSS
socker openers are shown as $ZTAnn), is $ZTC0 a TCPSAM or TCP6SAM (I believe
the later)? If so, in dual mode or in IPv4 only mode (seems it is the
later)? It does have more than one IP address (besides the 127.0.0.1), this
could be a problem (for samba), not sure tough. Is it a failover config?
I'm not enough of a NonStop TCP/IP expert to aske the right questions
here...
Bye, Jojo
Kunal Matharu
wrote:
Yes, $ztcp0 is conventional TCPIP – ( $ZTCP0 0,358 200 P 011
255,255 $SYSTEM.SYS16.TCPIP )
and $ZTC0 is ( $ZTC0 1,355 201 P 015 255,255
$SYSTEM.SYS16.TCP6SAM )
If so, in dual mode or in IPv4 only mode (seems it is the
later)? It does have more than one IP address (besides the 127.0.0.1),
this
could be a problem (for samba), not sure tough. Is it a failover
config?
I'm not enough of a NonStop TCP/IP expert to aske the right questions
here...
$ztc0 config for .201, .202
+ ADD SUBNET SN1,TYPE ETHERNET,DEVICENAME L018,IPADDRESS
192.168.0.200,SUBNETMASK 255.255.255.0
+ ALTER SUBNET #SN1, addalias 192.168.0.201, SUBNETMASK
255.255.255.0
+ ALTER SUBNET #SN1, addalias 192.168.0.202, SUBNETMASK
255.255.255.0
Should ( .201 and .202 ) subnets be removed for Samba?
Thank you!
Joachim Schmitz
> On Nov 29, 4:29 pm, "Joachim Schmitz" <nospam.j...@schmitz-digital.de>
> wrote:
>> I can see from this that $ZTCP0 is a conventional TCPIP process (there
>> OSS
>> believe
>> the later)?
>
> Yes, $ztcp0 is conventional TCPIP – ( $ZTCP0 0,358 200 P 011
> 255,255 $SYSTEM.SYS16.TCPIP )
> and $ZTC0 is ( $ZTC0 1,355 201 P 015 255,255
> $SYSTEM.SYS16.TCP6SAM )
>
>
>> If so, in dual mode or in IPv4 only mode (seems it is the
>> later)? It does have more than one IP address (besides the 127.0.0.1),
>> this
>> could be a problem (for samba), not sure tough. Is it a failover
>> config?
You didn't not answer these 2 questions
>> I'm not enough of a NonStop TCP/IP expert to aske the right questions
>> here...
> $ztc0 config for .201, .202
> + ADD SUBNET SN1,TYPE ETHERNET,DEVICENAME L018,IPADDRESS
> 192.168.0.200,SUBNETMASK 255.255.255.0
> + ALTER SUBNET #SN1, addalias 192.168.0.201, SUBNETMASK
> 255.255.255.0
> + ALTER SUBNET #SN1, addalias 192.168.0.202, SUBNETMASK
> 255.255.255.0
> Should ( .201 and .202 ) subnets be removed for Samba?
Just try and you'll know whether it makes a difference.
Bye, Jojo
wbreidbach
wrote:
>
> - Zitierten Text anzeigen -
I do not have an alus IP-address defined, but one of my interfaces is
configured with failover and sambe works fine.
Just one thing: If you are using IPV6 you might see the listen only
when looking at the monitor-processes:
status mon $zztcp.*. I see this