pxeboot.com<\/a><\/p>\nPress F12 for Network Service Boot<\/p>\n
I went to take a new screenshot for you just now, and now it PXE Boots just fine loads the image and gives me the option to capture. Reboot again and it does this again:<\/p>\n
OMG that’s much better
Out of curiosity, do you have PXE listed in your DHCP options? I think it’s option 60, 66 and 67…<\/p>","upvoteCount":0,"datePublished":"2014-03-07T19:12:20.000Z","url":"https://community.spiceworks.com/t/pxe-works-sometimes-wds-2012/283976/5","author":{"@type":"Person","name":"Little-Green-Man","url":"https://community.spiceworks.com/u/Little-Green-Man"}},{"@type":"Answer","text":"\n\n
<\/div>\n Bill Kindle:<\/div>\n
\nOut of curiosity, do you have PXE listed in your DHCP options? I think it’s option 60, 66 and 67…<\/p>\n<\/blockquote>\n<\/aside>\n
yup it is.<\/p>\n
The screenshot suggests that there is some sort of pxe referral/dhcp forwarding going on?<\/p>","upvoteCount":0,"datePublished":"2014-03-07T19:16:40.000Z","url":"https://community.spiceworks.com/t/pxe-works-sometimes-wds-2012/283976/6","author":{"@type":"Person","name":"Gary-D-Williams","url":"https://community.spiceworks.com/u/Gary-D-Williams"}},{"@type":"Answer","text":"
Yep I believe just opts 66/67 I had to step away for a few minutes I can confirm in an hour or so. Should I try disabling it since it should broadcast since they’re on the same subnet?<\/p>","upvoteCount":0,"datePublished":"2014-03-07T19:21:58.000Z","url":"https://community.spiceworks.com/t/pxe-works-sometimes-wds-2012/283976/7","author":{"@type":"Person","name":"mdubya","url":"https://community.spiceworks.com/u/mdubya"}},{"@type":"Answer","text":"
Yea just 66,67 and standard options:<\/p>\n
Do you have any event log entries for WDS?<\/p>","upvoteCount":0,"datePublished":"2014-03-07T20:27:36.000Z","url":"https://community.spiceworks.com/t/pxe-works-sometimes-wds-2012/283976/9","author":{"@type":"Person","name":"Little-Green-Man","url":"https://community.spiceworks.com/u/Little-Green-Man"}},{"@type":"Answer","text":"
Yea, a couple to me everything looks good:<\/p>\n
Event: 57348<\/strong><\/p>\nA Non-Shared buffer was created for reading file C:\\RemoteInstall\\Boot\\x64\\wdsnbp.com.<\/p>\n
Event:4096<\/strong><\/p>\nThe following client booted from PXE:<\/p>\n
Hardware Address: 28-18-78-B7-02-6F<\/p>\n
IP: 10.10.62.105<\/p>\n
Device ID: {0C4E91AD-910F-C724-AFB0-83DB8B77900E}<\/p>\n
ClientArchitecture: 4<\/p>\n
Prestaged: false<\/p>\n
Event: 4099<\/strong><\/p>\nThe Following Client started TFTP Download:<\/p>\n
Client IP: 10.10.62.184<\/p>\n
Filename: Boot\\x64\\wdsnbp.com<\/p>\n
File Size: 30832<\/p>\n
Client Port: 2072<\/p>\n
Server Port: 53220<\/p>\n
Variable Window: false<\/p>","upvoteCount":0,"datePublished":"2014-03-07T20:32:42.000Z","url":"https://community.spiceworks.com/t/pxe-works-sometimes-wds-2012/283976/10","author":{"@type":"Person","name":"mdubya","url":"https://community.spiceworks.com/u/mdubya"}},{"@type":"Answer","text":"
Ah, i do see a #4101<\/span><\/p>\nThe Following Client failed TFTP Download:<\/p>\n
Client IP: 10.10.62.184<\/p>\n
Filename: \\Boot\\x64\\Images\\boot-(2).wim<\/p>\n
ErrorCode: 1460<\/p>\n
File Size: 270098333<\/p>\n
Client Port: 10382<\/p>\n
Server Port: 53222<\/p>\n
Variable Window: true<\/p>","upvoteCount":0,"datePublished":"2014-03-07T20:34:14.000Z","url":"https://community.spiceworks.com/t/pxe-works-sometimes-wds-2012/283976/11","author":{"@type":"Person","name":"mdubya","url":"https://community.spiceworks.com/u/mdubya"}},{"@type":"Answer","text":"
Rebooted the same VM a few minutes ago and a different error:<\/p>\n
What am I missing here? How do I get three entirely different results from PXE booting . Is this an IPHelper issue? I thought I’d bypass any issue while testing by using a massive subnet on the WDS, DHCP Server and DHCP Client?<\/p>\n
the same VM?<\/p>","upvoteCount":0,"datePublished":"2014-03-09T02:57:36.000Z","url":"https://community.spiceworks.com/t/pxe-works-sometimes-wds-2012/283976/12","author":{"@type":"Person","name":"mdubya","url":"https://community.spiceworks.com/u/mdubya"}},{"@type":"Answer","text":"
Mdubya - do you have a link to the article? I’d just like to try and confirm that this is the issue I am dealing with before going to our network admin and tell him I need SCCM off of my WDS box
update on my issue - it did appear to be running services that SCCM had. My Network Admin had started playing around with SCCM, and installed a portion of it on my WDS box - which was definitely causing havoc with my PXE booting/deployments. Once I got the services turned off and disabled, WDS has been functioning normally since. Go figure<\/p>","upvoteCount":0,"datePublished":"2014-04-30T15:19:14.000Z","url":"https://community.spiceworks.com/t/pxe-works-sometimes-wds-2012/283976/15","author":{"@type":"Person","name":"chadrobards","url":"https://community.spiceworks.com/u/chadrobards"}},{"@type":"Answer","text":"
What SCCM services did you have disabled ? I am seeing this same exact issue and cannot figure out how to resolve.<\/p>\n
Thanks in advance!<\/p>","upvoteCount":0,"datePublished":"2015-06-29T11:50:38.000Z","url":"https://community.spiceworks.com/t/pxe-works-sometimes-wds-2012/283976/16","author":{"@type":"Person","name":"terryquaresimo","url":"https://community.spiceworks.com/u/terryquaresimo"}}]}}
mdubya
March 7, 2014, 6:50pm
1
I just setup WDS 2012 recently, and honestly I dont know much about it. But! It kind of seems to be working. I have a dell workstation that will PXE boot to my capture without issue. However, if I plug a laptop or surface into the same network port on the same switch it starts to PXE then I get a “No response from Windows Deployment Server” but in the evnt logs on WDS all looks good:
The Following Client completed TFTP Download:
Client IP: 10.10.62.184
Filename: Boot\x64\wdsnbp.com
File Size: 30832
Client Port: 2071
Server Port: 53223
Variable Window: false
What am I missing? I thought PXE would either work or not work… not have these intermittent results. For trouble shooting everything involved is on the same giant subnet .
5 Spice ups
Can’t really read that screenshot over the blinding power of your flash…
mdubya
March 7, 2014, 7:04pm
3
Haha, sorry. I’ll try to grab another one real quick There is definitely something wierd going on though. I spun up a Hyper-V VM booted it 5-6 times half hour ago and it did the same thing. It gets an IP, gets the IP of the WDS Server then does:
Contacting Server: 10.10.50.34 Gateway (0.0.0.0)
No Response from Windows Deployment Services Server.
Launching pxeboot.com
Press F12 for Network Service Boot
I went to take a new screenshot for you just now, and now it PXE Boots just fine loads the image and gives me the option to capture. Reboot again and it does this again:
1 Spice up
OMG that’s much better
Out of curiosity, do you have PXE listed in your DHCP options? I think it’s option 60, 66 and 67…
yup it is.
The screenshot suggests that there is some sort of pxe referral/dhcp forwarding going on?
mdubya
March 7, 2014, 7:21pm
7
Yep I believe just opts 66/67 I had to step away for a few minutes I can confirm in an hour or so. Should I try disabling it since it should broadcast since they’re on the same subnet?
mdubya
March 7, 2014, 8:22pm
8
Yea just 66,67 and standard options:
Do you have any event log entries for WDS?
mdubya
March 7, 2014, 8:32pm
10
Yea, a couple to me everything looks good:
Event: 57348
A Non-Shared buffer was created for reading file C:\RemoteInstall\Boot\x64\wdsnbp.com.
Event:4096
The following client booted from PXE:
Hardware Address: 28-18-78-B7-02-6F
IP: 10.10.62.105
Device ID: {0C4E91AD-910F-C724-AFB0-83DB8B77900E}
ClientArchitecture: 4
Prestaged: false
Event: 4099
The Following Client started TFTP Download:
Client IP: 10.10.62.184
Filename: Boot\x64\wdsnbp.com
File Size: 30832
Client Port: 2072
Server Port: 53220
Variable Window: false
mdubya
March 7, 2014, 8:34pm
11
Ah, i do see a #4101
The Following Client failed TFTP Download:
Client IP: 10.10.62.184
Filename: \Boot\x64\Images\boot-(2).wim
ErrorCode: 1460
File Size: 270098333
Client Port: 10382
Server Port: 53222
Variable Window: true
mdubya
March 9, 2014, 2:57am
12
Rebooted the same VM a few minutes ago and a different error:
What am I missing here? How do I get three entirely different results from PXE booting . Is this an IPHelper issue? I thought I’d bypass any issue while testing by using a massive subnet on the WDS, DHCP Server and DHCP Client?
the same VM?
mdubya
March 10, 2014, 12:26pm
13
After a few dozen hours fighting with this thing I believe I’ve found the problem. I found a technet post that mentioned WDS may conflict with SCCM. The server I was using previously had SCCM installed.
I installed WDS on a new server and everything is working perfectly now.
Mdubya - do you have a link to the article? I’d just like to try and confirm that this is the issue I am dealing with before going to our network admin and tell him I need SCCM off of my WDS box
update on my issue - it did appear to be running services that SCCM had. My Network Admin had started playing around with SCCM, and installed a portion of it on my WDS box - which was definitely causing havoc with my PXE booting/deployments. Once I got the services turned off and disabled, WDS has been functioning normally since. Go figure
What SCCM services did you have disabled ? I am seeing this same exact issue and cannot figure out how to resolve.
Thanks in advance!
![\"pxe.jpg\"](\"https://us1.discourse-cdn.com/spiceworks/original/4X/9/3/0/930f463972b592b0d65e926605a623207ab9fbcf.jpeg\")