mmmm same behavior under FreeDOS...
Checking network..., I can ping in both direction, from dos to my pc (with xping.exe) and from my pc to dos so it's not a network problem, it seem like a drive mapping problem

What NFS server are you running? It's not expecting some odd like the ancient pcnfsd server, rather than a typical 'modern' nfsv3/4 protocol, is it?

megatron-uk wrote on 2023-07-12, 22:12:

What NFS server are you running? It's not expecting some odd like the ancient pcnfsd server, rather than a typical 'modern' nfsv3/4 protocol, is it?

OpenMediaVault with NFSv2 enabled

Its quite possible that the client is expecting something like the Sun PC-NFS authentication server running - at least that's been the case with other DOS NFS clients I've seen. I've never heard of this "XFS" network stack/NFS client before though.

Nikoh wrote on 2023-07-12, 16:46:

I have […]
Show full quote

I have

Copy code to clipboard

1E: server:export/dos (nobody) rsize=1280 wsize=1280 retry=4 map=all

Not completely familiar with xfstools or OMV but I think you need a leading / for the path i.e. server:/export/dos.
Try mounting that NFS export with a different NFSv2 client, say a Linux client:

1mount -o nfsvers=2 server:/export/dos <mountpoint>

to isolate the issue to either the host or the client. Also:

1showmount -e server

will list the NFS exports for that server.

I don't know other nfs clients for dos, could you tell me which ones are the most used, if any?

jtchip wrote on 2023-07-13, 00:25:

Not completely familiar with xfstools or OMV but I think you need a leading / for the path i.e. server:/export/dos. Try mounting […]
Show full quote

Nikoh wrote on 2023-07-12, 16:46:

I have […]
Show full quote

I have

Copy code to clipboard

1E: server:export/dos (nobody) rsize=1280 wsize=1280 retry=4 map=all

Not completely familiar with xfstools or OMV but I think you need a leading / for the path i.e. server:/export/dos.
Try mounting that NFS export with a different NFSv2 client, say a Linux client:

Copy code to clipboard

1mount -o nfsvers=2 server:/export/dos <mountpoint>

I can't:

jtchip wrote on 2023-07-13, 00:25:

to isolate the issue to either the host or the client. Also: […]
Show full quote

to isolate the issue to either the host or the client. Also:

Copy code to clipboard

1showmount -e server

will list the NFS exports for that server.

First Image attached, any problem, it seems normally mounted on E:

Make sure that LASTDRIVE is set to at least E.

Grzyb wrote on 2023-07-13, 16:25:

Make sure that LASTDRIVE is set to at least E.

LASTDRIVE is set to Z (LASTDRIVE=Z)

Like the other replies, I suspect this is expecting a particular nfs server, not a run of the mill Linux/BSD modern nfs V2/3/4 implementation.

Check that the server is accessible from another 'nornal' nfs client first. A live Linux distro would probably work.

The freedos wiki for xfs mentions you need pcnfsd.

http://wiki.freedos.org/wiki/index.php/NFS_on_DOS

Pcnfsd is NOT the same as standard nfs server implementations:

https://man.netbsd.org/pcnfsd.8

Nikoh wrote on 2023-07-13, 15:19:

I can't: https://i.postimg.cc/t4TDXv6g/Schermata-a-2023-07-13-17-11-37.png […]
Show full quote

I can't:

Which distribution is the client? The client needs NFSv2 enabled, this is controlled by the CONFIG_NFS_V2 kernel configuration, usually stored in /boot/config-<version>. Try using Debian, it does have NFSv2 enabled, at least up to Debian 11. Run showmount anyway to see whether the NFS export was exported correctly.
It looks like the missing / was a transcription issue (you might want to edit the original post) as I pretty much ignored the image of a slightly blurry CRT in favour of the text.
Try mounting it without nfsvers to begin with, which should default to NFSv4, to check that it works. Then work backwards to NFSv3, NFSv3 over UDP, then NFSv2 to see if or when it fails.

megatron-uk wrote on 2023-07-13, 17:16:

The freedos wiki for xfs mentions you need pcnfsd.

http://wiki.freedos.org/wiki/index.php/NFS_on_DOS

This post on VCFED says it works with the Linux kernel NFS server, at least the Ubuntu one, as long as NFSv2 has been enabled.
@Nikoh, compare your configuration with the one in that post. Also try showmnt from xfstools to check that it can see the export.
If it still doesn't work, run a packet capture on the OMV server. OMV 6 is based on Debian 11 so hopefully it can use Debian packages, specifically tshark. Run this to capture NFS packets:

1tshark -O nfs -f "udp port 2049"

and see if there's any difference between mounting with a Linux client and with xfstools on DOS.

Interesting that post seems to say that pcnfsd is only used for the Auth and printing side of things.

My experience connecting old nfs clients (Irix, SunOS, usually for network imaging) to modern Linux nfs servers is that at some point along the line modern implementations (yes, even with nfsv2 enabled) started to break compatability with old systems. Fortunately at work I don't have to support such old systems; we puppet manage and network install mainly RHEL, Centos and Ubuntu on intel. All our legacy stuff is long gone.

Nikoh wrote on 2023-07-13, 10:01:

I don't know other nfs clients for dos, could you tell me which ones are the most used, if any?

Sun PC-NFS was the original NFS client for DOS from the company that originally developed NFS - I guess this might have been the most "popular". Beame & Whiteside also had a DOS/Windows 3.x NFS client which Novell licensed and included in their LAN Workplace product of Unix connectivity/IP tools for DOS/Windows workstations so this likely wasn't uncommon either.

But I don't know that any DOS NFS product was ever truly popular though. In 1993 NetWare had 66% market share, with the rest going to Windows NT (8%), IBM LanManager (7%), Banyan VINES (6.5%), Artisoft LANtastic (4%), DEC PathWorks (3.5%) and "Other" (5% - NFS and other products).

So DOS NFS clients were really just a "compatibility" product. You've already invested a pile of money in expensive UNIX Workstations and Servers and now someone needs a PC running MS Office. You want that PC networked but its not worth setting up a dedicated server for it so you buy some NFS client and just hook it up to the existing network of UNIX machines. The user experience will be worse than if you'd setup a proper PC server but that's acceptable given you're only networking a handful of machines.

If you had a lot of PCs you'd almost certainly skip NFS on PCs entirely and instead run a NetWare server. If you still wanted to provide some file sharing between the PCs and UNIX machines then Novell NFS Gateway lets NetWare mount an NFS share and re-share that to other machines over the usual NetWare protocols, while the Novell NFS Server lets UNIX machines access the NetWare server via NFS.

NFS on Windows to this day is still an odd duck.