2003 DC Bizarre behavior??

[adminbydefault]

I need some help?

I have a single 2003 DC with a combination of 2000 and 2003 member servers, along with couple of UNIX servers in my network. The clients are all 2000 or XP Pro.

I have some bizarre behavior with the XP Pro clients and couple of the 2003 member servers. The XP Pro clients seem to work great after inital login. All network drives are mapped through a script on the DC. However after a period of time they seem to loose their minds. They start dropping resources, like mapped drives and printers. The mapped drives still show connected, but when you attempt to use the drive it says the drive is already connected by this user but it doesn't work. The printers just drop off. There is not fixed time associated with these drops and I have disabled all of the autodisconnect features on the server and clients. If the user logs out and back in everything works great for some amount of time then problems start again.

I have checked all the DNS entries and everything appears to be correct. The server is not logging anything DNS related.

Another issue associated with this. This only occurs on the 2003 member servers. I can login as Domain admin on a 2003 member server with a Domain Admin account, yet I cannot access the Domain users when attempting to add a new user to the local machine? I do not have this problem on the 2000 member servers?

Also, some of the XP Pro clients will start experiencing very slow network performance after several hours of use. I have checked the network utilization on these machines and it barely registers. The network is all 100 base.

I am totaly miffed and would appreciate any suggestions or ideas of things to check. I am getting to the point of dumping the existing DC and starting over, but I would like to avoid that if possible.

Thanks in advance.

 

[supportahm1980]

The only time I saw the map drives drop is when a server lost its connection to the network. Rebooted or just crashed etc. I would do a ping -t ip address and when you see a disconnect drive see if you get a did not reply at the same time. That is the only thing i can think of.

 

[adminbydefault]

supportahm1980,

Thanks. I can ping it just fine, using either ping -t IP or ping -t FQDN. no problems.

The message I get back from MS reads as follows:

An error occurred while reconnecting to X: to \\servername\share.

Microsoft Windows Network: The local device name is already in use.

This connection has not been restored

 

[dberg35]

Maybe it is a DNS issue, did you check that?

 

[adminbydefault]

dberg35,

I am sort of thinking the same thing. However, I am running out of things to check.

The DNS logs on the server dont show any errors. Looks like all the DNS entries are resolving okay.

When I run dcdiag on the server everything passes.

When I run netdiag on the server I get a DNS error and the test fails. I get the following error:

"[WARGING] Cannot find a primary authoritative DNS server for the name 'machinename.domain.com' may not be registred in DNS.
[WARNING] The DNS entries for this DC are not registerd correctly on the DNS server '0.0.0.0' (my server ip). Please wait for 30 minutes for the DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registerd."

I have the DNS entries for my server listed in DNS as follows:

DNS
- SERVERNAME
-Forward Lookup Zones
- DNSzones.domain.com
- (same as parent folder) (NS) machinename.domain.com
- (same as parent folder) (SOA)machinename.domain.com

- Reverse Lookup Zones
- 0.0.0.x Subnet
- (same as parent folder) (NS) machinename.domain.com
- (same as parent folder)(SOA) machinename.domain.com

I should also not, that I have recurring, Userenv and Autoenrollment errors on the XP Pro boxes. However, when I attempt to Troubleshoot these errors under the user action selections everything works as it should.

Like I said, I still belive I have a DNS issue, but I am having a hard time figuring out what is wrong. Any ideas.

Thanks in advance.

 

[dberg35]

Ok try taking one of your clients that is having this issue and staticly assign your DNS to it. Also make sure your forwarder are set for your ISP DNS. Also check this out

http://support.microsoft.com/kb/816592