can't join xp sp2 to ad domain

Hi,
When trying to join a xp sp2 client to a server 2003 domain message appears
"the foloowing error occurred attempting to join the domain-arithmetic result
exceeded 32 bits'.
firewall has been disabled on the xp machine and can map to the server.
any suggestions?
thanks

In news:F4DA09B0-ADFA-4E31-8255-(E-Mail Removed),
GPRookie <(E-Mail Removed)> stated, which I commented on
below:
> Hi,
> When trying to join a xp sp2 client to a server 2003 domain message
> appears "the foloowing error occurred attempting to join the
> domain-arithmetic result exceeded 32 bits'.
> firewall has been disabled on the xp machine and can map to the
> server.
> any suggestions?
> thanks

Are you using Kixstart for scripts? That error used to come up years ago
with that, but I haven't seen this one in years. So I'll ask about your
current config: What DNS address is being used on the XP Pro machine and the
server? Only the internal DNS I assume. Or is there an ISP's DNS in there
too? If so, that will cause major issues.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If you are having difficulty in reading or finding responses to your post,
instead of the website you are using, if I may suggest to use OEx (Outlook
Express or any other newsreader of your choosing), and configure a newsgroup
account, pointing to news.microsoft.com. This is a direct link into the
Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
account with your ISP. With OEx, you can easily find your post, track
threads, cross-post, and sort by date, poster's name, watched threads or
subject.

Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.
=================================

Hi thanks for responding,
It's a new network i've recently put together at home(haven't had this
problem before, maybe i've done something different this time..?) so no
scripts yet.
the 2003 server has 2 NICs(1 connected directly to cable modem, and 1
connected directly to the xp client).
xp client dhcp and dns settings set to automatic.
both pcs can access internet ok.
ipconfig on xp shows internal ip and 2003 server as the default gateway.

Thanks.
"Ace Fekay [MVP]" wrote:

> In news:F4DA09B0-ADFA-4E31-8255-(E-Mail Removed),
> GPRookie <(E-Mail Removed)> stated, which I commented on
> below:
> > Hi,
> > When trying to join a xp sp2 client to a server 2003 domain message
> > appears "the foloowing error occurred attempting to join the
> > domain-arithmetic result exceeded 32 bits'.
> > firewall has been disabled on the xp machine and can map to the
> > server.
> > any suggestions?
> > thanks
>
> Are you using Kixstart for scripts? That error used to come up years ago
> with that, but I haven't seen this one in years. So I'll ask about your
> current config: What DNS address is being used on the XP Pro machine and the
> server? Only the internal DNS I assume. Or is there an ISP's DNS in there
> too? If so, that will cause major issues.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> If you are having difficulty in reading or finding responses to your post,
> instead of the website you are using, if I may suggest to use OEx (Outlook
> Express or any other newsreader of your choosing), and configure a newsgroup
> account, pointing to news.microsoft.com. This is a direct link into the
> Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
> account with your ISP. With OEx, you can easily find your post, track
> threads, cross-post, and sort by date, poster's name, watched threads or
> subject.
>
> Not sure how? It's easy:
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Windows Server Directory Services
> Microsoft Certified Trainer
> Assimilation Imminent. Resistance is Futile.
> Infinite Diversities in Infinite Combinations.
> =================================
>
>
>

What about the client's DNS setting? It should also point to the
server's private IP (ie the same IP as the default gateway). In AD, you use
DNS to find AD services such as netlogon. The DNS at your ISP will not have
these records.

Set the client (and the server itself) to use the server's private IP
for DNS. Then configure this local DNS server to forward to a public DNS
(such as your ISP).

GPRookie wrote:
> Hi thanks for responding,
> It's a new network i've recently put together at home(haven't had this
> problem before, maybe i've done something different this time..?) so
> no scripts yet.
> the 2003 server has 2 NICs(1 connected directly to cable modem, and 1
> connected directly to the xp client).
> xp client dhcp and dns settings set to automatic.
> both pcs can access internet ok.
> ipconfig on xp shows internal ip and 2003 server as the default
> gateway.
>
> Thanks.
> "Ace Fekay [MVP]" wrote:
>
>> In news:F4DA09B0-ADFA-4E31-8255-(E-Mail Removed),
>> GPRookie <(E-Mail Removed)> stated, which I
>> commented on below:
>>> Hi,
>>> When trying to join a xp sp2 client to a server 2003 domain message
>>> appears "the foloowing error occurred attempting to join the
>>> domain-arithmetic result exceeded 32 bits'.
>>> firewall has been disabled on the xp machine and can map to the
>>> server.
>>> any suggestions?
>>> thanks
>>
>> Are you using Kixstart for scripts? That error used to come up years
>> ago with that, but I haven't seen this one in years. So I'll ask
>> about your current config: What DNS address is being used on the XP
>> Pro machine and the server? Only the internal DNS I assume. Or is
>> there an ISP's DNS in there too? If so, that will cause major issues.
>>
>> --
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> If you are having difficulty in reading or finding responses to your
>> post, instead of the website you are using, if I may suggest to use
>> OEx (Outlook Express or any other newsreader of your choosing), and
>> configure a newsgroup account, pointing to news.microsoft.com. This
>> is a direct link into the Microsoft Public Newsgroups, and it is
>> FREE and DOES NOT require a Usenet account with your ISP. With OEx,
>> you can easily find your post, track threads, cross-post, and sort
>> by date, poster's name, watched threads or subject.
>>
>> Not sure how? It's easy:
>> How to Configure OEx for Internet News
>> http://support.microsoft.com/?id=171164
>>
>> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
>> Microsoft MVP - Windows Server Directory Services
>> Microsoft Certified Trainer
>> Assimilation Imminent. Resistance is Futile.
>> Infinite Diversities in Infinite Combinations.
>> =================================

In news:(E-Mail Removed),
Bill Grant <not.available@online> stated, which I commented on below:
> What about the client's DNS setting? It should also point to the
> server's private IP (ie the same IP as the default gateway). In AD,
> you use DNS to find AD services such as netlogon. The DNS at your ISP
> will not have these records.
>
> Set the client (and the server itself) to use the server's private
> IP for DNS. Then configure this local DNS server to forward to a
> public DNS (such as your ISP).

Exactly what I was getting at too Bill! :-)

I wanted to see the ipconfig for that reason and to insure the domain is not
a single label name as well.

Alsom since this has dual NICs, it complicates it a bit, especially since it
is a DC (DCs shouldn't really be multihomed). Below is a repost for GPRookie
to help configure this DC to work properly with the two NICs, which is
probably causing the problem along with the DNS client entries. But
honestly, after reading this stuff below, it would be less overhead and
headache to buy an inexpensive Linksys router to perform NAT functionality
for the network instead of altering default DC functionality to make this
work.

_________________________
Honestly, multi-homed DCs are not recommended because of the associated
issues that can occur, as you've encountered. We usually recommend
purchasing an inexpensive Linksys, DLink, etc, Cable/DSL router to perform
NAT for you, take out the extra NIC off the DC, but still let the DC handle
DHCP (and not the router).

Since this DC is multi-homed, it requires additional configuration to
prevent the public interface addresses from being registered in DNS. This
creates a problem for internal clients locating AD to authenticate and find
other services and resources such as the Global Catalog, file sharing and
the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events to be
logged, authenticating to shares and printers, logging on takes forever,
among numerous other issues.

But if you like, there are some registry changes to eliminate the
registration of the external NIC. Here's the whole list of manual steps to
follow.

But believe me, it's much easier to just get a separate NAT device or
multihome a non-DC then having to alter the DC. - Good luck!

1. Insure that all the NICS only point to your internal DNS server(s) only
and none others, such as your ISP's DNS servers' IP addresses.

2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,
move the internal NIC (the network that AD is on) to the top of the binding
order (top of the list).

3. Disable the ability for the outer NIC to register. The procedure, as
mentioned, involves identifying the outer NIC's GUID number. This link will
show you how:
246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
NIC too):
http://support.microsoft.com/?id=246804

4. Disable NetBIOS on the outside NIC. That is performed by choosing to
disable NetBIOS in IP Properties, Advanced, and you will find that under the
"WINS" tab. You may want to look at step #3 in the article to show you how
to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Note: A standard Windows service, called the "Browser service", provides the
list of machines, workgroup and domain names that you see in "My Network
Places" (or the legacy term "Network Neighborhood"). The Browser service
relies on the NetBIOS service. One major requirement of NetBIOS service is a
machine can only have one name to one IP address. It's sort of a
fingerprint. You can't have two brothers named Darrell. A multihomed machine
will cause duplicate name errors on itself because Windows sees itself with
the same name in the Browse List (My Network Places), but with different
IPs. You can only have one, hence the error generated.

5. Disable the "File and Print Service" and disable the "MS Client Service"
on the outer NIC. That is done in NIC properties by unchecking the
respective service under the general properties page. If you need these
services on the outside NIC (which is unlikely), which allow other machines
to connect to your machine for accessing resource on your machine (shared
folders, printers, etc.), then you will probably need to keep them enabled.

6. Uncheck "Register this connection" under IP properties, Advanced
settings, "DNS" tab.

7. Delete the outer NIC IP address, disable Netlogon registration, and
manually create the required records

a. In DNS under the zone name, (your DNS domain name), delete the outer
NIC's IP references for the "LdapIpAddress". If this is a GC, you will need
to delete the GC IP record as well (the "GcIpAddress"). To do that, in the
DNS console, under the zone name, you will see the _msdcs folder. Under
that, you will see the _gc folder. To the right, you will see the IP address
referencing the GC address. That is called the GcIpAddress. Delete the IP
addresses referencing the outer NIC.

i. To stop these two records from registering that information,
use the steps provided in the links below:
Private Network Interfaces on a Domain Controller Are Registered in
DNShttp://support.microsoft.com/?id=295328

ii. The one section of the article that disables these records is
done with this registry entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Netlogon\Parameters
(Create this Multi-String Value under it):
Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress
GcIpAddress

iii. Here is more information on these and other Netlogon Service
records:
Restrict the DNS SRV resource records updated by the Netlogon service
[including GC]:
http://www.microsoft.com/technet/tre...o_rr_in_ad.asp

b. Then you will need to manually create these two records in DNS with
the IP addresses that you need for the DC. To create the LdapIpAddress,
create a new host under the domain, but leave the "hostname" field blank,
and provide the internal IP of the DC, which results in a record that looks
like:
(same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
purposes)

i. You need to also manually create the GcIpAddress as well, if
this is a GC. That would be under the _msdcs._gc SRV record under the zone.
It is created in the same fashion as the LdapIpAddress mentioned above.

8. In the DNS console, right click the server name, choose properties, then
under the "Interfaces" tab, force it only to listen to the internal NIC's IP
address, and not the IP address of the outer NIC.

9. Since this is also a DNS server, the IPs from all NICs will register,
even if you tell it not to in the NIC properties. See this to show you how
to stop that behavior (this procedure is for Windows 2000, but will also
work for Windows 2003):
275554 - The Host's A Record Is Registered in DNS After You Choose Not to
Register the Connection's Address:
http://support.microsoft.com/?id=275554

10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
not sure which
DNS to forward to until you've got the DNS address of your ISP. How to set a
forwarder?
Depending on your operating system,choose one of the following articles:

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
(How to configure a forwarder):
http://support.microsoft.com/d/id?=323380


<==*** Some additional reading ***==>
More links to read up and understand what is going on:

292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
unwanted IPs registering]:
http://support.microsoft.com/?id=292822

246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
Server 2003
http://support.microsoft.com/?id=246804

295328 - Private Network Interfaces on a Domain Controller Are Registered in
DNS
[also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent
private IP]:
http://support.microsoft.com/?id=295328

306602 - How to Optimize the Location of a DC or GC That Resides Outside of
a Client's
Site [Includes info LdapIpAddress and GcIpAddress information and the SRV
mnemonic values]:
http://support.microsoft.com/?id=306602

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003 (including how-to configure a forwarder):
http://support.microsoft.com/default...b;en-us;825036

291382 - Frequently asked questions about Windows 2000 DNS and Windows
Server 2003 DNS
http://support.microsoft.com/default...b;en-us;291382

296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

_________________________


Ace

I noticed I was having quite a few DNS related errors in the event log and I
couldn't be bothered trouble shooting anymore because I was a little
frustrated as I have set this same network a few times before with no
problems so I just reinstalled win2k3 and guess what?
It all works fine! I guess there was something wrong with the initial
install or something.
My network now looks like this....

Room 1 has the xp machine and cable modem connected to a hub which connects
the another hub/switch in room2 which then connects to the 2 NICs on the
win2k3 machine.

The xp machine is set with auto DHCP and DNS settings and ipconfig /all
shows it has an internal IP, gateway, DHCP and DNS is pointing to the
internal server.

The internal NIC on the server has a static IP and DNS pointing to it's own
DNS.
The external NIC on the server is set to auto IP with DNS pointing to it's
own DNS.

although it is all working fine now I was just wondering, does it make the
network/client pc performance any more efficient if I explicitly configure
the xp machine's DNS to point to the win2k3 server instead of having it on
auto detect?

I Appriciate the help guys.


"Ace Fekay [MVP]" wrote:

> In news:(E-Mail Removed),
> Bill Grant <not.available@online> stated, which I commented on below:
> > What about the client's DNS setting? It should also point to the
> > server's private IP (ie the same IP as the default gateway). In AD,
> > you use DNS to find AD services such as netlogon. The DNS at your ISP
> > will not have these records.
> >
> > Set the client (and the server itself) to use the server's private
> > IP for DNS. Then configure this local DNS server to forward to a
> > public DNS (such as your ISP).
>
> Exactly what I was getting at too Bill! :-)
>
> I wanted to see the ipconfig for that reason and to insure the domain is not
> a single label name as well.
>
> Alsom since this has dual NICs, it complicates it a bit, especially since it
> is a DC (DCs shouldn't really be multihomed). Below is a repost for GPRookie
> to help configure this DC to work properly with the two NICs, which is
> probably causing the problem along with the DNS client entries. But
> honestly, after reading this stuff below, it would be less overhead and
> headache to buy an inexpensive Linksys router to perform NAT functionality
> for the network instead of altering default DC functionality to make this
> work.
>
> _________________________
> Honestly, multi-homed DCs are not recommended because of the associated
> issues that can occur, as you've encountered. We usually recommend
> purchasing an inexpensive Linksys, DLink, etc, Cable/DSL router to perform
> NAT for you, take out the extra NIC off the DC, but still let the DC handle
> DHCP (and not the router).
>
> Since this DC is multi-homed, it requires additional configuration to
> prevent the public interface addresses from being registered in DNS. This
> creates a problem for internal clients locating AD to authenticate and find
> other services and resources such as the Global Catalog, file sharing and
> the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events to be
> logged, authenticating to shares and printers, logging on takes forever,
> among numerous other issues.
>
> But if you like, there are some registry changes to eliminate the
> registration of the external NIC. Here's the whole list of manual steps to
> follow.
>
> But believe me, it's much easier to just get a separate NAT device or
> multihome a non-DC then having to alter the DC. - Good luck!
>
> 1. Insure that all the NICS only point to your internal DNS server(s) only
> and none others, such as your ISP's DNS servers' IP addresses.
>
> 2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,
> move the internal NIC (the network that AD is on) to the top of the binding
> order (top of the list).
>
> 3. Disable the ability for the outer NIC to register. The procedure, as
> mentioned, involves identifying the outer NIC's GUID number. This link will
> show you how:
> 246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
> NIC too):
> http://support.microsoft.com/?id=246804
>
> 4. Disable NetBIOS on the outside NIC. That is performed by choosing to
> disable NetBIOS in IP Properties, Advanced, and you will find that under the
> "WINS" tab. You may want to look at step #3 in the article to show you how
> to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
> 296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
> [Registry Entry]:
> http://support.microsoft.com/?id=296379
>
> Note: A standard Windows service, called the "Browser service", provides the
> list of machines, workgroup and domain names that you see in "My Network
> Places" (or the legacy term "Network Neighborhood"). The Browser service
> relies on the NetBIOS service. One major requirement of NetBIOS service is a
> machine can only have one name to one IP address. It's sort of a
> fingerprint. You can't have two brothers named Darrell. A multihomed machine
> will cause duplicate name errors on itself because Windows sees itself with
> the same name in the Browse List (My Network Places), but with different
> IPs. You can only have one, hence the error generated.
>
> 5. Disable the "File and Print Service" and disable the "MS Client Service"
> on the outer NIC. That is done in NIC properties by unchecking the
> respective service under the general properties page. If you need these
> services on the outside NIC (which is unlikely), which allow other machines
> to connect to your machine for accessing resource on your machine (shared
> folders, printers, etc.), then you will probably need to keep them enabled.
>
> 6. Uncheck "Register this connection" under IP properties, Advanced
> settings, "DNS" tab.
>
> 7. Delete the outer NIC IP address, disable Netlogon registration, and
> manually create the required records
>
> a. In DNS under the zone name, (your DNS domain name), delete the outer
> NIC's IP references for the "LdapIpAddress". If this is a GC, you will need
> to delete the GC IP record as well (the "GcIpAddress"). To do that, in the
> DNS console, under the zone name, you will see the _msdcs folder. Under
> that, you will see the _gc folder. To the right, you will see the IP address
> referencing the GC address. That is called the GcIpAddress. Delete the IP
> addresses referencing the outer NIC.
>
> i. To stop these two records from registering that information,
> use the steps provided in the links below:
> Private Network Interfaces on a Domain Controller Are Registered in
> DNShttp://support.microsoft.com/?id=295328
>
> ii. The one section of the article that disables these records is
> done with this registry entry:
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Netlogon\Parameters
> (Create this Multi-String Value under it):
> Registry value: DnsAvoidRegisterRecords
> Data type: REG_MULTI_SZ
> Values: LdapIpAddress
> GcIpAddress
>
> iii. Here is more information on these and other Netlogon Service
> records:
> Restrict the DNS SRV resource records updated by the Netlogon service
> [including GC]:
> http://www.microsoft.com/technet/tre...o_rr_in_ad.asp
>
> b. Then you will need to manually create these two records in DNS with
> the IP addresses that you need for the DC. To create the LdapIpAddress,
> create a new host under the domain, but leave the "hostname" field blank,
> and provide the internal IP of the DC, which results in a record that looks
> like:
> (same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
> purposes)
>
> i. You need to also manually create the GcIpAddress as well, if
> this is a GC. That would be under the _msdcs._gc SRV record under the zone.
> It is created in the same fashion as the LdapIpAddress mentioned above.
>
> 8. In the DNS console, right click the server name, choose properties, then
> under the "Interfaces" tab, force it only to listen to the internal NIC's IP
> address, and not the IP address of the outer NIC.
>
> 9. Since this is also a DNS server, the IPs from all NICs will register,
> even if you tell it not to in the NIC properties. See this to show you how
> to stop that behavior (this procedure is for Windows 2000, but will also
> work for Windows 2003):
> 275554 - The Host's A Record Is Registered in DNS After You Choose Not to
> Register the Connection's Address:
> http://support.microsoft.com/?id=275554
>
> 10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
> not sure which
> DNS to forward to until you've got the DNS address of your ISP. How to set a
> forwarder?
> Depending on your operating system,choose one of the following articles:
>
> 300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
> http://support.microsoft.com/?id=300202&FR=1
>
> 323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
> (How to configure a forwarder):
> http://support.microsoft.com/d/id?=323380
>
>
> <==*** Some additional reading ***==>
> More links to read up and understand what is going on:
>
> 292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
> Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
> unwanted IPs registering]:
> http://support.microsoft.com/?id=292822
>
> 246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
> Server 2003
> http://support.microsoft.com/?id=246804
>
> 295328 - Private Network Interfaces on a Domain Controller Are Registered in
> DNS
> [also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent
> private IP]:
> http://support.microsoft.com/?id=295328
>
> 306602 - How to Optimize the Location of a DC or GC That Resides Outside of
> a Client's
> Site [Includes info LdapIpAddress and GcIpAddress information and the SRV
> mnemonic values]:
> http://support.microsoft.com/?id=306602
>
> 825036 - Best practices for DNS client settings in Windows 2000 Server and
> in Windows Server 2003 (including how-to configure a forwarder):
> http://support.microsoft.com/default...b;en-us;825036
>
> 291382 - Frequently asked questions about Windows 2000 DNS and Windows
> Server 2003 DNS
> http://support.microsoft.com/default...b;en-us;291382
>
> 296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
> [Registry Entry]:
> http://support.microsoft.com/?id=296379
>
> _________________________
>
>
> Ace
>
>
>

In news:942FD8BE-DDF8-4BA5-B71A-(E-Mail Removed),
GPRookie <(E-Mail Removed)> stated, which I commented on
below:
> I noticed I was having quite a few DNS related errors in the event
> log and I couldn't be bothered trouble shooting anymore because I was
> a little frustrated as I have set this same network a few times
> before with no problems so I just reinstalled win2k3 and guess what?
> It all works fine! I guess there was something wrong with the initial
> install or something.
> My network now looks like this....
>
> Room 1 has the xp machine and cable modem connected to a hub which
> connects the another hub/switch in room2 which then connects to the 2
> NICs on the win2k3 machine.
>
> The xp machine is set with auto DHCP and DNS settings and ipconfig
> /all shows it has an internal IP, gateway, DHCP and DNS is pointing
> to the internal server.
>
> The internal NIC on the server has a static IP and DNS pointing to
> it's own DNS.
> The external NIC on the server is set to auto IP with DNS pointing to
> it's own DNS.
>
> although it is all working fine now I was just wondering, does it
> make the network/client pc performance any more efficient if I
> explicitly configure the xp machine's DNS to point to the win2k3
> server instead of having it on auto detect?
>
> I Appriciate the help guys.

No prob for the help. DNS, whether statically set or acquired thru DHCP
doesn't make a difference. The only thing in an AD network, all machine MUST
only use the interla DNS server and not the ISP's, since the ISP's DNS does
not have any info about your internal private AD system, which is where AD
stores it's service and resource locations in.

:-)

Ace

excellent, exactly what i was thought.
Thanks for the assistance!


"Ace Fekay [MVP]" wrote:

> In news:942FD8BE-DDF8-4BA5-B71A-(E-Mail Removed),
> GPRookie <(E-Mail Removed)> stated, which I commented on
> below:
> > I noticed I was having quite a few DNS related errors in the event
> > log and I couldn't be bothered trouble shooting anymore because I was
> > a little frustrated as I have set this same network a few times
> > before with no problems so I just reinstalled win2k3 and guess what?
> > It all works fine! I guess there was something wrong with the initial
> > install or something.
> > My network now looks like this....
> >
> > Room 1 has the xp machine and cable modem connected to a hub which
> > connects the another hub/switch in room2 which then connects to the 2
> > NICs on the win2k3 machine.
> >
> > The xp machine is set with auto DHCP and DNS settings and ipconfig
> > /all shows it has an internal IP, gateway, DHCP and DNS is pointing
> > to the internal server.
> >
> > The internal NIC on the server has a static IP and DNS pointing to
> > it's own DNS.
> > The external NIC on the server is set to auto IP with DNS pointing to
> > it's own DNS.
> >
> > although it is all working fine now I was just wondering, does it
> > make the network/client pc performance any more efficient if I
> > explicitly configure the xp machine's DNS to point to the win2k3
> > server instead of having it on auto detect?
> >
> > I Appriciate the help guys.
>
> No prob for the help. DNS, whether statically set or acquired thru DHCP
> doesn't make a difference. The only thing in an AD network, all machine MUST
> only use the interla DNS server and not the ISP's, since the ISP's DNS does
> not have any info about your internal private AD system, which is where AD
> stores it's service and resource locations in.
>
> :-)
>
> Ace
>
>
>

In newsF9DDCA7-C811-4034-84E1-(E-Mail Removed),
GPRookie <(E-Mail Removed)> stated, which I commented on
below:
> excellent, exactly what i was thought.
> Thanks for the assistance!

No prob!
:-)