Re: Not connecting to Domain

Mark Wilson wrote:
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.


"Lanwench [MVP - Exchange]" wrote:


Mark Wilson <MarkWilson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

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.
--
Cheers, Bob
.

Relevant Pages

  • Re: Windows 2K3 and Virtual Server 2005 guests NAT problem
    ... these machines are not able to connect to our ... internal network. ... If you want to have the two or three VMs on a private ... If you have configured DNS on the host and have set your vms to use this ...
    (microsoft.public.windows.server.networking)
  • Re: Windows 2K3 and Virtual Server 2005 guests NAT problem
    ... these machines are not able to connect to our ... internal network. ... Ethernet adapter "MS Loopback Adapter": ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.networking)
  • Re: [opensuse] Have a separate resolv.conf per interface
    ... I'm at a client and need to be on their network to access their ... but I want to be able to resolve machine names on their ... Can you not then specify just the DNS of the client? ... Their DNS boxes only serve to resolve names for internally hosted machines. ...
    (SuSE)
  • Re: Big problem....Big Question
    ... One primary difference is that in going into the DNS Server settings on ... > the machines that work and those that don't. ... Cannot login to the Network Domain after having added the ...
    (microsoft.public.win2000.dns)
  • Re: XP AND 2000
    ... There are around 14 PCs! ... The XP machines probably have the Windows Firewall on ... I came across a network setup with the following:- ...
    (microsoft.public.win2000.networking)
Loading