OK the disk image you're booting is running ghost client, and it sounds like you were expecting ghost.exe. Glad the PXE stuff is working, and you did the right thing by switching servers.ĭo me a favor and mark that as a solution so I get the points. (it's completely retarded that MSFT doesn't really let you control the TFTP server in 2k8) Linux: xinetd & dnsmasq are good too. Windows: TFTPD32 & solar winds tftp are popular options. If nothing else you should use a better tftp server. This is just one alternative, but I think it's the best. I wrote a really long post on this a year or two ago: If you ever plan to use PXE for anything else, you should consider abandoning the 3com suite as it's really old abandon-ware. Take a look at 1 & 2 for your setup, and if you can't get it working please provide some more details about your network typology. If it's really a router that could be your problem, and you may need a dhcp relay to go between subnets.but I'm hoping it's really just acting as a switch. You say their's a router between the server & clients. Is your PXE server providing DHCP? or is it somewhere else? If you're using MSFT's dhcp you'll probably need to set option 60 to "pxeclient", but that will depend on you typology. At the very minimum you'll need both the next-server (tftp server) & filename (your NBP) options defined in your DHCP server. Remember w/ PXE it's all about the DHCP server.
Best practice is to serve \TFTPBOOT as the root and pass \mba.pxe to your clients.Ģ. Once you get this worked out you can run these as services. the clients would try to load \TFTPBOOT\TFTPBOOT\mba.pxe <- watch for that. A common mistake is to chroot'ing the TFTP to \TFTPBOOT (if I remember it's the default and 3com calls it "secure mode" or something silly) and then passing the same location in with the NBP (mba.pxe). This is espeically helpful for monitoring the TFTP server. While setting this up, run both the PXE server & TFTP server as applications.
The PXE service is configured for Proxy DHCP.Ĭan someone please help me figure out where I might have done something wrong? Any suggestions would be great!Ī couple things will make life easier when troubleshooting the 3com suite.ġ. The TFTP service is configured to transmit files from C:\TFTPBOOT In the BOOTPTAB Editor, I am editing C:\TFTPBOOT\BOOTPTAB which looks like this.ĭefault:ha=?:sm=255.255.255.0:to=3600:bf=mba.pxe: In the Options tab, I have the menu title setup, menu wait time of 30s and an empty Path field. Mba.pxe, with two boot options, 1) from HD, 2) ghost.sys In the 3Com Boot Image Editor, I have the the following PXE menu boot file setup: My issue at the moment is that even though I have a ghost.sys image created from the Ghost Boot Wizard in the C:\TFTPBOOT directory, and the 3Com PXE and TFTP services running, I still get a "PXE-E53: No boot filename received". Right now, in my testing environment, I have a small D-Link router between the server and the clients. Also, I have followed the instructions here:
I'm trying to get Symantec Ghost 8.0 setup on a Windows Server 2003 box with 3Com Boot Services ver.