tftpd32 & WinPE Boot Help Required

HI all....

I'm very, very new to this, and wondered if someone could possibly help?

I can boot the WinPE image through tftpd32 no problem, but when I get to the PE command prompt I can't do anything - I can type commands, but nothing seems to work?

I can't ping the other laptop I've just booted from via crossover cable, and I can't use the 'net use' command as it just errors out with something like 'network path not found.' There do appear to be errors in the tftp log windows though, but I can't make any sense of them - just find it a bit weird that everything appears to transfer ok, and I get to WinPE, but the log appears to suggest otherwise?

Can't see anyway of inserting attachments on here, so have pasted the log below...

Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:13:77:BB:89:3E [22/04 19:40:04.125]
Client requested address 0.0.0.68 [22/04 19:40:04.127]
DHCP: proposed address 192.168.1.10 [22/04 19:40:04.127]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:13:77:BB:89:3E [22/04 19:40:08.188]
Previously allocated address 192.168.1.10 acked [22/04 19:40:08.189]
Connection received from 192.168.1.10 on port 2070 [22/04 19:40:08.194]
Read request for file <boot\pxeboot.com>. Mode octet [22/04 19:40:08.195]
Using local port 64536 [22/04 19:40:08.195]
<boot\pxeboot.com>: sent 49 blks, 25068 bytes in 0 s. 0 blk resent [22/04 19:40:08.234]
Connection received from 192.168.1.10 on port 2071 [22/04 19:40:08.875]
Read request for file <boot\bootmgr.exe>. Mode octet [22/04 19:40:08.892]
Using local port 64553 [22/04 19:40:08.894]
<boot\bootmgr.exe>: sent 817 blks, 417896 bytes in 1 s. 0 blk resent [22/04 19:40:09.685]
Connection received from 192.168.1.10 on port 9394 [22/04 19:40:09.889]
Read request for file <\Boot\Fonts\wgl4_boot.ttf>. Mode octet [22/04 19:40:09.891]
File <Boot\Fonts\wgl4_boot.ttf> : error 3 in system call CreateFile The system cannot find the path specified. [22/04 19:40:09.896]
Connection received from 192.168.1.10 on port 9395 [22/04 19:40:09.925]
Read request for file <\boot\boot.ini>. Mode octet [22/04 19:40:09.926]
File <boot\boot.ini> : error 2 in system call CreateFile The system cannot find the file specified. [22/04 19:40:09.927]
Connection received from 192.168.1.10 on port 9396 [22/04 19:40:25.425]
Read request for file <\Boot\BCD>. Mode octet [22/04 19:40:25.427]
OACK: <tsize=12288,> [22/04 19:40:25.428]
Using local port 60800 [22/04 19:40:25.429]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [22/04 19:40:25.431]
Connection received from 192.168.1.10 on port 9397 [22/04 19:40:25.432]
Read request for file <\Boot\BCD>. Mode octet [22/04 19:40:25.435]
OACK: <tsize=12288,> [22/04 19:40:25.437]
Using local port 60801 [22/04 19:40:25.437]
Connection received from 192.168.1.10 on port 9398 [22/04 19:40:25.468]
<Boot\BCD>: sent 25 blks, 12288 bytes in 0 s. 0 blk resent [22/04 19:40:25.468]
Read request for file <\Boot\Fonts\wgl4_boot.ttf>. Mode octet [22/04 19:40:25.471]
File <Boot\Fonts\wgl4_boot.ttf> : error 3 in system call CreateFile The system cannot find the path specified. [22/04 19:40:25.475]
Connection received from 192.168.1.10 on port 9399 [22/04 19:40:25.495]
Read request for file <\hiberfil.sys>. Mode octet [22/04 19:40:25.496]
File <hiberfil.sys> : error 2 in system call CreateFile The system cannot find the file specified. [22/04 19:40:25.497]
Connection received from 192.168.1.10 on port 9400 [22/04 19:40:25.499]
Read request for file <\Boot\WinPE.wim>. Mode octet [22/04 19:40:25.501]
OACK: <tsize=164002999,> [22/04 19:40:25.502]
Using local port 60804 [22/04 19:40:25.502]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [22/04 19:40:25.505]
Connection received from 192.168.1.10 on port 9401 [22/04 19:40:25.505]
Read request for file <\boot\boot.sdi>. Mode octet [22/04 19:40:25.506]
OACK: <tsize=3170304,> [22/04 19:40:25.507]
Using local port 60805 [22/04 19:40:25.507]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [22/04 19:40:25.508]
Connection received from 192.168.1.10 on port 9402 [22/04 19:40:25.509]
Read request for file <\boot\boot.sdi>. Mode octet [22/04 19:40:25.510]
OACK: <tsize=3170304,> [22/04 19:40:25.511]
Using local port 60806 [22/04 19:40:25.511]
<boot\boot.sdi>: sent 6193 blks, 3170304 bytes in 6 s. 0 blk resent [22/04 19:40:31.579]
Connection received from 192.168.1.10 on port 9403 [22/04 19:40:31.581]
Read request for file <\Boot\WinPE.wim>. Mode octet [22/04 19:40:31.583]
OACK: <tsize=164002999,> [22/04 19:40:31.585]
Using local port 60845 [22/04 19:40:31.585]
<Boot\WinPE.wim>: sent 320319 blks, 164002999 bytes in 314 s. 0 blk resent [22/04 19:45:45.034]
Connection received from 192.168.1.10 on port 9730 [22/04 19:45:46.290]
Read request for file <\Boot\Fonts\wgl4_boot.ttf>. Mode octet [22/04 19:45:46.292]
File <Boot\Fonts\wgl4_boot.ttf> : error 3 in system call CreateFile The system cannot find the path specified. [22/04 19:45:46.294]

Any help would really be appreciated - Thanks

Hello Dekhog,

As a quick idea sometimes winpe images dont know about ehternet harwarware installed on teh machine, so one has to inject the proper drivers, does the ipconfig work?
if so, sometimes the dchp server leases are tricky, so you may want to try to set up a fixec ip adress with all the details running netsh etc etc
hope you success
kind regards

A Windows PE is a minimal Windows environment. I agree with Gonzalongo regarding making sure your NIC drivers are available to the client; perhaps inside your WinPE.wim file.