Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Booting wds without wimboot
2014-12-31, 14:08
Post: #10
RE: Booting wds without wimboot
Okay, thank you so long. I'll be patient.
But I think this is an additional problem.

Since the intel chipset gets stuck I tried a different (and brand new) machine with a realtek card.
Dhcp and so on works fine.
Downloading of 512mb is smooth and fast (a bit more than half a minute, didn't test md5sum or sha1sum) and resuming an interrupted link works fine, too.

But same issue here:
net0: 172.16.0.45/255.255.0.0 gw 172.16.0.1
Next server:172.16.0.2
Filename: boot\x86\wdsnbp.com
tftp://172.16.0.2/boot\x86\wdsnbp.com... ok

Downloaded WDSNBP...

Press F12 for network service boot
Architecture: x64
WDSNBP started using DHCP Referral.
Contacting Server: 172.16.0.2 (Gateway: 0.0.0.0).
Contacting Server: 172.16.0.2.
TFTP Download: boot\x64\pxeboot.n12
.

<multiple times the same two lines, very often>

TFTP Download: boot\x64\pxeboot.n12
.
TFTP Download: boot\x64\pxeboot.n12

Failed to restart TFTP.
TFTP download failedCould not boot image: Error 0x7f8d101 (http://ipxe.org/7f8d8101)
No more network devices.

iPXE> route
net0: 172.16.0.45/255.255.0.0 gw 172.16.0.1


I'm wondering what this message means: (Gateway 0.0.0.0)
and weather this is okay.

Since this onboard networkcard is only a sigle one I couldn't test loopback functions for now. - Or should I try it with a different one?
Please advise what to do or test next.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Booting wds without wimboot - chmeyer - 2014-12-01, 21:46
RE: Booting wds without wimboot - chmeyer - 2014-12-31 14:08



User(s) browsing this thread: 1 Guest(s)