Re: NetServer under V4R4

Hello,

Am 13.08.2023 um 00:06 schrieb hush <system@xxxxxxxxx>:

I am working on my 170 running V4R4 and trying to get CODE/400 up on a Windows box- for some reason I am unable to authenticate to Samba shares on the 170 using either of my accounts.

What Windows release are you running? Poking blindly, I assert: Use an equally old release of e. G. NT4 or 2000 (e. g. in a VM) and you'll be fine. (If you plan to do that, you might have a look at legacyupdate.net — extremely helpful to quickly patch a new w2k install to the latest level available.)

NetServer V4 only supports NetBIOS over TCP connections (NBT) over TCP Port 139. A protocol which has been deprecated by Microsoft for decades, in favor of SMB (tcp/445). I wouldn't wonder if some "code rot" broke client support in recent Windows releases. NetServer didn't age as well as the rest of the system, when it comes to connection from/to the outside world.

I've tried to beat my Mac into submission for mounting shares for some crude file serving purposes and eventually gave up. I suggest you do the same. NetServer V4 just isn't worth the effort. And this won't change unless somebody ports (parts of) Samba to V4. :-)

Btw., if you find out what's going on over the TCP socket being opened by issuing strcode, I'm, all ears! Maybe this facility can be repurposed for other uses?

I am guessing some sort of misconfiguration.

There is not much you can configure at all.

I've been unable to find any NetServer configuration menus

Yap. Unfortunately, IBM decided that NetServer configuration has to be done solely through Operations Navigator, a component of Client Access Express. Under the hood, those OpNav functions just place API calls to be serviced by your machine.

and the GO NETS command does not exist in an OS400 version this old

Yap. See here:

https://blog.faq400.com/en/system-administration-en/04d-ifs-en/netserver-for-everyone-part-3/

Unfortunately, NETSRVCMD seems to not be available in V4R5 and earlier. Not sure if it could be feasible to "backport" the code from newer releases, though. Looking through the accompanying document QUSRTOOL/QATTINFO.TZLSINFO on a 7.2 installation, I see components mainly being sources for CLP, CMD, Menu, and a message file. Not sure if trying a port is worth the effort. See description above.

This time it's not the firewall, I haven't reenabled that yet. :)

LOL! That clearly was an "own goal" — this time intentionally. ;-)

:wq! PoC