XP client cannot join domain in other VLAN

I have 4 VLANs in my office. My Win2003 Standard server is
on VLAN1. When my XP clients are in VLAN1, they can joined
the domain. However, when i move the PCs to other VLANs,
and making changes to the IP settings correspondingly, they
cannot find the domain server anymore. I will get an "rpc
server is unavaliable" error after 5mins. Routing between
the vlans is done by a Cisco 4506 core switch which support
layer 3. Pls advise


Also, our corporate DNS server with like "comp.com.au" Can
I configure all the workstation to keep the DNS suffix sas
the above and still have acces to my server? Do I need to
use "comp.local"?

Thanks in advance to all

The Active Directory DNS on the DC must be the DNS that all machines use.
Other DNS Servers not related the Active Directory are used by including
them in the Forwarder's List in the AD DNS Server.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"julian" <(E-Mail Removed)> wrote in message
news:1771401c4497b$4c5c50e0$(E-Mail Removed)...
> I have 4 VLANs in my office. My Win2003 Standard server is
> on VLAN1. When my XP clients are in VLAN1, they can joined
> the domain. However, when i move the PCs to other VLANs,
> and making changes to the IP settings correspondingly, they
> cannot find the domain server anymore. I will get an "rpc
> server is unavaliable" error after 5mins. Routing between
> the vlans is done by a Cisco 4506 core switch which support
> layer 3. Pls advise
>
>
> Also, our corporate DNS server with like "comp.com.au" Can
> I configure all the workstation to keep the DNS suffix sas
> the above and still have acces to my server? Do I need to
> use "comp.local"?
>
> Thanks in advance to all

As Phillip said, the clients use DNS and its SRV records to log on. To do
this properly, their DNS settings must point to your local DNS server which
contains these records. If you expand your DNS you will see these records
(starting with an underscore) which allow clients to find AD services like
netlogon. If they are not there (or are not found because the DNS setting is
wrong), you are trying to logon using the Netbios name of the server, and
that will fail in a segmented network without WINS.

So make sure that the entries are in DNS, and ensure that your clients
point to the correct DNS server to find them.

"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> The Active Directory DNS on the DC must be the DNS that all machines use.
> Other DNS Servers not related the Active Directory are used by including
> them in the Forwarder's List in the AD DNS Server.
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "julian" <(E-Mail Removed)> wrote in message
> news:1771401c4497b$4c5c50e0$(E-Mail Removed)...
> > I have 4 VLANs in my office. My Win2003 Standard server is
> > on VLAN1. When my XP clients are in VLAN1, they can joined
> > the domain. However, when i move the PCs to other VLANs,
> > and making changes to the IP settings correspondingly, they
> > cannot find the domain server anymore. I will get an "rpc
> > server is unavaliable" error after 5mins. Routing between
> > the vlans is done by a Cisco 4506 core switch which support
> > layer 3. Pls advise
> >
> >
> > Also, our corporate DNS server with like "comp.com.au" Can
> > I configure all the workstation to keep the DNS suffix sas
> > the above and still have acces to my server? Do I need to
> > use "comp.local"?
> >
> > Thanks in advance to all
>
>

Phillip,

Do you mean my PCs must be in the same domain as the DC.
Could you provide me info.

(E-Mail Removed)
>-----Original Message-----
>The Active Directory DNS on the DC must be the DNS that
all machines use.
>Other DNS Servers not related the Active Directory are
used by including
>them in the Forwarder's List in the AD DNS Server.
>
>
>--
>
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>
>"julian" <(E-Mail Removed)> wrote in message
>news:1771401c4497b$4c5c50e0$(E-Mail Removed)...
>> I have 4 VLANs in my office. My Win2003 Standard server
is
>> on VLAN1. When my XP clients are in VLAN1, they can
joined
>> the domain. However, when i move the PCs to other
VLANs,
>> and making changes to the IP settings correspondingly,
they
>> cannot find the domain server anymore. I will get
an "rpc
>> server is unavaliable" error after 5mins. Routing
between
>> the vlans is done by a Cisco 4506 core switch which
support
>> layer 3. Pls advise
>>
>>
>> Also, our corporate DNS server with like "comp.com.au"
Can
>> I configure all the workstation to keep the DNS suffix
sas
>> the above and still have acces to my server? Do I need
to
>> use "comp.local"?
>>
>> Thanks in advance to all
>
>
>.
>

Your subject says that the XP machines can not join the Domain from another
subnet. I said *all* your machines must use the AD DNS server (not some
other one) or they won't be able to find the DC while in other subnets
because they cannot "broadcast" to find it. Broadcasts don't cross routers.
Wether it is a VLAN or hardwired Subnet is not relevant, the principle is
the same.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


<(E-Mail Removed)> wrote in message
news:1a41201c44e3b$aa0bbef0$(E-Mail Removed)...
> Do you mean my PCs must be in the same domain as the DC.
> Could you provide me info.
>
> (E-Mail Removed)
> >-----Original Message-----
> >The Active Directory DNS on the DC must be the DNS that
> all machines use.
> >Other DNS Servers not related the Active Directory are
> used by including
> >them in the Forwarder's List in the AD DNS Server.