Problem with iPXE's NFS protocol #1541
Replies: 3 comments 2 replies
|
Every error that iPXE shows also includes an ipxe.org url. Please make sure you include the actuall error message, including the url that is shown in the message. |
|
255 / 5 000 |
|
So then you don't have a problem with iPXE, but rather with some tools in an initrd that iPXE can't do anything about? |
|
If you load kernel and initrd over http, then you should probably not even enable iPXEs NFS support. And it has nothing to do with any NFS you are using inside booted OS. |
|
In this case, it's the Linux Mint installer that can't access the NFS share, |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I'm experiencing a problem with iPXE's NFS protocol that I can't resolve despite
extensive research.
I configured iPXE on a Windows Server 2019 to deploy Linux Mint via iPXE. I
created an NFS share on the Windows server into which I extracted the Linux Mint ISO. I removed
authentication for the different Kerberos versions, allowed access for
unmapped users, and allowed anonymous access. Regarding security (NTFS rights), I even added "Anonymous logon" for reading. I can access this share from a Debian or Ubuntu client, both via TCP and UDP, without needing to authenticate. However, when I try to deploy Linux Mint with iPXE, after loading the vmlinuz and initrd files (via HTTP), I receive the following error message:
NFS over TCP is not available on xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx being the IP address of my Windows server).
I did, however, enable NFS support in the general.h file before compiling the iPXE files.
Could the problem be due to an incompatibility between iPXE and Windows server for the NFS protocol?
Thanks in advance for your answers.
All reactions