Shares become unavailable

[CCSSLP]

We have a head scratcher here. We have Win2K Server (upgraded two months ago from NT4,) running Exchange 2000 (upgraded at the same time from 5.5.) This machine is a DC and hosts files made available over the network on a share. Conversion went very smoothly as did initial network operation. Within the last two weeks, however, the server has seemed to forget that it is to share.

Behavior usually begins with users noticing slow access to documents (usually Word) on the share. This will persist for a couple of minutes at least. Email seems to function normally. From the server console, the share can be browsed via network neighborhood. Suddenly, anyone (including at the console,) is unable to access the share and receive "network path cannot be found." The directories may be browsed at the console on the partitions, but not through the share via Network Neighborhood.

A reboot restores functionality. Event logs show nothing about the event and as yet, we've not found helpful information in TechNet. Any help in this would be much appreciated.

 

[GlenJohnson]

Conflict with DHCP changing address' and host file? (Host file doesn't match actual IP?) Rename hosts file oldhosts and see what happens. Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com


"Science is built up with facts, as a house is with stones. But a collection
of facts is not more a science than a heap of stones is a home".
Henri Poincare (1854 - 1912) French mathematician

 

[CCSSLP]

Slipstream: I'll be sure to post back if we make any progress. We did have another server--same configuration less exchange. It is a file and print server. Shares would become unavailable in much the same way, but no error messages were generated. Problems did begin when it was still NT4, but became so frequent we rebuilt the server from the ground up. (i.e. no upgrade path.)

Glen: Our servers are statically assigned IPs and this one matches the hosts file. We did find that some connections to the network behaved more consistently when we updated hosts to reflect the FQDN. In looking at local copies of the file on this machine, I noticed not all had been updated. I have corrected that, and will see if anything comes of it. Thanks for your input. I'll let you know how it turns out.

 

[CCSSLP]

We seem to have proven that AV services are behind some of the problems. We've been advised not to scan Inetsrv, NTDS, SYSVOL, exchsrvr (on all directories), M:\. Since omitting NTDS and SYSVOL from realtime protection and scans, the problem has subsided. The other three directories had previously been excluded.

 

[doomhamur]

There are several things that you should consider.
Win2k domains work best when using WINS, DHCP and DNS together. it stops most of the problems you are dealing with also. It is also not recomended to use your file/exchange server for your domain controler.

It would be better to have a low end server (like a dell PowerEdge 350) and use it as your DC running primary WINS, DNS and DHCP. the use your file server to run secondary WINS, DNS and DHCP. also setup routeing on the DC and not on the file server.
i have built networks with static ip address (60 different static class c networks with 5-230 static IP addresses each) to Static IP for servers and printer only with DHCP for clients. It is much easier to manage one with WINS, DHCP and DNS.

If you would like more info, or some help setting things up i can be contacted at support@brigadeindustries.net

Thanks and good luck

 

[273485]

what is mean by old host?
Thanks in advance.