Quote:

I wouldn't worry too much about the entries in Netstat - these seem to be related to inetd iteslf, rather than the actual operation of any services it manages.

I have just set up a working (basic) samba installation, and I also get these null ports in netstat.

Even if I put a silly entry in inetd:

test1 stream tcp nowait root foo:bar bar
(and an entry in 'services' to match:
test1 20057/tcp test1 #user test of 'missing' service)

This also results in a null port in Netstat when inetd is launched.

The screenshot here shows everything mentioned above.
Note that that even with these null entries in Netstat, an smbfs client can still connect using port 139 to a working Samba server using inetd.

--------------------------------------------

Reading here suggests it is normal behaviour for netstat to show this information for listening services managed by inetd. This in fact shows that inetd is correctly set up to listen on the ports listed.

In summary - ignore the strange entries in netstat, they are normal.

Next step - download netcat from Aminet and use it to check each malfunctioning service individually.

[ Edited by boot_wb 30.07.2016 - 23:16 ]