Windows DNS and Netware DNS Jim C <matt_hather[ at ]o2.co.uk> 6/11/2007 1:02:46 PM Hi. We currrently have a Netware 6.5 domain but will be installing AD soon to accomodate the move away from Groupwise and on to Exchange 2003. Both Netware and AD will be running side by side as AD is being used purely for Exchange. At the present time, all workstations have the Netware DNS server specified in their TCP settings. When we move over to exchange, they will obviously need these settings changing to the new AD DNS servers. Can a Windows stub zone be used to allow machines to resolve to DNS on the Netware domain?

Re: Windows DNS and Netware DNS "Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 6/11/2007 1:43:41 PM Read inline please. In news:1181566966.374375.241560[ at ]k79g2000hse.googlegroups.com, Jim C <matt_hather[ at ]o2.co.uk> typed: [Quoted Text] > Hi. > > We currrently have a Netware 6.5 domain but will be installing AD soon > to accomodate the move away from Groupwise and on to Exchange 2003. > Both Netware and AD will be running side by side as AD is being used > purely for Exchange. > > At the present time, all workstations have the Netware DNS server > specified in their TCP settings. When we move over to exchange, they > will obviously need these settings changing to the new AD DNS > servers. The way I read this, you seem to be saying that the client machines will not be members of the AD domain, correct? If this is the case, then it won't be necessary for the clients to use the Windows DNS because they will not actually be authenticating with AD for network resources. Users will still need to authenticate with Exchange just like any other external user would. If the users will be using Outlook 2003 to connect to their Exchange mailbox, you should set their accounts up in Outlook using RPC over HTTPS (You'll need to acquire an SSL cert) where they will need to enter their username and password when they start Outlook, just like they would with Outlook Web Access. > > Can a Windows stub zone be used to allow machines to resolve to DNS on > the Netware domain? You can use Stub zones, Secondary zones, or Forwarding. -- Best regards, Kevin D. Goodknecht Sr. [MVP] Hope This Helps =================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue, to respond directly to me remove the nospam. from my email address. =================================== http://www.lonestaramerica.com/ http://support.wftx.us/ http://message.wftx.us/ =================================== Use Outlook Express?... Get OE_Quotefix: It will strip signature out and more http://home.in.tum.de/~jain/software/oe-quotefix/ =================================== Keep a back up of your OE settings and folders with OEBackup: http://www.oehelp.com/OEBackup/Default.aspx ===================================

Re: Windows DNS and Netware DNS Jim C <matt_hather[ at ]o2.co.uk> 6/11/2007 2:20:07 PM On 11 Jun, 14:43, "Kevin D. Goodknecht Sr. [MVP]" <a...[ at ]nospam.WFTX.US> wrote: [Quoted Text] > Read inline please. > > Innews:1181566966.374375.241560[ at ]k79g2000hse.googlegroups.com, > Jim C <matt_hat...[ at ]o2.co.uk> typed: > > > Hi. > > > We currrently have a Netware 6.5 domain but will be installing AD soon > > to accomodate the move away from Groupwise and on to Exchange 2003. > > Both Netware and AD will be running side by side as AD is being used > > purely for Exchange. > > > At the present time, all workstations have the Netware DNS server > > specified in their TCP settings. When we move over to exchange, they > > will obviously need these settings changing to the new AD DNS > > servers. > > The way I read this, you seem to be saying that the client machines will not > be members of the AD domain, correct? > If this is the case, then it won't be necessary for the clients to use the > Windows DNS because they will not actually be authenticating with AD for > network resources. > Users will still need to authenticate with Exchange just like any other > external user would. If the users will be using Outlook 2003 to connect to > their Exchange mailbox, you should set their accounts up in Outlook using > RPC over HTTPS (You'll need to acquire an SSL cert) where they will need to > enter their username and password when they start Outlook, just like they > would with Outlook Web Access. > > > > > Can a Windows stub zone be used to allow machines to resolve to DNS on > > the Netware domain? > > You can use Stub zones, Secondary zones, or Forwarding. > > -- > Best regards, > Kevin D. Goodknecht Sr. [MVP] > Hope This Helps > > =================================== > When responding to posts, please "Reply to Group" > via your newsreader so that others may learn and > benefit from your issue, to respond directly to > me remove the nospam. from my email address. > ===================================http://www.lonestaramerica.com/http://support.wftx.us/http://message.wftx.us/ > =================================== > Use Outlook Express?... Get OE_Quotefix: > It will strip signature out and morehttp://home.in.tum.de/~jain/software/oe-quotefix/ > =================================== > Keep a back up of your OE settings and folders > with OEBackup:http://www.oehelp.com/OEBackup/Default.aspx > =================================== Sorry. All client machines will be members of the new AD domain. Sorry for not mentioning this in the original post. Matt