Hello,
does anybody know an an answer to this (very specific) problem:
We try to use PXE-Boot on different installationservers under Netware 6 and Zenworks 4. These installationservers have 3 - 6 nic's (1 bakbone-nic and installation-nic's). On
every nic we created via DNS/DHCP manager a different subnet for PXE (to reduce network traffic).
What we can do is:
* a PXE-boot from every nic alone
What we can't do is:
* a PXE-Boot from a random nic while more than one PXE-Subnet is activated
What happens:
* The PXE-Client get the correct DHCP-Server IP (depending on which networksegment the client is connected) an a correct Client IP and subnetmask. If the client tries to load the DINIC.SYS (after autochoosing Zenworks Boot), the client allways contact the IP adress of the PDHCP Server layed down as PDHCP_SERVER_IP in the PDHCP.INI. If the client ist not conneted to the belonging nic it (of course) never get an answer and stop the PXE-Boot with PXE-E11: ARP Timeout error.
I my point of view it looks like Zenworks is using the PDCHP_SERVER_IP adress to transfer the DINIC.SYS File via TFTP.
What we tried (among other things):
* use multiple PDCHP_SERVER_IP entry's -> Only the first entry is used
* no PDCHP_SERVER_IP entry -> The IP-Adress of the DHCP-Server on the Backbone is used (first nic is onbord and used for backbone connection, the DHCP backbone server is installed on a different server).
* changing TFTP_SERVER_IP has no effekt, even if no entry is used.
does anybody know an an answer to this (very specific) problem:
We try to use PXE-Boot on different installationservers under Netware 6 and Zenworks 4. These installationservers have 3 - 6 nic's (1 bakbone-nic and installation-nic's). On
every nic we created via DNS/DHCP manager a different subnet for PXE (to reduce network traffic).
What we can do is:
* a PXE-boot from every nic alone
What we can't do is:
* a PXE-Boot from a random nic while more than one PXE-Subnet is activated
What happens:
* The PXE-Client get the correct DHCP-Server IP (depending on which networksegment the client is connected) an a correct Client IP and subnetmask. If the client tries to load the DINIC.SYS (after autochoosing Zenworks Boot), the client allways contact the IP adress of the PDHCP Server layed down as PDHCP_SERVER_IP in the PDHCP.INI. If the client ist not conneted to the belonging nic it (of course) never get an answer and stop the PXE-Boot with PXE-E11: ARP Timeout error.
I my point of view it looks like Zenworks is using the PDCHP_SERVER_IP adress to transfer the DINIC.SYS File via TFTP.
What we tried (among other things):
* use multiple PDCHP_SERVER_IP entry's -> Only the first entry is used
* no PDCHP_SERVER_IP entry -> The IP-Adress of the DHCP-Server on the Backbone is used (first nic is onbord and used for backbone connection, the DHCP backbone server is installed on a different server).
* changing TFTP_SERVER_IP has no effekt, even if no entry is used.