I shall peruse that as well. Thanks.
Kurt On Thu, Sep 26, 2013 at 5:16 AM, Christopher Bodnar < [email protected]> wrote: > Have you tried changing option 67 to: > > boot\x86\wdsnbp.com > > Per this KB article? > > http://technet.microsoft.com/en-us/library/cc766320(v=ws.10).aspx > > > *Christopher Bodnar* > Enterprise Architect I, Corporate Office of Technology:Enterprise > Architecture and Engineering Services Tel 610-807-6459 > 3900 Burgess Place, Bethlehem, PA 18017 > [email protected] > > > * > The Guardian Life Insurance Company of America* > * > **www.guardianlife.com* <http://www.guardianlife.com/> > > > > > > > From: Kurt Buff <[email protected]> > To: [email protected] > Date: 09/25/2013 05:22 PM > Subject: Re: [NTSysADM] Issue with WDS > Sent by: [email protected] > ------------------------------ > > > > option 67 - boot.wim <<-- this works just fine. > option 66 - FQDN of server and/or IP address of server <<-- neither worked > when client wasn't on same subnet as WDS server. FQDN worked when client on > same subnet. > > Kurt > > > On Wed, Sep 25, 2013 at 1:37 PM, Christopher Bodnar <* > [email protected]* <[email protected]>> wrote: > What is your DHCP Option 67 set to? > > *Christopher Bodnar* > Enterprise Architect I, Corporate Office of Technology:Enterprise > Architecture and Engineering Services Tel *610-807-6459* <610-807-6459> > 3900 Burgess Place, Bethlehem, PA 18017 > [email protected] > * > > The Guardian Life Insurance Company of America** > ** > **www.guardianlife.com* <http://www.guardianlife.com/> > > > > > > From: Kurt Buff <*[email protected]* <[email protected]>> > To: *[email protected]* <[email protected]> > Date: 09/25/2013 03:17 PM > Subject: Re: [NTSysADM] Issue with WDS > Sent by: > *[email protected]*<[email protected]> > ------------------------------ > > > > We have DHCP helpers on our layer3 swtich. The client gets the DHCP > settings in its subnet, and then tries to communicate with the WDS > server. If that WDS server is in a different subnet than the client, > the tftp request fails. It probably doesn't help that the client, DHCP > server and WDS server are all on different subnets. > > In fact, placing the client and the WDS server on the same subnet > fixed the problem. > > Kurt > > On Wed, Sep 25, 2013 at 5:11 AM, Mayo, Bill > <*[email protected]*<[email protected]>> > wrote: > > I know that in the Cisco switch environment, you have to use the "dhcp > helper" command for the WDS server when crossing subnets. > > > > -----Original Message----- > > From: *[email protected]* <[email protected]>[ > *mailto:[email protected]* <[email protected]>] > On Behalf Of Kurt Buff > > > Sent: Tuesday, September 24, 2013 8:32 PM > > To: *[email protected]* <[email protected]> > > Subject: Re: [NTSysADM] Issue with WDS > > > > Haven't done it before. Been more server/network focused, but JA got the > bug, and I encouraged him to try, so some of the troubleshooting fell to me. > > > > Pretty cool technology, but he's got some work to do in putting the > driver packs together. Better him than me... > > > > Kurt > > > > On Tue, Sep 24, 2013 at 5:22 PM, Art DeKneef > > <*[email protected]*<[email protected]>> > wrote: > >> It can be done if I remember correctly when I did this for a school > district over 5 years ago. > >> > >> But all of my latest installs have been for SMBs and have been on the > same subnet. > >> > >> Just started setting up an installation of WDS on Server 2012 R2 today. > >> > >> Art > >> > >> -----Original Message----- > >> From: *[email protected]* <[email protected]> > >> [ > *mailto:[email protected]* <[email protected]>] > On Behalf Of Kurt Buff > > >> Sent: Tuesday, September 24, 2013 4:07 PM > >> To: *[email protected]* <[email protected]> > >> Subject: Re: [NTSysADM] Issue with WDS > >> > >> It's an initial install of WDS. > >> > >> Turns out the problem goes away if WDS server and client are in the > same subnet. > >> > >> I did some googling regarding tftp across different subnets, and did > see some entries regarding reg entries, but none regarding hotfixes. > >> I'll pursue that if we want to keep clients and server on different > subnets. > >> > >> Kurt > >> > >> On Tue, Sep 24, 2013 at 3:44 PM, Art DeKneef > >> <*[email protected]*<[email protected]>> > wrote: > >>> Has it worked before and doesn't with this machine or is this the > first time? > >>> > >>> Is the DHCP server initialized and authorized? > >>> > >>> Have all the WDS hotfixes been applied? There are some that pertain to > TFTP if memory serves me. > >>> > >>> Just a couple of thoughts off the top of my head. > >>> > >>> Art > >>> > >>> -----Original Message----- > >>> From: *[email protected]*<[email protected]> > >>> [ > *mailto:[email protected]* <[email protected]>] > On Behalf Of Kurt Buff > > >>> Sent: Tuesday, September 24, 2013 1:47 PM > >>> To: *[email protected]* <[email protected]> > >>> Subject: [NTSysADM] Issue with WDS > >>> > >>> All, > >>> > >>> Junior admin is having problems making this go. > >>> > >>> Config looks good to me after cursory inspection, but I've found an > error message being emitted by the WDS server to the laptop, which looks > like this: > >>> > >>> IP 192.168.9.10.69 > 192.168.24.69.2070: 22 ERROR EBADOP "Access > violation." > >>> > >>> This looks like a TFTP error from what I've found via Google. > >>> > *http://www.mwat.de/docs/tftp/w4/tftp/Tftp.html#EBADOP*<http://www.mwat.de/docs/tftp/w4/tftp/Tftp.html#EBADOP> > > >>> > >>> The laptop is a Dell E6420. > >>> > >>> The WDS server is a 2008R2 VM at 192.168.9.10, as shown above, and the > DHCP server is one of our DCs, also 2008R2, on the > *192.168.10.0/24*<http://192.168.10.0/24>subnet. > >>> > >>> Anyone seen anything like this and can give me a clue? > >>> > >>> Kurt > >>> > >>> > >>> > >>> > >> > >> > >> > >> > > > > > > > > ----------------------------------------- This message, and any > attachments to it, may contain information that is privileged, > confidential, and exempt from disclosure under applicable law. If the > reader of this message is not the intended recipient, you are notified that > any use, dissemination, distribution, copying, or communication of this > message is strictly prohibited. If you have received this message in error, > please notify the sender immediately by return e-mail and delete the > message and any attachments. Thank you. > > ----------------------------------------- This message, and any > attachments to it, may contain information that is privileged, > confidential, and exempt from disclosure under applicable law. If the > reader of this message is not the intended recipient, you are notified that > any use, dissemination, distribution, copying, or communication of this > message is strictly prohibited. If you have received this message in error, > please notify the sender immediately by return e-mail and delete the > message and any attachments. Thank you. > >
<<image/jpeg>>
<<image/jpeg>>
