Posts made by chornbeck

@theopenem_admin Also, we have two other DHCP policies set up for 32-bit and BIOS respectively in the DHCP server. But, we really don't use them these days.

ipxe.zip @theopenem_admin We are using the DHCP proxy. Here is a screenshot of the options in the server.

Also, I attached my original ipxe file that works.

ipxe.zip

Thanks for the help!

@theopenem_admin I copied the old ipxe file back and updated the pxe settings. I get this error when I do that, I don't know if it would be relevant.

"Updated Settings Successfully, But Could Not Copy PXE Binaries On One Or More Com Servers. Check The Logs For More Info"

The old file works on my old device again.

@theopenem_admin Yea, unfortunately. I just tried an older device that worked before again and it times out trying to download the default.ipxe file.

@theopenem_admin Good morning! Any luck adding that TFTP path to the ipxe image? Thanks!

@theopenem_admin
Thanks! I poked around on this end and wasn't able to get anywhere.

@theopenem_admin
Thanks! I just tried it out. Looks like we're making some progress. Unfortunately, now I'm getting this timeout error after pulling down the default.ipxe file. I'll keep poking around.

@theopenem_admin Oh no, I'm sorry to hear that.

@theopenem_admin Good morning! Any luck on the ipxe build? Thanks!

@theopenem_admin Sure, that sounds good. We are in no rush. I did have a similar problem a few years back and a new iPXE build did solve my problem back then. Thank you so much!

@theopenem_admin Sure, I just tried both of those options in the "PXE settings" menu. I got the same result.

Hi there,

We are purchasing some HP ProBook 440 G11 laptops. I'm trying to network boot using iPXE and I'm having trouble. On the laptop, the process stops at "iPXE Initialising devices..." Here's a screenshot:

On the server, when I check the logs viewer in the TFTPD64_gui.exe, I see the following:

Connection received from 10.14.2.19 on port 1897 [31/03 11:37:06.603]
Read request for file <proxy/efi64/pxeboot.0>. Mode octet [31/03 11:37:06.603]
OACK: <tsize=1020416,blksize=1468,> [31/03 11:37:06.604]
Using local port 58007 [31/03 11:37:06.604]
Peer returns ERROR <User aborted the transfer> -> aborting transfer [31/03 11:37:06.604]
Connection received from 10.14.2.19 on port 1898 [31/03 11:37:06.604]
Read request for file <proxy/efi64/pxeboot.0>. Mode octet [31/03 11:37:06.604]
OACK: <blksize=1468,> [31/03 11:37:06.604]
Using local port 58008 [31/03 11:37:06.604]
<proxy\efi64\pxeboot.0>: sent 696 blks, 1020416 bytes in 0 s. 0 blk resent [31/03 11:37:06.747]
Connection received from 10.14.2.19 on port 1899 [31/03 11:37:06.763]
Read request for file <proxy\efi64\autoexec.ipxe>. Mode octet [31/03 11:37:06.763]
File <proxy\efi64\autoexec.ipxe> : error 2 in system call CreateFile The system cannot find the file specified. [31/03 11:37:06.763]

Everything works on all of our other devices. Also, I tried updating the Kernel in the boot menu to the newest version available, "6.13.4x64-updated".

Any ideas on what I can do? Thank you!

@eruthon Me as well, so far so good! I've got two sessions running right now. I haven't tested anything else yet.

@theopenem_admin Thank you!

@theopenem_admin I think we are on to something.

One of our techs started deploying an image. I tried to PXE boot and start a task and it is giving me "Not Authorized" again. It's only happening whenever 1 other task is running.

@theopenem_admin Is it possible that if a task is currently running, starting a new task will not start/queue up in the task list? We're suspecting this might be the case and are going to test it shortly.

Nobody is using the system right now and I've not had any problem getting in.

@theopenem_admin Sure, here's a compilation of the web.config in each folder.

toec-API:

• web.config 4.8
  Toems-API:
• web.config: 4.8
• web.config.mysql: 4.6
• web.config.sqlserver: 4.6
  toems-UI:
• web.config 4.8

Should the web.config.mysql and web.config.sqlserver files be 4.8?

I attempted again using the newly created account that worked before and it gave me "Not authorized" this time. I also regenerated the Imaging token under settings > security.

@theopenem_admin I did not regenerate any tokens. I can try this.

I just ran into the problem again with the admin account.

I tried changing the password for admin, same problem.

I tried one of our techs accounts, no change.

I tried using a newly created account and it worked.

@theopenem_admin I just doublechecked the server and .NET 4.8 is installed. I didn't make any changes to it before or after install theopenem 1.5.0.