Scenario was that DHCP server (a DC) was on subnet A, the WDS server was on subnet B, and the client was on subnet C.
WDS/network config wasn't working. Moved WDS server to subnet C, and it started working. I then went to Montana. Of course, when I came back, it had stopped working. I've rifled through this thread again, and forwarded on the relevant bits to junior admin, and we'll work on this some more tomorrow. Scenario will be DHCP server on subnet A, WDS server and client on subnet C. Should be easier this time around. Kurt On Tue, Oct 1, 2013 at 4:19 PM, Michael B. Smith <[email protected]> wrote: > What was the issue? I was out of the country for a couple of weeks, until > Sunday... > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Tuesday, October 1, 2013 7:05 PM > To: [email protected] > Subject: Re: [NTSysADM] Issue with WDS > > Coming back to this after a bit of time off in tromping about in Montana - > sorely needed... > > On Wed, Sep 25, 2013 at 2:11 PM, Mayo, Bill <[email protected]> > wrote: >> 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. > > Uh - a *list* of DHCP helper addresses? Hmmm.... Interesting. I see that I > can stack multiple 'ip helper-address ip.add.re.ss' entries on a VLAN. I did > not know that before just now. Fascinating. Never had a reason to look at > that before. > > That, plus the link from Mr. Brothwell, has clarified a few things. > > Thanks. > > Kurt > >
