Re: Win2k3 and Slow Logons
From: Daniel Olinger (daniel.olinger_at_gmail.com)
Date: 12/07/04
- Next message: ed: "no dns servers configured for local system"
- Previous message: Mike Carter: "Windows 2003 Internal domain name same as FQDN"
- In reply to: Herb Martin: "Re: Win2k3 and Slow Logons"
- Next in thread: Herb Martin: "Re: Win2k3 and Slow Logons"
- Reply: Herb Martin: "Re: Win2k3 and Slow Logons"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 07 Dec 2004 08:51:18 -0800
Herb Martin wrote:
> <anonymous@discussions.microsoft.com> wrote in message
> news:185501c4dbca$f2169720$a301280a@phx.gbl...
>
>>Ok, I have taken some screenshots of various things
>>concerning my issue. Hopefully you guys can figure out my
>>problem with these. I have shots of the TCP/IP properties,
>>various DNS settings from the server and my router set up.
>>If you guys feel you need anymore, please let me know.
>>
>>You can browse the index of pics here:
>>
>>http://www.thevoiceless.net/dns/
>>
>
>
> This setup will not work correctly and reliably for you.
>
> This type of router cannot really work for AD clients and
> serves, ever. It can be the forwarder (which you have set)
> for internal DNS servers, but it must NOT be listed on any
> DNS clients, including DCs and other servers, NIC-IP
> settings (as you have it.)
>
> First, to the router: you need a router which can be a
> secondary -- this one (probably) does not do that from
> what I can see.
>
> If it could function as a Secondary DNS server this could
> work by making it a secondary to your internal AD DNS
> zone/domain, e.g., yourcompany.com.
>
> As it much not be listed on the IP properties of any machine
> you must change (at least) two things:
>
> 1) On the DC (and any other manual IP assignment, you
> must remove it from the NIC->IP client DNS settings
> The DC must ONLY specific itself or other internal
> DNS servers.
>
> 2) Since it is being used as your DHCP server to hand out
> IP addresses and configuration, it must NOT list itself
> in the setup it gives to clients, but rather list ONLY the
> INTERNAL DNS servers that know about your internal
> Domain/zone.
>
> The problem is that any client that uses this router directly
> will no nothing about the internal DNS names you need to
> resolve -- and to register, even you DC is set (incorrectly)
> this way and will not register itself with the internal DNS
> server domain/zone.
>
> Even trying to specify both an internal and this (external)
> router-DNS server will NOT work reliably.
>
> You must either install another DNS server internally
> or do without fault tolerance when the DC is down.
>
> There are DNS servers than can run on workstations if
> cost is an issue.
>
> Otherwise, you must manually make such changes if you
> only have one or two machines and want DNS to work
> then the DC-DNS server is down for most than a few
> minutes.
>
>
>
One more thing, how about these online 'Primary/Secondary' DNS services?
Could that be a possibility I can look into?
- Next message: ed: "no dns servers configured for local system"
- Previous message: Mike Carter: "Windows 2003 Internal domain name same as FQDN"
- In reply to: Herb Martin: "Re: Win2k3 and Slow Logons"
- Next in thread: Herb Martin: "Re: Win2k3 and Slow Logons"
- Reply: Herb Martin: "Re: Win2k3 and Slow Logons"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
