Link to home
Start Free TrialLog in
Avatar of kaushal2004
kaushal2004Flag for United States of America

asked on

Logon to Windows 2003 Server from XP Workstation

Hi,

I had just setup a small home network with Windows 2003 server.  Everything seems to work fine on server side.  I log on to my Windows XP machine and join the laptop on to the domain without a problem.  After I reboot my laptop and login to the domain account, I get a response that "there are no domain available at this time".  I have waited for 3 hours and tried once again, the laptop just cannot logon to the the domain.  When I look at the the active directory on the server, my computer's host name is listed under Computer folder.  

There are no apparent logs that I can see.  Except I did notice event log under DNS tab with Error and ID's 4015, 4004.  Does anyone have any idea what is really causing this problem or what kind of DNS problems I am encountering.

Thanks in advance....
Avatar of Lazarus
Lazarus
Flag of United States of America image

Event ID 4015 - The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The event data contains the error.

Some users report this problem after upgrading Win2K DNS servers to Win2K3. -- Restart the DNS server
If it continues...

Event ID 4004 - The DNS server was unable to complete directory service enumeration of zone .. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The event data contains the error.

From a newsgroup post: "This can be caused if you have a single DC or two DCs and they point to themselves as the first entry in the DNS list in IP properties and the zone is AD Integrated. Reason could be that the DC has many services running on it (SQL, Exchange, etc.) or is a slower machine, and when the Netlogon service tries to register into the zone at boot time, AD is not quite initialized yet and so you get the error. You can either ignore it or change the zone to a Primary, or if you have multiple DCs, change the first entry to the partner and the second to itself".

This error can also appear after a chang in the network and you forgot to change the reverse-lookupzone.

Check that all your patches are up to date, Restart both your computers.
You did not mention, but I'll assume that you are refering to XP Professional not Home...?
Avatar of kaushal2004

ASKER

Yes, I was referring to Windows XP Professional.  The Windows 2003 server is currently not running any other applications like SQL, Exchange or anything for that matter.  It is only domain controller.  I only have one domain controller in this shop, nothing else.  

What needs to be really configured in the DNS or what should be in DNS entries.  Currently the forward lookup zone has HOST(A) records, Name Server (NS) and Start of Authority (SOA) entries.  Don't know where to go from here to resolve this issue.
Avatar of joedoe58
joedoe58

Can you resolve names from the laptop with nslookup? Is your DC a Global Catalog, if not make it a GC.
I cannot resolve names from my laptop with nslookup.  No it is not GC but I will convert it to GC
If you type ipconfig /all from a command prompt on your laptop what is the ip of your DNS server? It should be your server and not one on the internet.
If your only running one server it should handle all roles. Does your server point to itself for it's DNS server or do you have it set to look for and outside DNS server. It should point to itself.
to respond to joedoe58 answer, my laptop's dns is currently pointing to the interent.  i had set it initially to be no dns so that it would pick from the server.  but i was unable to browse the internet.  so i had to put in my internet OR ISP's dns info.

to respond to lazarus98, i have the server look for outside dns info in the forwarder properties of dns.  where and what should be entered.
also, will it help if i give one more piece of information.  the laptop is using Linksys Wireless Access Point.  The access point has it's own IP address.  There is no DNS configuration on this access point.  let me know if i can help further.
and i have also noticed that, i can ping from my laptop to the server's ip address but i cannot ping from the server to the laptop's ip address.  
If your th IP to your DNS server is say 192.168.1.2. You should be setting your Preferred DNS Server in your TCP/IP Stack to the same.
maybe this peice of information i am missing.  my server is setup as follows in the TCP/IP setting

IP Address:  192.168.1.199
SM:  255.255.255.0
GW:  192.168.1.1

Nothing for primary or secondary dns.  
ASKER CERTIFIED SOLUTION
Avatar of miroofi75
miroofi75

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The DNS are for Laptop.

regards


Imran
>>maybe this peice of information i am missing.  my server is setup as follows in the TCP/IP setting
>>
>>IP Address:  192.168.1.199
>>SM:  255.255.255.0
>>GW:  192.168.1.1
>>
>>Nothing for primary or secondary dns.  

Here ^^^^^^^^^^^^^^^^^^^^^^

Your'e Primary DNS should be set to 192.168.1.199
I have setup my laptop and server as mentioned by MIROOFI75.  It still doesn't work.

Laptop
IP:  192.168.1.200
SM: 255.255.255.0
GW:  192.168.1.1
Primary DNS:  192.168.1.199 (server's IP address)
Secondary DNS:  ISP's DNS

Server
IP:  192.168.1.199
SM:  255.255.255.0
GW:  192.168.1.1
NO DNS INFO

In DNS configuration, I have setup Forwarder as ISP's primary and secondary DNS info.

Please help me further.  Where am I doing wrong.
kaushal2004 - You must have your Servers Network Settings (TCP/IP) Primary DNS  pointing to itself. The DNS Server should be point to all other forwarders.
Server
IP:  192.168.1.199
SM:  255.255.255.0
GW:  192.168.1.1
DNS 192.168.1.199
Thanks to MIROOFI75 and LAZARUS98 for their help.  It really worked.  But my ultimate problem was the built in Windows XP firewall which was preventing other machines from accessing my laptop.  Hence my laptop was not able to go on to the domain neither my server could ping the laptop.  Now all works well.

Thanks a lot to MIROOFI75 and LAZARUS98
Your more than welcome.
You are welcome.