network access slower when member of a domain?

Hi,

I've a strange case.
When a computer is included in my Win 2003 domain, the network access appear
to be slower then if the computer is not in the domain (but in the local
network)

any idea?

how to improve the performance ?
or how to diagnose the problem?

thanks

Jerome.

In news:(E-Mail Removed),
Jéjé <(E-Mail Removed)> asked for help and I offered my
suggestions below:
> Hi,
>
> I've a strange case.
> When a computer is included in my Win 2003 domain, the network access
> appear to be slower then if the computer is not in the domain (but in
> the local network)
>
> any idea?
>
> how to improve the performance ?
> or how to diagnose the problem?
>
> thanks
>
> Jerome.

Without a discrete description of exactly what is "slower", my first guess
is that the logons take longer, (hanging on the applying settings or network
connections screen) which indicates to me a DNS configuration issue with AD.

If this applies to you, here are the AD & DNS rules:

1. Do not use your ISP's DNS addresses anywhere on any member server, domain
controller or client machines' IP properties. DNS addresses must only show
the internal DNS only. Otherwise, numerous issues WILL occur.

2. If you desire internet resolution, DNS will do that out of the box for
your clients. You can make it more efficient by configuring a forwarder. If
the option is grayed out, delete the Root zone. This article shows how to do
both:
http://support.microsoft.com/?id=300202

More info:
http://support.microsoft.com/?id=291382

If my assumptions were incorrect, I apologize, but I would like to ask of
you to please elaborate extensively on what is exactly going on to better
assist, provide an example, maybe even a screen shot, messages, Event ID
error messages (the Event ID #), etc.

Also, if you feel this did not help, can you post some info to better help
us help you out with, such as:
1. ipconfig /all from a client and from your DC
2. The DNS domain name of AD
3. The zonename in your Forward Lookup Zones in DNS

Thanks


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================

I found my computers slower specially when I access the internet (through
ISA Server) and during local network navigation.
the througput appear to be the same, but the first connections are slowers.

I've 1 DC (which is SBS 2003) (with DNS + AD + DHCP + Wins)
1 ISAServer

My DHCP options are:
* Route : ISA Server
* DNS: SBS Server
* WINS : SBS Server
* 046 option: 0x8 (h node)

I'll double check my DNS config


"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@ho tmail.com> a écrit dans le
message de news:(E-Mail Removed)...
> In news:(E-Mail Removed),
> Jéjé <(E-Mail Removed)> asked for help and I offered my
> suggestions below:
> > Hi,
> >
> > I've a strange case.
> > When a computer is included in my Win 2003 domain, the network access
> > appear to be slower then if the computer is not in the domain (but in
> > the local network)
> >
> > any idea?
> >
> > how to improve the performance ?
> > or how to diagnose the problem?
> >
> > thanks
> >
> > Jerome.
>
> Without a discrete description of exactly what is "slower", my first guess
> is that the logons take longer, (hanging on the applying settings or
network
> connections screen) which indicates to me a DNS configuration issue with
AD.
>
> If this applies to you, here are the AD & DNS rules:
>
> 1. Do not use your ISP's DNS addresses anywhere on any member server,
domain
> controller or client machines' IP properties. DNS addresses must only show
> the internal DNS only. Otherwise, numerous issues WILL occur.
>
> 2. If you desire internet resolution, DNS will do that out of the box for
> your clients. You can make it more efficient by configuring a forwarder.
If
> the option is grayed out, delete the Root zone. This article shows how to
do
> both:
> http://support.microsoft.com/?id=300202
>
> More info:
> http://support.microsoft.com/?id=291382
>
> If my assumptions were incorrect, I apologize, but I would like to ask of
> you to please elaborate extensively on what is exactly going on to better
> assist, provide an example, maybe even a screen shot, messages, Event ID
> error messages (the Event ID #), etc.
>
> Also, if you feel this did not help, can you post some info to better help
> us help you out with, such as:
> 1. ipconfig /all from a client and from your DC
> 2. The DNS domain name of AD
> 3. The zonename in your Forward Lookup Zones in DNS
>
> Thanks
>
>
> --
> Regards,
> Ace
>
> Please direct all replies ONLY to the Microsoft public newsgroups
> so all can benefit.
>
> This posting is provided "AS-IS" with no warranties or guarantees
> and confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft Windows MVP - Windows Server - Directory Services
>
> Security Is Like An Onion, It Has Layers
> HAM AND EGGS: A day's work for a chicken;
> A lifetime commitment for a pig.
> --
> =================================
>
>

"Jéjé" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> I found my computers slower specially when I access the internet (through
> ISA Server) and during local network navigation.
> the througput appear to be the same, but the first connections are
slowers.
>
> I've 1 DC (which is SBS 2003) (with DNS + AD + DHCP + Wins)
> 1 ISAServer
>
> My DHCP options are:
> * Route : ISA Server
> * DNS: SBS Server
> * WINS : SBS Server
> * 046 option: 0x8 (h node)
>
> I'll double check my DNS config
>
>
> "Ace Fekay [MVP]"
> <PleaseSubstituteMyActualFirstName&LastNameHere@ho tmail.com> a écrit dans
le
> message de news:(E-Mail Removed)...
> > In news:(E-Mail Removed),
> > Jéjé <(E-Mail Removed)> asked for help and I offered my
> > suggestions below:
> > > Hi,
> > >
> > > I've a strange case.
> > > When a computer is included in my Win 2003 domain, the network access
> > > appear to be slower then if the computer is not in the domain (but in
> > > the local network)
> > >
> > > any idea?
> > >
> > > how to improve the performance ?
> > > or how to diagnose the problem?
> > >
> > > thanks
> > >
> > > Jerome.
> >
> > Without a discrete description of exactly what is "slower", my first
guess
> > is that the logons take longer, (hanging on the applying settings or
> network
> > connections screen) which indicates to me a DNS configuration issue with
> AD.
> >
> > If this applies to you, here are the AD & DNS rules:
> >
> > 1. Do not use your ISP's DNS addresses anywhere on any member server,
> domain
> > controller or client machines' IP properties. DNS addresses must only
show
> > the internal DNS only. Otherwise, numerous issues WILL occur.
> >
> > 2. If you desire internet resolution, DNS will do that out of the box
for
> > your clients. You can make it more efficient by configuring a forwarder.
> If
> > the option is grayed out, delete the Root zone. This article shows how
to
> do
> > both:
> > http://support.microsoft.com/?id=300202
> >
> > More info:
> > http://support.microsoft.com/?id=291382
> >
> > If my assumptions were incorrect, I apologize, but I would like to ask
of
> > you to please elaborate extensively on what is exactly going on to
better
> > assist, provide an example, maybe even a screen shot, messages, Event ID
> > error messages (the Event ID #), etc.
> >
> > Also, if you feel this did not help, can you post some info to better
help
> > us help you out with, such as:
> > 1. ipconfig /all from a client and from your DC
> > 2. The DNS domain name of AD
> > 3. The zonename in your Forward Lookup Zones in DNS
> >
> > Thanks
> >
> >
> > --
> > Regards,
> > Ace
> >
> > Please direct all replies ONLY to the Microsoft public newsgroups
> > so all can benefit.
> >
> > This posting is provided "AS-IS" with no warranties or guarantees
> > and confers no rights.
> >
> > Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> > Microsoft Windows MVP - Windows Server - Directory Services
> >
> > Security Is Like An Onion, It Has Layers
> > HAM AND EGGS: A day's work for a chicken;
> > A lifetime commitment for a pig.
> > --
> > =================================
> >
> >
>
>

I would agree that it's probably DNS related. I had that issue when I
migrated some clients from Windows 2000 Pro to XP Pro. Solution was to set
up DNS on the server so that everyone pointed to the IP address of the DC
(including the NIC of the DC), and then set the forwards to point to the ISP
DNS. That resolved it for me.

I've controlled my config
and the config appear to be good.

I've just changed the config at my DC server himself and the isa server to
insure the usage of the right DNS server on these 2 computers.

I'll test it now

"Daniel Jaburg" <(E-Mail Removed)> a écrit dans le message de
news:ODH$(E-Mail Removed)...
>
> "Jéjé" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > I found my computers slower specially when I access the internet
(through
> > ISA Server) and during local network navigation.
> > the througput appear to be the same, but the first connections are
> slowers.
> >
> > I've 1 DC (which is SBS 2003) (with DNS + AD + DHCP + Wins)
> > 1 ISAServer
> >
> > My DHCP options are:
> > * Route : ISA Server
> > * DNS: SBS Server
> > * WINS : SBS Server
> > * 046 option: 0x8 (h node)
> >
> > I'll double check my DNS config
> >
> >
> > "Ace Fekay [MVP]"
> > <PleaseSubstituteMyActualFirstName&LastNameHere@ho tmail.com> a écrit
dans
> le
> > message de news:(E-Mail Removed)...
> > > In news:(E-Mail Removed),
> > > Jéjé <(E-Mail Removed)> asked for help and I offered my
> > > suggestions below:
> > > > Hi,
> > > >
> > > > I've a strange case.
> > > > When a computer is included in my Win 2003 domain, the network
access
> > > > appear to be slower then if the computer is not in the domain (but
in
> > > > the local network)
> > > >
> > > > any idea?
> > > >
> > > > how to improve the performance ?
> > > > or how to diagnose the problem?
> > > >
> > > > thanks
> > > >
> > > > Jerome.
> > >
> > > Without a discrete description of exactly what is "slower", my first
> guess
> > > is that the logons take longer, (hanging on the applying settings or
> > network
> > > connections screen) which indicates to me a DNS configuration issue
with
> > AD.
> > >
> > > If this applies to you, here are the AD & DNS rules:
> > >
> > > 1. Do not use your ISP's DNS addresses anywhere on any member server,
> > domain
> > > controller or client machines' IP properties. DNS addresses must only
> show
> > > the internal DNS only. Otherwise, numerous issues WILL occur.
> > >
> > > 2. If you desire internet resolution, DNS will do that out of the box
> for
> > > your clients. You can make it more efficient by configuring a
forwarder.
> > If
> > > the option is grayed out, delete the Root zone. This article shows how
> to
> > do
> > > both:
> > > http://support.microsoft.com/?id=300202
> > >
> > > More info:
> > > http://support.microsoft.com/?id=291382
> > >
> > > If my assumptions were incorrect, I apologize, but I would like to ask
> of
> > > you to please elaborate extensively on what is exactly going on to
> better
> > > assist, provide an example, maybe even a screen shot, messages, Event
ID
> > > error messages (the Event ID #), etc.
> > >
> > > Also, if you feel this did not help, can you post some info to better
> help
> > > us help you out with, such as:
> > > 1. ipconfig /all from a client and from your DC
> > > 2. The DNS domain name of AD
> > > 3. The zonename in your Forward Lookup Zones in DNS
> > >
> > > Thanks
> > >
> > >
> > > --
> > > Regards,
> > > Ace
> > >
> > > Please direct all replies ONLY to the Microsoft public newsgroups
> > > so all can benefit.
> > >
> > > This posting is provided "AS-IS" with no warranties or guarantees
> > > and confers no rights.
> > >
> > > Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> > > Microsoft Windows MVP - Windows Server - Directory Services
> > >
> > > Security Is Like An Onion, It Has Layers
> > > HAM AND EGGS: A day's work for a chicken;
> > > A lifetime commitment for a pig.
> > > --
> > > =================================
> > >
> > >
> >
> >
>
> I would agree that it's probably DNS related. I had that issue when I
> migrated some clients from Windows 2000 Pro to XP Pro. Solution was to
set
> up DNS on the server so that everyone pointed to the IP address of the DC
> (including the NIC of the DC), and then set the forwards to point to the
ISP
> DNS. That resolved it for me.
>
>

In news:(E-Mail Removed),
Jéjé <(E-Mail Removed)> asked for help and I offered my
suggestions below:
> I've controlled my config
> and the config appear to be good.
>
> I've just changed the config at my DC server himself and the isa
> server to insure the usage of the right DNS server on these 2
> computers.
>
> I'll test it now
>

Very good. Just insure all machines point to this DNS only. COnfigure a
forwarder to your ISP. This way, assuming you are using ISA as a web proxy,
DNS will forward out for Inernet resolution.


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================