Re: unable to join to the domain with netbios name

Tech-Archive recommends: Speed Up your PC by fixing your registry

OM <om@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
addomin is the netbios name of the Active Directory.

OK.

The DC
automatically added addomain.domain.com as the primary DNS suffix when
it joined to the domain.

No, it shouldn't have. What you showed in the ipconfig /all indicates that
addomain.domain.com is the domain name.

From the server itself, if you ping the server's NetBIOS name, what FQDN
does it return?

By default, the dhcp server assigns
domain.com as the DNS suffix for all dhcp clients on the network. w

Only because someone set it up to do that.

As
I mentioned before, all XP machines are able to join to the domain
with the Netbios name but not Vista machines (work if I use FQDN).

We are educational organization and have a qualified class B address
assigned.

OK, but that still doesn't mean you need them internally. I understand
that's not your department, but it's probably a bad choice unless there's
some compelling requirement.

I can't tell why we use public IP addresses and why there
have so many DNS servers as I am not the network administrator. I am
only responsible for the Windows servers.

I'd ask them. This does impact what you work on.

BTY, we don't use Windows DNS server in our network, we use BIND
instead. Would it make a difference?

You probably should be using AD-integrated DNS, but you don't necessarily
have to, as long as your DNS server supports dynamic updates.

If you open AD Domains and Trusts, what is the AD domain name listed there?
Whatever it is, is the primary DNS suffix you should have on all servers and
clients.


Lanwench [MVP - Exchange] wrote:
OM <om@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Vista PC

Windows IP Configuration

Host Name . . . . . . . . . . . . : pcs05
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : domain.com
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : 00-11-11-47-D4-68
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 155.50.106.93(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.224.0
Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2008
8:52:53 AM Lease Expires . . . . . . . . . . : Wednesday, October
15, 2008 8:52:53 AM
Default Gateway . . . . . . . . . : 155.50.100.18
DHCP Server . . . . . . . . . . . : 155.50.100.186
DNS Servers . . . . . . . . . . . : 155.50.100.19
155.50.100.68
155.50.106.82
155.50.127.50
155.50.113.101
NetBIOS over Tcpip. . . . . . . . : Enabled


Windows 2003 DC

Windows IP Configuration

Host Name . . . . . . . . . . . . : addc
Primary Dns Suffix . . . . . . . : addomain.domain.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : addomain.domain.com
domain.com

Ethernet adapter Local Area Connection:


Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-16-3E-00-00-21
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 155.50.100.220
Subnet Mask . . . . . . . . . . . : 255.255.224.0
Default Gateway . . . . . . . . . : 155.50.100.18
DNS Servers . . . . . . . . . . . : 155.50.100.19
155.50.100.68


OK - you've got addomain.domain.com as the DNS suffix on your DC, but
domain.com on the client.
Also, why are you using public IPs on your LAN, and why so many DNS
server IPs on the client?


Lanwench [MVP - Exchange] wrote:
OM <om@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi

I am unable to join my Vista business machine to a windows 2003
domain using netbios name, FQDN is fine. Netbios resolution is
working as I can browse the domain and use net use to map network
drive on all DCs within the domain. Also, all Windows XP machines
can join to the domain with netbios name.

Netbios over tcpip is enabled and IPV6/local firewall is disabled.
All client machines are on the same subnet. No WINS is used on the
network.
The error message is:
An attempt to resolve the DNS name of a DC in the domain being
joined has failed. Please verify this client is configured to
reach a DNS server that can resolve DNS names in the target
domain. Any idea?

Thanks
Please post the unedited output of an ipconfig /all from this PC
and one of your DCs.



.

Relevant Pages

  • Re: GPO problems
    ... It was the ISA 2004 firewall client. ... DNS settings and network properties on the server and client computers. ... > Service of SBS is configured to be the DNS server on the problematic ...
    (microsoft.public.windows.server.sbs)
  • RE: Dynamic Update of A&PTR Records - Best Practice?
    ... The DNS server does not support the DNS dynamic update protocol; ... For Windows Server 2003-based computers, the primary full computer name is ... When one of these events triggers a DNS update, the DHCP Client service, ...
    (microsoft.public.windows.server.dns)
  • Re: Migration from NT4 to W2K
    ... 272594 Problems logging on to a Windows 2000-based server or a Windows ... | Full DNS domain name is now ABC1.cz, ... | before in-place upgrade of NT4 is able to logon to this W98 client. ...
    (microsoft.public.windows.server.migration)
  • Re: Connect Computer - Not successful after Numerous Attempts
    ... Since that temporary account is used in the migration ... Client LAN connection is now configured to ONLY show ... the SBS server IP as the DNS server. ... Looks like all DNS records are in place as you ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP on router or server
    ... There are plenty of real instances of problems that many have seen, and have even been posted here, that have been caused by having non-AD DNS servers on a windows client. ... There is a difference between getting an answer of "record not found" and not getting an answer at all (a DNS server being down, timeout exceeded, etc.) If a server replies that a record does not exist, the DNS client will *not* query other servers. ... However I'm wondering if the router should be the one handing out DHCP ...
    (microsoft.public.windows.server.sbs)