Ghost Solution Suite

 View Only
Back to discussions
Expand all | Collapse all

PXE boot not working my way

  • 1.  PXE boot not working my way

    Posted Jan 04, 2008 02:46 PM
    Hi,
     
    I have installed GSS 2.0 and the 3com pxe boot environment on a windows 2003 server. Dhcp is on another server so dhcp proxy is enabled in the pxe server.
     
    I have created a "tcp/ip network ghost clinet boot image" in GSS boot wizard. I have also created a boot menu in the boot image editor. I have also edited the boottptab file. So I have .sys files, .mnu files .pxe files but no .img file. Do I need one and if so how do I create it without using a floppy? The boot image editor assumes A: as th source.
     
    When I boot a client into pxe it either does not connect at all to the server but instead just waits for dhcp. I have checked the dhcp and there is an active lease for the mac adress I am working with.
     
    Thanks a lot, I´m going nuts not being able to connect to the console and push an OS image.
     


  • 2.  RE: PXE boot not working my way

    Posted Jan 08, 2008 01:17 AM
    Hi,

    One possibility is a firewall in the server blocking PXE requests. Do you have any firewalls installed?

    If you go to Control panel, you can enable the log files for 3com PXE and TFTP services. Do they say anything?

    You have all the files necessary. mnu file and pxe file are pretty much the same, they are menus. It will allow you to select different sys files from the menu.

    Basically, you need to assing the .pxe file to the mac address of the machine in boottab file (you can use wildcards too) and the pxe file should contain entries for differnt sys files. Though there are different ways of setting this, above is the most common way.

    Krish


  • 3.  RE: PXE boot not working my way

    Posted Jan 08, 2008 06:26 AM
    Hello,
     
    There is no firewall preventing communication. With the 3com pxe the pxe server does not show on the network. With the deploy center pxe the pxe at least show on the network but the menus won´t work. I have followed the instrucions available step by step.
     
    Logging has been enabled for the 3com pxe but the logs don´t show much.
     
    I have tried all the links below and as I said, followed them step by step. The last one worked ONCE. But instead the computer would not boot into a console session. The next time I rebooted the computer it didn´t work. I repeated the steps again but never got it to work
     
     
    Whick pxe is endosrsed and the supported one that we should use? It seems pointless tu supply several differnt ones instead of a single one that is well supported.
     
    Is ther no other way in GSS 2.0 to supply brand new computers with an OS except PXE?
     
    Thanks


  • 4.  RE: PXE boot not working my way

    Posted Jan 08, 2008 06:49 PM
    I quickly skimmed the material you link'd to.  It all looks good.

    You mentioned your PXE is on a 2003 Server (so is mine) and your DHCP is on another server (again the same as me.)  2003 Server (where your PXE is) does have a firewall by default.  Make sure your Exceptions includes the actual server daemon.  Once you're at the Exceptions tab on the windows 2003 firewall, click Add Program.  It might show "BOOTP Server" or "PXE Server"  in the programs list.  That's not enough.  CLick Browse.  Then go to C:/Program Files/3Com/Boot Services/3cpxes.exe as well.  In all, you'll need 3cpxe.exe 3cpxes.exe 3ctftp.exe and 3ctftps.exe.  I'm not sure if you really need the "not-s" version but I do it anyway.  The not-s version of each program is what shows up on the Programs list - I think it's the Control Panel/GUI for the actual daemon/server (which would be the S version of the software.)

    You mentioned looking in the PXE logs and not seeing much.  Again, that makes me think firewall.  If the firewall is blocking access to your actual PXE/TFTP server, you won't see any log activitiy.  You should at least see an incoming request in the PXE SErver log (3COM PXE Control Panel, Logging Tab, View Log File button.)   You should also see something in the Event Viewer if you have those two boxes checked (I do) so try Administrative Tools -> Event Viewer -> Applications, and you should see "3Com PXE" as the "Source" column for the entries.
    In the Network Adapters tab, make sure the correct adapter is checked for PXE

    If you started your daemon first, and then made changes to the Windows firewall, it won't take.  You'll need to reboot or at least restart the services.

    Since you're not PXE'ing, you probably aren't getting far enough for TFTP, but you can check those logs too (3COM TFTP control panel, Configure, Enable Log File, View Log File.)

    If you're sure it's not a firewall, then double check the BOOTPTAB file by running the BOOTPTAB Editor program.  Make sure in the Address column, you've got enough ?-marks.  I missed by one once (sigh) and so it had 000???... in that column instead of 00??.... :)  I shoulda just had all ?-marks and it'd have been fine.  Changes to the BOOTPTAB file should be automatically detected by the PXE daemon, but Restart the service anyway.

    I only have three files in my C:/TFTPBOOT/ directory - the one .PXE file and two .SYS files.  The PXE file I made using that BootImage editor, Create PXE Boot menu file.  Just create a single-entry one that has the default entry as boot local hard drive checked.  I call mine mba.pxe and that's what the BOOTPTAB file uses for MAC addresses that match my ?????......

    The two SYS files, I didn't make using the Boot Image Editor.  I made those directly w/Ghost Boot Wizard.   The last two option on the GBW main mune "TCP/IP Network Boot Image" and "TCP/IP Network Ghost Client Boot Image".  I made a SGS11-Manual.sys and SGS11-Console.sys and saved them to C:/TFTPBOOT/ using the GBW.  My Boot Image Editor PXE menu refers to those two files (the topmost default entry being boot to local hard drive.)

    Good luck,
    PH



  • 5.  RE: PXE boot not working my way

    Posted Jan 09, 2008 04:16 AM
    Hi and thanks for your reply!
     
    Allthough I´m quite sure it´s not firewall I will check what you suggested. I actually did get som action in the log file and as mentioned in my last post got the pxe to boot, but only once. So that would indicate that the firewall isn´t the problem, or do you mean thát the "firewall problem" could be intermittent?
     
    In the BOOTPTAB I entered all questionmarks as wildcard.
    Should the only line in the BOOTPTAB file be the one that I enter or can the default example line be left?
     
    I used ghost boot wizard to create the "network ghost client image" and the 3com editor for the pxe and menu files.
     
    In one document there was something about adding pboot.exe and editing the autoexec.bat with swithes -ja -sure with the argument of the ghost session name for the -ja switch. Is that needed?
     
    Thanks!


  • 6.  RE: PXE boot not working my way

    Posted Jan 09, 2008 01:15 PM
    I don't remember what the default line in the BOOTPTAB file is.  The only line in my BOOTPTAB file is the ????... file that points to a file mba.pxe.

    None of the switches or pboot will matter (yet.)  Your systems haven't booted via the PXE image, so until then it really won't matter :)  Once you manage to boot PXE then you can worry about whether the contents of that bootable PXE image is right or not :)

    I don't think the firewall would be intermittent.  At least on my setup, usually once my firewall is working right, it just works.  The DHCP, PXE, TFTP servers along with the Ghost console and the target client are all on the same network right?  No routers, different subnets, etcetc in between them anywhere?  Make sure you both PXE and TFTP services are running, and that you only have one each of DHCP, PXE, and TFTP server on your network.

    Post a copy of your log file(s) from DHCP, PXE, TFTP services.  If you can Pause the screen while your client boots up, passes POST, and then attempts the DHCP/PXE boot process via its NIC that would be good.  I've had difficulty debugging my DHCP/PXE NIC boot stuff way back when, cause it would just flash by the screen (after some error) and I couldn't read the stupid screen :)  Sigh.  So I sat there booting again and again trying to read a few words at a time, and trying to hit Pause at just the right time :)

    Good luck,
    PH



  • 7.  RE: PXE boot not working my way

    Posted Jan 10, 2008 12:10 AM
    Hi,

    Other than what Paul had suggested, only think I can add is that keeping the default entries there should not create any issue. When you use a full wildcard (12 question marks) it pretty much take over the whole network.

    Krish


  • 8.  RE: PXE boot not working my way

    Posted Jan 11, 2008 05:22 AM
    I have checked the firewall and on the pxe server it is disabled. I have also checked the anti virus firewall and all is ok. When I use the deploy center pxe and search the network for pxe servers it shows up. When I tried the same with the 3com ( disabling the deploy center pxe of course) it shows up once. Then I tried to boot my client and it went through the pxe menu and started to load pc-dos. It then gets stuck on a line in dos-mode, saying "client ip:port 1346 connecnting to server ip:port 1347" and then it keeps trying and says acknowledging and restarting.
     
    The next time I tried the pxe server does not show up again on the network and the client never goes into the boot menu again. That´s when I gave up and went home.
     
    Here are som logs:
     
    The last try that I described above was on 2008-01-10
     
    3ComBOOTP.log
     
    2008-01-10 22:13 - Service started
    2008-01-10 22:13 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:13 - Data read: 6 hosts, 1 templates
    2008-01-10 22:16 - Service started
    2008-01-10 22:16 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:16 - Data read: 6 hosts, 1 templates
    2008-01-10 22:18 - Service reconfigured
    2008-01-10 22:18 - Service started
    2008-01-10 22:18 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:18 - Data read: 6 hosts, 1 templates
     
    3ComPXE.log
     
    2008-01-05 17:01 - Service started
    2008-01-05 17:01 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 13:35)
    2008-01-05 17:01 - Data read: 6 hosts, 1 templates
    2008-01-05 17:02 - Service reconfigured
    2008-01-05 17:02 - Service started
    2008-01-05 17:02 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 13:35)
    2008-01-05 17:02 - Data read: 6 hosts, 1 templates
    2008-01-05 17:16 - Service stopped
    2008-01-05 17:16 - Program started
    2008-01-05 17:16 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 13:35)
    2008-01-05 17:16 - Data read: 6 hosts, 1 templates
    2008-01-05 17:16 - Server started
    2008-01-05 17:16 - Program exit
    2008-01-05 17:24 - Service started
    2008-01-05 17:24 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 13:35)
    2008-01-05 17:24 - Data read: 6 hosts, 1 templates
    2008-01-05 17:24 - Service reconfigured
    2008-01-05 17:24 - Service started
    2008-01-05 17:24 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 13:35)
    2008-01-05 17:24 - Data read: 6 hosts, 1 templates
    2008-01-05 17:38 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 17:38)
    2008-01-05 17:38 - Data read: 6 hosts, 1 templates
    2008-01-05 17:39 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-05 17:39 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-05 17:39 - PXE: [001D92302EC6] (STDSTH001)
    2008-01-05 17:41 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-05 17:41 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-05 17:41 - PXE: [001D92302EC6] (STDSTH001)
    2008-01-05 17:42 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-05 17:42 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-05 17:42 - PXE: [001D92302EC6] (STDSTH001)
    2008-01-05 17:43 - Service reconfigured
    2008-01-05 17:43 - Service started
    2008-01-05 17:43 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 17:38)
    2008-01-05 17:43 - Data read: 6 hosts, 1 templates
    2008-01-05 17:44 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-05 17:44 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-05 17:44 - PXE: [001D92302EC6] (STDSTH001)
    2008-01-05 17:58 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-05 17:58 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-05 17:58 - PXE: [001D92302EC6] (STDSTH001)
    2008-01-05 18:00 - Service started
    2008-01-05 18:00 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 17:38)
    2008-01-05 18:00 - Data read: 6 hosts, 1 templates
    2008-01-05 18:05 - Service reconfigured
    2008-01-05 18:05 - Service started
    2008-01-05 18:05 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 17:38)
    2008-01-05 18:05 - Data read: 6 hosts, 1 templates
    2008-01-05 18:08 - Service reconfigured
    2008-01-05 18:08 - Service started
    2008-01-05 18:08 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 17:38)
    2008-01-05 18:08 - Data read: 6 hosts, 1 templates
    2008-01-05 18:18 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 18:18)
    2008-01-05 18:18 - Data read: 6 hosts, 1 templates
    2008-01-05 18:25 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 18:25)
    2008-01-05 18:25 - Data read: 6 hosts, 1 templates
    2008-01-05 18:26 - Service reconfigured
    2008-01-05 18:26 - Service started
    2008-01-05 18:26 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 18:25)
    2008-01-05 18:26 - Data read: 6 hosts, 1 templates
    2008-01-05 18:37 - Service reconfigured
    2008-01-05 18:37 - Service started
    2008-01-05 18:37 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 18:25)
    2008-01-05 18:37 - Data read: 6 hosts, 1 templates
    2008-01-06 15:51 - Service reconfigured
    2008-01-06 15:51 - Service started
    2008-01-06 15:51 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-05 18:25)
    2008-01-06 15:51 - Data read: 6 hosts, 1 templates
    2008-01-06 15:54 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 15:54)
    2008-01-06 15:54 - Data read: 6 hosts, 1 templates
    2008-01-06 16:01 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-06 16:01 - Data read: 6 hosts, 1 templates
    2008-01-06 16:05 - Service stopped
    2008-01-10 21:59 - Service started
    2008-01-10 21:59 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 21:59 - Data read: 6 hosts, 1 templates
    2008-01-10 22:00 - Service stopped
    2008-01-10 22:01 - Service started
    2008-01-10 22:01 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:01 - Data read: 6 hosts, 1 templates
    2008-01-10 22:01 - Proxy: [00B0D086FD66] (STDSTH001)
    2008-01-10 22:01 - Proxy: [00B0D086FD66] (STDSTH001)
    2008-01-10 22:01 - Proxy: [00B0D086FD66] (STDSTH001)
    2008-01-10 22:01 - Proxy: [00B0D086FD66] (STDSTH001)
    2008-01-10 22:02 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-10 22:02 - Proxy: [001D92302EC6] (STDSTH001)
    2008-01-10 22:02 - PXE: [001D92302EC6] (STDSTH001)
    2008-01-10 22:02 - Proxy: [00B0D086FD66] (STDSTH001)
    2008-01-10 22:02 - Proxy: [00B0D086FD66] (STDSTH001)
    2008-01-10 22:02 - Proxy: [00B0D086FD66] (STDSTH001)
    2008-01-10 22:03 - Service reconfigured
    2008-01-10 22:03 - Service started
    2008-01-10 22:03 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:03 - Data read: 6 hosts, 1 templates
    2008-01-10 22:05 - Service reconfigured
    2008-01-10 22:05 - Service started
    2008-01-10 22:05 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:05 - Data read: 6 hosts, 1 templates
    2008-01-10 22:06 - Service stopped
    2008-01-10 22:08 - Program started
    2008-01-10 22:08 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:08 - Data read: 6 hosts, 1 templates
    2008-01-10 22:08 - Server started
    2008-01-10 22:08 - Program exit
    2008-01-10 22:09 - Program started
    2008-01-10 22:09 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:09 - Data read: 6 hosts, 1 templates
    2008-01-10 22:09 - Server started
    2008-01-10 22:10 - Server stopped
    2008-01-10 22:10 - Program exit
    2008-01-10 22:10 - Service started
    2008-01-10 22:10 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:10 - Data read: 6 hosts, 1 templates
    2008-01-10 22:11 - Service reconfigured
    2008-01-10 22:11 - Service started
    2008-01-10 22:11 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:11 - Data read: 6 hosts, 1 templates
    2008-01-10 22:13 - Service stopped
    2008-01-10 22:13 - Service started
    2008-01-10 22:13 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:13 - Data read: 6 hosts, 1 templates
    2008-01-10 22:16 - Service started
    2008-01-10 22:16 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:16 - Data read: 6 hosts, 1 templates
    2008-01-10 22:18 - Service reconfigured
    2008-01-10 22:18 - Service started
    2008-01-10 22:18 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:18 - Data read: 6 hosts, 1 templates
    2008-01-10 22:18 - Service reconfigured
    2008-01-10 22:18 - Service started
    2008-01-10 22:18 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:18 - Data read: 6 hosts, 1 templates
    2008-01-10 22:18 - Service stopped
    2008-01-10 22:18 - Service started
    2008-01-10 22:18 - Data file: D:\Program Files\TFTPBOOT\BOOTPTAB (2008-01-06 16:01)
    2008-01-10 22:18 - Data read: 6 hosts, 1 templates
     
    3ComTFTPS.log
     
    1/5/08 17:16 - Program started
    1/5/08 17:16 - Server started
    1/5/08 17:16 - Program exited
    Sat Jan 05 17:24:28 - Service started
    DOWNLOAD Sat Jan 05 17:39:39 127.0.0.1 START d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Sat Jan 05 17:39:40 192.168.40.2 START d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Sat Jan 05 17:39:40 127.0.0.1 DONE d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Sat Jan 05 17:39:40 192.168.40.2 DONE d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Sat Jan 05 17:39:45 192.168.40.2 START d:\program files\TFTPBOOT\pxe.sys
    Sat Jan 05 17:57:49 - Service started
    DOWNLOAD Sat Jan 05 17:58:30 127.0.0.1 START d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Sat Jan 05 17:58:30 192.168.40.2 START d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Sat Jan 05 17:58:30 127.0.0.1 DONE d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Sat Jan 05 17:58:30 192.168.40.2 DONE d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Sat Jan 05 17:58:38 192.168.40.2 START d:\program files\TFTPBOOT\pxe.sys
    Sat Jan 05 18:00:12 - Service started
    Sat Jan 05 18:26:20 - Service stopped
    Sat Jan 05 18:26:22 - Service started
    Sun Jan 06 15:51:05 - Service stopped
    Sun Jan 06 15:51:15 - Service started
    Sun Jan 06 16:05:16 - Service stopped
    Thu Jan 10 21:59:30 - Service started
    Thu Jan 10 22:00:00 - Service stopped
    Thu Jan 10 22:01:07 - Service started
    DOWNLOAD Thu Jan 10 22:02:17 127.0.0.1 START d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Thu Jan 10 22:02:17 192.168.40.21 START d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Thu Jan 10 22:02:17 127.0.0.1 DONE d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Thu Jan 10 22:02:17 192.168.40.21 DONE d:\program files\TFTPBOOT\mba.pxe
    DOWNLOAD Thu Jan 10 22:02:20 192.168.40.21 START d:\program files\TFTPBOOT\pxe.sys
    Thu Jan 10 22:07:22 - Service started
    Thu Jan 10 22:08:04 - Service stopped
    1/10/08 22:08 - Program started
    1/10/08 22:08 - Server started
    1/10/08 22:08 - Program exited
    1/10/08 22:09 - Program started
    1/10/08 22:09 - Server started
    1/10/08 22:10 - Server stopped
    Thu Jan 10 22:10:39 - Service started
    Thu Jan 10 22:13:43 - Service stopped
    Thu Jan 10 22:13:44 - Service started
    Thu Jan 10 22:16:26 - Service started
     


  • 9.  RE: PXE boot not working my way

    Posted Jan 14, 2008 05:05 PM
    Hi Alex,

    One thing I noticed was that you have both Bootp and PXE services running. You need only one of them, only PXE service for DHCP environments.

    When you say you stopped DCL PXE server, did you in stop both PXE and TFTP services?

    Once you make sure only 3ComPXE and 3ComTFTP services are running from the lot, have a look at 3ComPXE log. Every time it receives a request for a client regardless it is in the database or not, PXEServer creates a log entry. I have seen couple of them in your log, such as


    2008-01-05 17:39 - Proxy: [001D92302EC6] (STDSTH001)


    If the MAC is not in the boottab, instead of the last parameter it will just say (not found).

    Let me know what you would get after doing this.

    Krish

    Message Edited by Krish Jayaratne on 01-15-2008 10:06 AM


  • 10.  RE: PXE boot not working my way

    Posted Jan 15, 2008 04:30 AM
    Hi Krish,
     
    I stopped all symantec services related to pxe/tftp. Later on I also unistalled all of the deploy center.
     
    So I don´t need to install the Bootp service at all in this scenario then? Would the Bootp service being started, disturb the functioning of the pxe and tftp?
     
    In the log files above on the 10:th of january only 3Com was running, no deploy center.
     
    /Alex
     
     


  • 11.  RE: PXE boot not working my way

    Posted Jan 15, 2008 12:34 PM
    Yep.  BOOTP and PXE will conflict will each other.   I dunno anything about the Deploy Center stuff but I assume it'd be the same there.  The 3COM stuff installs BOOTP, PXE, and TFTP but only the PXE and TFTP need/should be running (plus some DHCP server somewhere else.)

    Despite the other software being called a BOOTPTAB Editor, the PXE Server reads the BOOTPTAB file.  So don't worry, there's no PXETAB or anything like that.

    Both the 3COM PXE & 3COM TFTP should be running.  The 3COM BOOTP should not be running.  The two services that are running should have Logging enabled and as always, make sure the firewall exceptions are in place for the actual service executable (the "s" version of the software.)  Once this is the case, anything that attempts to PXE Boot (whether succesful or not) should at least show up as a log-entry in your PXE and/or TFTP service logs as either succesful or unsucessful.

    Good luck,
    PH