Not connecting to Domain

[Guest]

I need help on this little thing. A few Pc's that we have on a school network
will not join to the domain. It see's that it is connected to a network as
the two computers in the corner are plashin but they just won't join to the
domain, any idea's?

 

[Lanwench [MVP - Exchange]]

I need help on this little thing. A few Pc's that we have on a school
network will not join to the domain. It see's that it is connected to
a network as the two computers in the corner are plashin

What is "plashin" ?

but they
just won't join to the domain, any idea's?

You'll have to provide a lot more detail in order to get help, I'm afraid.
E.g.,

I presume you're using XP Pro boxes (not Home or MCE), and are using AD ?
How are you trying to do this, and what errors are you getting?
Are you using DHCP, is your DNS configured properly (no external/public IPs
specified for any client or server in AD)?
Can you ping your DC by name?
Are you logging in as an administrator?

....etc.

Help us to help you:
http://www.dts-l.org/goodpost.htm



[Hope you won't take offense at this, but "sees" and "ideas" do not have
apostrophes. Apostrophes connote the possessive, or a contraction. Spelling,
grammar, and clear communication do matter, even in usenet. ;-) ]

 

[Guest]

Hello Lanwench

Thank you for your reply and I apologise for the terrible grammar and
spelling in the last post – to much haste on my part to get the post written.

The machines are all running windows XP Professional with service pack 2.
All the machines are in active directory under ‘computers’. The IP is set to
static. Logging in as administrator I can ping the server by IP but not by
name on the affected PCs.

The odd thing is this has suddenly happened on two machines in a network of
30, with no other PCs reporting the same problem. Before that the above setup
was working fine. Nothing has been changed on the two affected machines with
no software installed, nothing configured differently or tweaked.

Any help with matter would be greater appreciated.

I need help on this little thing. A few Pc's that we have on a school
network will not join to the domain. It see's that it is connected to
a network as the two computers in the corner are plashin

What is "plashin" ?

but they
just won't join to the domain, any idea's?

You'll have to provide a lot more detail in order to get help, I'm afraid.
E.g.,

I presume you're using XP Pro boxes (not Home or MCE), and are using AD ?
How are you trying to do this, and what errors are you getting?
Are you using DHCP, is your DNS configured properly (no external/public IPs
specified for any client or server in AD)?
Can you ping your DC by name?
Are you logging in as an administrator?

....etc.

Help us to help you:
http://www.dts-l.org/goodpost.htm



[Hope you won't take offense at this, but "sees" and "ideas" do not have
apostrophes. Apostrophes connote the possessive, or a contraction. Spelling,
grammar, and clear communication do matter, even in usenet. ;-) ]

 

[Bob Willard]

Hello Lanwench

Thank you for your reply and I apologise for the terrible grammar and
spelling in the last post – to much haste on my part to get the post written.

The machines are all running windows XP Professional with service pack 2.
All the machines are in active directory under ‘computers’. The IP is set to
static. Logging in as administrator I can ping the server by IP but not by
name on the affected PCs.

The odd thing is this has suddenly happened on two machines in a network of
30, with no other PCs reporting the same problem. Before that the above setup
was working fine. Nothing has been changed on the two affected machines with
no software installed, nothing configured differently or tweaked.

Any help with matter would be greater appreciated.


:

I need help on this little thing. A few Pc's that we have on a school
network will not join to the domain. It see's that it is connected to
a network as the two computers in the corner are plashin

What is "plashin" ?

but they
just won't join to the domain, any idea's?

You'll have to provide a lot more detail in order to get help, I'm afraid.
E.g.,

I presume you're using XP Pro boxes (not Home or MCE), and are using AD ?
How are you trying to do this, and what errors are you getting?
Are you using DHCP, is your DNS configured properly (no external/public IPs
specified for any client or server in AD)?
Can you ping your DC by name?
Are you logging in as an administrator?

....etc.

Help us to help you:
http://www.dts-l.org/goodpost.htm



[Hope you won't take offense at this, but "sees" and "ideas" do not have
apostrophes. Apostrophes connote the possessive, or a contraction. Spelling,
grammar, and clear communication do matter, even in usenet. ;-) ]

When PING by number works but PING by name fails, it usually indicates a
problem with DNS, the name=>number translator service for your network.
Check the DNS settings, by eyeball and by comparing those settings on the
failing PCs with those on working PCs. Since you don't use DHCP, you must
also set DNS by hand.

If you don't spot a problem with the DNS settings, the next step I'd suggest
is to temporarily disable or remove all firewall and AV apps from those PCs,
and see if that fixes it; if so, you will know what app is the culprit.

And, since you use a M$ OS, boot three times while wearing a grass skirt and
holding chicken bones in your left hand.

 

[Lanwench [MVP - Exchange]]

Hello Lanwench

Thank you for your reply and I apologise for the terrible grammar and
spelling in the last post - to much haste on my part to get the post
written.

No worries - and I'm a bit of a crank, I know.

The machines are all running windows XP Professional with service
pack 2. All the machines are in active directory under 'computers'.
The IP is set to static.

Why statics? DHCP is the way to go - and if you have specific computers that
must, for some reason, have non-changing IP addresses, give them DHCP
reservations.

Logging in as administrator I can ping the
server by IP but not by name on the affected PCs.

This points to DNS problems, as the other reply stated.

The odd thing is this has suddenly happened on two machines in a
network of 30, with no other PCs reporting the same problem. Before
that the above setup was working fine. Nothing has been changed on
the two affected machines with no software installed, nothing
configured differently or tweaked.

Any help with matter would be greater appreciated.

In AD, all computers/servers *must* specify the internal (usually
AD-integrated) DNS server - if you have only one DC, specify that server's
LAN IP. Do not use any public/external IP addresses. The DNS server itself
should be configured with forwarders to your ISP's DNS servers for external
name resolution.

I need help on this little thing. A few Pc's that we have on a
school network will not join to the domain. It see's that it is
connected to a network as the two computers in the corner are
plashin

What is "plashin" ?

but they
just won't join to the domain, any idea's?

You'll have to provide a lot more detail in order to get help, I'm
afraid. E.g.,

I presume you're using XP Pro boxes (not Home or MCE), and are using
AD ? How are you trying to do this, and what errors are you getting?
Are you using DHCP, is your DNS configured properly (no
external/public IPs specified for any client or server in AD)?
Can you ping your DC by name?
Are you logging in as an administrator?

....etc.

Help us to help you:
http://www.dts-l.org/goodpost.htm



[Hope you won't take offense at this, but "sees" and "ideas" do not
have apostrophes. Apostrophes connote the possessive, or a
contraction. Spelling, grammar, and clear communication do matter,
even in usenet. ;-) ]

 

[Guest]

Thanks for your help. I will try your sugguestions and let you know the
outcome.

Mark

Hello Lanwench

Thank you for your reply and I apologise for the terrible grammar and
spelling in the last post - to much haste on my part to get the post
written.

No worries - and I'm a bit of a crank, I know.

The machines are all running windows XP Professional with service
pack 2. All the machines are in active directory under 'computers'.
The IP is set to static.

Why statics? DHCP is the way to go - and if you have specific computers that
must, for some reason, have non-changing IP addresses, give them DHCP
reservations.

Logging in as administrator I can ping the
server by IP but not by name on the affected PCs.

This points to DNS problems, as the other reply stated.

The odd thing is this has suddenly happened on two machines in a
network of 30, with no other PCs reporting the same problem. Before
that the above setup was working fine. Nothing has been changed on
the two affected machines with no software installed, nothing
configured differently or tweaked.

Any help with matter would be greater appreciated.

In AD, all computers/servers *must* specify the internal (usually
AD-integrated) DNS server - if you have only one DC, specify that server's
LAN IP. Do not use any public/external IP addresses. The DNS server itself
should be configured with forwarders to your ISP's DNS servers for external
name resolution.

I need help on this little thing. A few Pc's that we have on a
school network will not join to the domain. It see's that it is
connected to a network as the two computers in the corner are
plashin

What is "plashin" ?


but they
just won't join to the domain, any idea's?

You'll have to provide a lot more detail in order to get help, I'm
afraid. E.g.,

I presume you're using XP Pro boxes (not Home or MCE), and are using
AD ? How are you trying to do this, and what errors are you getting?
Are you using DHCP, is your DNS configured properly (no
external/public IPs specified for any client or server in AD)?
Can you ping your DC by name?
Are you logging in as an administrator?

....etc.

Help us to help you:
http://www.dts-l.org/goodpost.htm



[Hope you won't take offense at this, but "sees" and "ideas" do not
have apostrophes. Apostrophes connote the possessive, or a
contraction. Spelling, grammar, and clear communication do matter,
even in usenet. ;-) ]