Yes. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mayo, Bill Sent: Wednesday, September 25, 2013 5:11 PM To: [email protected] Subject: RE: [NTSysADM] Issue with WDS
I don't think I have done a good job of making myself clear, so I will try one more time. If you already understood what I was saying, sorry. What I am saying is that we had to put the IP address of the WDS server itself in the list of DHCP helpers. I am sure this was necessary for RIS, and I *think* it still holds true for WDS. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kurt Buff Sent: Wednesday, September 25, 2013 4:27 PM To: [email protected] Subject: Re: [NTSysADM] Issue with WDS Normal DHCP servers. Didn't want to stand up another one and deal with it. For now, we've isolated WDS and client on one subnet, and the DHCP server, which is a DC, remains on its original subnet, and it's working fine. Kurt On Wed, Sep 25, 2013 at 12:25 PM, Mayo, Bill <[email protected]> wrote: > Do you have DHCP helpers for your normal DHCP server or the WDS server > itself? My experience is that you need it for WDS itself (as well as normal > DHCP server), although I admit I could be confusing that with old RIS. That > came to mind because of the indication of it not working on different > subnets. If you are already setup that way, I don't know of anything else > right off. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Kurt Buff > Sent: Wednesday, September 25, 2013 3:14 PM > To: [email protected] > Subject: Re: [NTSysADM] Issue with WDS > > 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]> > 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] >> [mailto:[email protected]] On Behalf Of Kurt Buff >> Sent: Tuesday, September 24, 2013 8:32 PM >> To: [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]> 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] >>> [mailto:[email protected]] On Behalf Of Kurt Buff >>> Sent: Tuesday, September 24, 2013 4:07 PM >>> To: [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]> 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 >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >> > >
