Server 2008 - Windows XP Windows 7 Clients not authenticating at login

I have a domain that has been in place for over a year.  I recently rebooted the server as well as changed the time on the server manually.  Since then the workstations are logging into the network but lose their drive mappings and are prompted to authenticate once they try to access the shard drives.  once they enter the passwords they then get their drive mappings back.  The time on the workstations is synced to the server.
why is this happening?  What can be done to remedy.  This is happening for all workstations.  All are 7 Pro with a single XP machine. domain-authent.docx
datzitAsked:
Who is Participating?
 
datzitAuthor Commented:
the issue was with the AV software - even though it had been disabled.
I had to remove it and everything worked fine...
sorry for the delay on this as I have been away.
thanks
0
 
akhalighiCommented:
How do you map the drives ? through a log on script ?
0
 
datzitAuthor Commented:
no just through a manual mapping on the client side...
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
saastechCommented:
Is the server running DNS service as well? Are the workstations using the server as it's DNS server?

0
 
datzitAuthor Commented:
yes to both.
0
 
rsoly777Commented:
I would probably reload the DNS Zone on the server first then do an ipconfig/flushdns on the clients. Also check to see that the client times are actually synched to the server
0
 
datzitAuthor Commented:
ok...i restarted the DNS service and did an flushdns and registerdns to a client.
How do i confirm the time sync?
0
 
akhalighiCommented:
use net time on workstation end and force a sync with active directory.
0
 
datzitAuthor Commented:
something going on in DNS.  Nothing has changed in DNS...but the dcdiag,exe shows a couple of failures and the Test in the Monitroing tab of the DNS Zone properties is failing both tests....
0
 
rsoly777Commented:
what kind of errors are you getting in your application and system logs?
0
 
datzitAuthor Commented:
i am going to reboot and then send log info over.
thanks
0
 
datzitAuthor Commented:
3 of these come up...
App Log
1) No client computers have ever contacted the server.
Sys Log
2) The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.

3)Name resolution for the name 1.0.0.127.in-addr.arpa timed out after none of the configured DNS servers responded.


I have the Servers NIC Setting as a static IP address
192.168.1.9
127.0.0.1

Manual DNS Server Entries
192.168.1.9
127.0.0.1
0
 
datzitAuthor Commented:
correction....remove the 127.0.0.1 from the "I have the Servers NIC Setting as a static IP address" part...its just 192.168.1.9l.  Sorry...typo
0
 
rsoly777Commented:
do you use an external DNS Server addresslike from your ISP for the ability to get to the internet?
Are these the settings you always had? Take a look here also: http://technet.microsoft.com/en-us/library/cc959340.aspx
0
 
datzitAuthor Commented:
i have not made any changes on the server.  I do have the ISP DNS for external resolution listed as a forwarder in DNS.
Will look at the article....and reply back as needed.
0
 
rsoly777Commented:
sorry gave you the lonk to windows 2000 although some may apply:
here is the 2008 server troubleshooting DNS article
http://technet.microsoft.com/en-us/library/cc731991.aspx
0
 
datzitAuthor Commented:
I have attached the DCDiag.exe log.
dcdiag.log
0
 
rsoly777Commented:
It appears there is some sort of permissions issue is your sysvol still shared? Is the disk space on your machine good, 1.5 to 2+ gig. Also is there only one DNS Server? Is this also a DC? Are there any more than this one on your network? Also are you using active directory.
0
 
datzitAuthor Commented:
400+GB free space on C.
Running AD
One DNS server only this is it and it is a DC.
very small network.  
Sysvol is shared....nothing seems to be going on there..
I think that it has to be due to the time change..
I am not sure where to confirm that DC is syncd to a global time server...
0
 
datzitAuthor Commented:
running the Best Practices Analyzer it provides many items
first one is this.

Title:
The AD DS BPA should be able to collect data about the name of the forest from the domain controller Server
Severity:
Error
Date:
05/06/11 4:21:14 PM
Category:
Configuration
Issue:
The Active Directory Domain Services Best Practices Analyzer (AD DS BPA) is not able to collect data about the name of the forest from the domain controller Server.
Impact:
The AD DS BPA will not be able to validate configuration data about the name of the forest.
Resolution:
Troubleshoot the domain controller Server to determine the root cause of the problem.
More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=142188
0
 
rsoly777Commented:
you really want your PDC ) to be pointing to an external time server. Have you actually checked the time on each machine to see what the time difference is?  And also, you do want to be sure that the time zone itself is set correctly.

At this point, you could simply point your new server to an external time source, since that's the way it should be long term:

net time /setsntp:time-a.nist.gov,0x1

Stop and restart the time service as before.  This will synchronize the time on your machines with time-a.nist.gov which is a public time server at NIST (cesium clock and all that jazz).   That is the correct way to configure the time service on your server.

0
 
LeeTutorretiredCommented:
I've requested that this question be deleted for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
 
rsoly777Commented:
Lee I think the points should be split since it is obvious all involved put some time into providing an answer
0
 
Robert MarleySinger / SongwriterCommented:
Starting the auto-close procedure on behalf of the question author.

-----
Everyt'ing is everyt'ing,

Mod_MarlEE
Community Support Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.