File shares stop working

I'm experiencing a problem on on of my server 2003 domain controllers.
It is also a file server and occationally (about once a week) all it's file
shares stop responding. You can terminal to the server and it repsonds to
pings but file and print shares cannot be accessed (though they still look
like they're there on the server). There's nothing in the system or app logs
to indicate anything going wrong. Has anyone heard of this behaviour before?
Can anyone suggest additional logging to switch on to diagnose the issue?

Thanks.

what's the system error if you do net view \\servername when that happens?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Tommy" <(E-Mail Removed)> wrote in message news:CC85C526-711B-4A35-A8ED-(E-Mail Removed)...
I'm experiencing a problem on on of my server 2003 domain controllers.
It is also a file server and occationally (about once a week) all it's file
shares stop responding. You can terminal to the server and it repsonds to
pings but file and print shares cannot be accessed (though they still look
like they're there on the server). There's nothing in the system or app logs
to indicate anything going wrong. Has anyone heard of this behaviour before?
Can anyone suggest additional logging to switch on to diagnose the issue?

Thanks.

I'm also experiencing this as a symptom of a problem on my DC. Since we use
roaming profiles, it also means that people can't log on or log off
correctly. They can't run logon scripts or get GPO information either, and
these are the errors that show up in the event log. It is because the
shares are inaccessible... I'm writing a full account of my problem, but I
thought I'd post in this thread, too, to see if anyone has ideas that can
help Tommy and myself out.

Marc

"Tommy" <(E-Mail Removed)> wrote in message
news:CC85C526-711B-4A35-A8ED-(E-Mail Removed)...
> I'm experiencing a problem on on of my server 2003 domain controllers.
> It is also a file server and occationally (about once a week) all it's
> file
> shares stop responding. You can terminal to the server and it repsonds to
> pings but file and print shares cannot be accessed (though they still look
> like they're there on the server). There's nothing in the system or app
> logs
> to indicate anything going wrong. Has anyone heard of this behaviour
> before?
> Can anyone suggest additional logging to switch on to diagnose the issue?
>
> Thanks.
>
>