Re: Can Novell and Win2k3 Coexists

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Bob Grabbe (bgrabbe_at_umich.edu)
Date: 07/28/04


Date: Wed, 28 Jul 2004 08:39:18 -0400

You don't really have to use the MS dns server at all. When you dcpromo, you
can tell ad about your current dns servers instead. Just have all your
Windows machines point to it for dns resolution.
If you can get away without putting the Novell client on, you probably would
get better login times. For mapping drives to Novell servers, look at their
Native File Access. Using it in Domain mode would mean making a connection
between the Nds user id and the Ad user id, but to me this is a small price
to pay for getting rid of the ipx transport.

-- 
Bob Grabbe
bgrabbe@umich.edu
"Michael Kleef [MSFT]" <mkleef@online.microsoft.com> wrote in message
news:edtGWNHdEHA.2268@TK2MSFTNGP12.phx.gbl...
> Yes they can co-exist.
>
> 1.  Create a DNS server upon DCPROMO and have it just be used by AD and
not
> affect any Novell stuff?
> Yes. Though watch out if your tree's are named the same. Novell now
finally
> uses DNS for NDS tree lookup... so if you have an nds tree named Company
and
> you append a DNS suffix and that namespace clashes with the DNS provided
in
> Windows you can get issues. Call your AD directory something else like
> companyad.company.com
>
> 2.  Once we put the actual DNS servers in the connection setup for the
NIC,
> will that cause any issues?
> If they are pointing to a Windows DNS then you can do a conditional
> forwarder to any Novell based DNS services that you have and a default
> forwarder out to the internet if you want. Again, make sure that the
> namespaces for DNS are different or you get nasty DNS clashes because each
> will be the SOA and wont believe the other.
>
> 3.  Can we put the corporate DNS as a forwarder without it causing any
> issues with the current DSN?
> As a forwarder from the Windows DNS? If so then definately yes.
>
> Are you installing a Novell client on Citrix?
>
>
> Michael Kleef
> Microsoft
> (was a CNE5)
>
>
>
> "Trevor Jansen" <TrevorJansen@discussions.microsoft.com> wrote in message
> news:62BB1EBD-E3BA-4E7F-B4C0-CE76BB463CCC@microsoft.com...
> > Hi Clay,
> >
> > Same here . . a good working Novell 6.5 network and working with citrix
> > (the windows machines are still placed in workgroups)
> > now i want to set up a windows domain (w2k3) specialy for citrix, so not
> > messing with Novell and our Linux NDS  . . . ;-)
> >
> > Did you have the solutuions also for me . . . ??
> >
> > with regards
> > Trevor Jansen
> > SRON- Utrecht
> > The Netherlands
> >
> > "Clay Black" wrote:
> >
> >> We currently have a Novell 6/5 network.  We want to install a AD domain
> >> on
> >> the network to overcome some issues with Citrix.  We do not want to
> >> migrate,
> >> we just want to have both.  Since AD needs a DNS server, and we don't
> >> want
> >> to mess with the corporate one, can we:
> >>
> >> 1.  Create a DNS server upon DCPROMO and have it just be used by AD and
> >> not
> >> affect any Novell stuff?
> >>
> >> 2.  Once we put the actual DNS servers in the connection setup for the
> >> NIC,
> >> will that cause any issues?
> >>
> >> 3.  Can we put the corporate DNS as a forwarder without it causing any
> >> issues with the current DSN?
> >>
> >> We want this to be transparent to the Novell system, since it really
has
> >> nothing to do with Novell and we do not want any type of connectivity
> >> between the two NOS'.  Since Citrix will only be serving up web pages
for
> >> access, any other type of access is not needed.  We will be manually
> >> enter
> >> users on the AD side for Citrix to control access.
> >>
> >> TIA for any help.
> >>
> >> Clay
> >>
> >>
> >>
>
>


Relevant Pages

  • Re: Kindly Advice - NT to Windows 2003 domain Upgrade
    ... We are proposing to Migrate from Windows NT to 2003 Active Directory. ... The campuses are primarily on Novell NDS ... Novell Account manager works. ... DNS servers are currently on Novell and even the NT domains use the DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Group Policy and performance during logon procces from client
    ... Note that there are some problems regarding to the use of FW in the Windows XP machine, make sure that the FW are configured correctly with GPO. ... Assuming DNS AD Integrated Zone ... Do not place the ISP DNS server or any other DNS on the client or DNS Server NIC properties, ...
    (microsoft.public.windows.server.active_directory)
  • RE: In-place upgrade to AD 2003
    ... point to itself as the primary DNS server. ... During the upgrade, name the internal DNS name different from Public DNS ... When you set up a new Windows 2003 DC and transfer the FSMO roles, ...
    (microsoft.public.windows.server.migration)
  • Re: DNS cache poisoning?
    ... Windows DNS and thanks to numerous others for reporting. ... On Windows 2000 SP3 and above, the DNS server DOES protect against DNS ... BIND4 and BIND8 forwarders will not filter the cache poisoning attack to ...
    (Incidents)
  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... AD-Integrated DNS does not do zone transfers between the ... your DNS server will bypass ...
    (microsoft.public.windows.server.active_directory)