Re: Some xp clients very slow to boot

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

On 21 Apr, 17:38, "Ace Fekay [Microsoft Certified Trainer]"
<ace...@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Even if it is for ISCSI, it will still cause a problem because of the DNS
registration issues. If you have some clients that it is not happening to, I
am surprised, but think that they aer just happening to find the domain at
first shot, possibly because at first start up, the first DNS address was
being used for the query, and it found the domain, but then a round robin is
in place, and usually at first request, the first address is given, meaning
the internal interface.


Hi Ace,
first of all thanks for your help, I really appreciate it.

The NIC used for iscsi:
-has "client for MS networks", "network load balancing" and "File and
Printer sharing for MS networks" *disabled*
-in advanced TCP settings/DNS *doesn't* have the flag on "Register
this connection addresses in DNS".

Furthermore, in Network Connections/Advanced settings, the NIC that
connects to the LAN is at top of binding order.
Could this mitigate the issues you mention in having a multihomed DC?



.

Relevant Pages

  • RE: 2003 Group Policies not applying to XP
    ... can you confirm to me that the first dns on trouble-causing clients is your ... did you try using group policy results to check whether the clients get the ... So client machines with load it and other wont. ...
    (microsoft.public.windows.group_policy)
  • Re: -- force clients to get time from the server --
    ... The clients use 3 DNS but the first DNS name is the SBS DC. ... I tried to run NETDIAG command, ...
    (microsoft.public.win2000.security)