PXE boot server

[rwschneider1]

I am trying to set my PXE server to boot a windows installation image. In its current state, I can successfully boot Linux/Unix images without issue.

When I try to boot a Windows installation image, however, I get the following error:
INF file txtsetup.sif is corrupt or missing, status 21.



A TCPDUMP session shows that it is attempting to pull down files using backslashes in the paths:
14:09:44.722774 IP 192.168.108.204.36213 > 192.168.108.16.tftp: 39 RRQ "winxp.sif" octet blksize 1432 tsize 0
14:09:44.724254 IP 192.168.108.16.39933 > 192.168.108.204.36213: UDP, length 25
14:09:44.724553 IP 192.168.108.204.36213 > 192.168.108.16.39933: UDP, length 4
14:09:44.724620 IP 192.168.108.16.39933 > 192.168.108.204.36213: UDP, length 354
14:09:44.724881 IP 192.168.108.204.36213 > 192.168.108.16.39933: UDP, length 4
14:09:44.724966 IP 192.168.108.204.36214 > 192.168.108.16.tftp: 54 RRQ "\winxp\i386\txtsetup.si_" octet blksize 1432 tsize 0
14:09:44.726543 IP 192.168.108.16.34469 > 192.168.108.204.36214: UDP, length 19
14:09:44.727109 IP 192.168.108.204.36215 > 192.168.108.16.tftp: 54 RRQ "\winxp\i386\txtsetup.sif" octet blksize 1432 tsize 0
14:09:44.728280 IP 192.168.108.16.49418 > 192.168.108.204.36215: UDP, length 19



However, I am using a TFTP remap file which contains a single line:
rg \\ /


/usr/sbin/in.tftpd -V yields the following output:
tftp-hpa 5.0, with remap, with tcpwrappers


my xinetd tftp config file contains the following:
service tftp-hpa
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /var/lib/tftpboot -m /etc/tftpd.map
}


I have tried restarting the service several times, and have tried multiple variants of the config files, but to no avail. It seems as though my TFTP remap is not working as desired.

Any help would be greatly appreicated.

Sincerely,
Rick

[Phred]

I haven't done this in several years, and even this it was booting a PC to a windows (WinServer2003) server rather than a *nix server.

As I recall, the biggest hangup was that the server containing the install image *HAD* to also be the DHCP server. Not sure why, but that's the way it had to be.
I'f I'm reading the above rifght, it looks like you're booting from .204 and then trying to get the image from .16? I was never able to get it to work like that.

[rwschneider1]

Hi Phred,

Thanks for your response. Actually .16 is the DHCP server as well as the server that contains the images. .204 is the IP address of the client machine that I am trying to install windows to.

Any thoughts?