PDA

View Full Version : Windows XP pro workstations cannot logon to Windows 2000 servers with WINS


Senghor Etienne
June 6th 03, 03:37 PM
I have a network that consists of windows 2000 servers and
WIN XP / WIN 2000 Workstations . We have a domain
controller named WVHTIO configured with the IP 192.168.0.5
and this is also the logon domain ...every users have
internet access so they have to use the 198.77.116.8 which
the DNS used for name resolution for the internet but not
for the inside network ..The DNS for the inside network is
the same as the domain controller ...so , we use an H-Node
Type of WINS server for name resolution and a DHCP server
sends configurations automatically to the workstations ..

The DHCP sends a configuration like for example :


Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : esenghor
Primary DNS Suffix . . . . . . . : wvhtio
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : wvhtio

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Cable
Disconnected
Description . . . . . . . . . . . : Intel 21143
Based PCI Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-10-7A-15-85-
7C

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R)
PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-00-39-47-73-
82
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.xxx
(the xxx is a variable number)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.5
DNS Servers . . . . . . . . . . . : 198.77.116.8
Primary WINS Server . . . . . . . : 192.168.0.5
Lease Obtained. . . . . . . . . . : Tuesday, June
03, 2003 10:34:59 AM
Lease Expires . . . . . . . . . . : Wednesday,
June 11, 2003 10:34:59 AM


so all the workstations get this configurations by mean of
DHCP ..
In this configuration, as you can notice , the user uses
WINS as their primary name resolution technic to logon to
the server and for browsing the network resources and they
use the 198.77.116.8 as the second resolution technic for
the internet ...
Normally all the computers are members of the domain
WVHTIO , so when a user logs to the domain , his machine
shouldn't ask for a password when another user in the same
domain tries to access his folders or resources because
the security in centralized at the domain controller ...!!
all users have login scripts and drives have to be mapped
from another file server wich is also part of the domain ..

but now the problem is that when a user with windows XP
machine wants to logon with the same settings , i receive
a message like "user cannot log on because the WVHTIO
domain is not available" . if i manually configure the pc
with the DNS 192.168.0.5 , it works ..!!
and the workstations cannot use both the DNS address: the
192.168.0.5 and the 198.77.116.8 as alternate . In the
this form, they will logon fine but they won't go to the
internet !!

but this settings work fine for windows 2000 machines as
soon as they join the domain , they can access machines
normally on the domain and drives can be mapped quickly
via their logon scripts ..

i then realized that the problem is really a name
resolution thing !

So, in brief the problem is:

1) users use 192.168.0.5 for internal name resoltuion with
H-NODE WINS and they 198.77.116.8 for name resolution to
the intenet !
2) Both windows 2000 and windows XP cannot use both the
DNS at the same time in the form (primary,
alternate ) ..Thay will be able to logon but they won;t go
to the internet
3) We want the users to be able to logon and go to the
internet at the same time .so we try to bypass that
problem by allowing the user to logon via WINS and use the
198.77.116.8 as DNS for name resolution to the internet ..
4) This setting works fine for windows 2000 and failed to
work for WIndows XP machines ..
5) Most of the workstation computers of our network is
equipped with windows XP. Only a few have windows 2000 pro
6) Questions:
a) how can we get Windows XP to use WINS for name
resolution so that users can logon to a domain and access
ressources on the network normallly ?
b) How can i use two DNS addresses in the DNS server
section of TCP / IP configuration of windows XP and
Windows 2000 so that the system bypasses one and chooses
the other alternate DNS server , if doesn't find the name
it looks for in the first one ? (this will be the best
technic to solve this problem ..!!

If you have any suggestions, please
Please help me find a solution !!

Ron Lowe
June 6th 03, 06:22 PM
"Senghor Etienne" > wrote in message
...
> I have a network that consists of windows 2000 servers and
> WIN XP / WIN 2000 Workstations . We have a domain
> controller named WVHTIO configured with the IP 192.168.0.5
> and this is also the logon domain ...every users have
> internet access so they have to use the 198.77.116.8 which
> the DNS used for name resolution for the internet but not
> for the inside network ..The DNS for the inside network is
> the same as the domain controller ...so , we use an H-Node
> Type of WINS server for name resolution and a DHCP server
> sends configurations automatically to the workstations ..
>
> The DHCP sends a configuration like for example :
>
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : esenghor
> Primary DNS Suffix . . . . . . . : wvhtio
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : wvhtio
>
> Ethernet adapter Local Area Connection 2:
>
> Media State . . . . . . . . . . . : Cable
> Disconnected
> Description . . . . . . . . . . . : Intel 21143
> Based PCI Fast Ethernet
> Adapter
> Physical Address. . . . . . . . . : 00-10-7A-15-85-
> 7C
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R)
> PRO/100 VE Network Connecti
> on
> Physical Address. . . . . . . . . : 00-00-39-47-73-
> 82
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.0.xxx
> (the xxx is a variable number)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.1
> DHCP Server . . . . . . . . . . . : 192.168.0.5
> DNS Servers . . . . . . . . . . . : 198.77.116.8
> Primary WINS Server . . . . . . . : 192.168.0.5
> Lease Obtained. . . . . . . . . . : Tuesday, June
> 03, 2003 10:34:59 AM
> Lease Expires . . . . . . . . . . : Wednesday,
> June 11, 2003 10:34:59 AM
>
>
> so all the workstations get this configurations by mean of
> DHCP ..
> In this configuration, as you can notice , the user uses
> WINS as their primary name resolution technic to logon to
> the server and for browsing the network resources and they
> use the 198.77.116.8 as the second resolution technic for
> the internet ...
> Normally all the computers are members of the domain
> WVHTIO , so when a user logs to the domain , his machine
> shouldn't ask for a password when another user in the same
> domain tries to access his folders or resources because
> the security in centralized at the domain controller ...!!
> all users have login scripts and drives have to be mapped
> from another file server wich is also part of the domain ..
>
> but now the problem is that when a user with windows XP
> machine wants to logon with the same settings , i receive
> a message like "user cannot log on because the WVHTIO
> domain is not available" . if i manually configure the pc
> with the DNS 192.168.0.5 , it works ..!!
> and the workstations cannot use both the DNS address: the
> 192.168.0.5 and the 198.77.116.8 as alternate . In the
> this form, they will logon fine but they won't go to the
> internet !!
>
> but this settings work fine for windows 2000 machines as
> soon as they join the domain , they can access machines
> normally on the domain and drives can be mapped quickly
> via their logon scripts ..
>
> i then realized that the problem is really a name
> resolution thing !
>
> So, in brief the problem is:
>
> 1) users use 192.168.0.5 for internal name resoltuion with
> H-NODE WINS and they 198.77.116.8 for name resolution to
> the intenet !
> 2) Both windows 2000 and windows XP cannot use both the
> DNS at the same time in the form (primary,
> alternate ) ..Thay will be able to logon but they won;t go
> to the internet
> 3) We want the users to be able to logon and go to the
> internet at the same time .so we try to bypass that
> problem by allowing the user to logon via WINS and use the
> 198.77.116.8 as DNS for name resolution to the internet ..
> 4) This setting works fine for windows 2000 and failed to
> work for WIndows XP machines ..
> 5) Most of the workstation computers of our network is
> equipped with windows XP. Only a few have windows 2000 pro
> 6) Questions:
> a) how can we get Windows XP to use WINS for name
> resolution so that users can logon to a domain and access
> ressources on the network normallly ?
> b) How can i use two DNS addresses in the DNS server
> section of TCP / IP configuration of windows XP and
> Windows 2000 so that the system bypasses one and chooses
> the other alternate DNS server , if doesn't find the name
> it looks for in the first one ? (this will be the best
> technic to solve this problem ..!!
>
> If you have any suggestions, please
> Please help me find a solution !!


Your DNS is misconfigured.
Point all your clients to your internal DNS.

XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers.

WINS and NETBIOS is not the means by which name resolution
occours in the first instance.

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.

( you should use the DHCP server to push out the local DNS server
address. )

2) Ensure DNS server on win2k is configured to permit dynamic updates.

3) Ensure the win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers.
Accept any nags etc, and let it delete any corresponding reverse lookuop
zones if it asks.


The following articles may assist you in setting up DNS correctly:

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202


--
Best Regards,
Ron Lowe
MS-MVP Windows Networking

Google