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]> 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] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Tuesday, September 24, 2013 1:47 PM > To: [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 > > 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 subnet. > > Anyone seen anything like this and can give me a clue? > > Kurt > > > >
