Network Shares become Unavailable

By julisana ·
I'm running into an issue where one of my servers' network shares become unavailable after a few days. The only fix I've been able to do is to reboot it. They'll be available after that, but only for a few days (week max) and then they're unavailable again.

The server is running Server 2003 SP2. It's got plenty of HDD space and 3GB of RAM.

It's running as an application server, hosting 3 programs that have databases running SQL2005 Standard. We keep them on the same server because they integrate with each other automatically.

What would cause this issue to be happening?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

What do you mean?

by cmiller5400 In reply to Network Shares become Una ...

What do you mean by "unavailable"? Is there some sort of error message? Is there anything in the event logs?

Collapse -

They're no longer accessable

by julisana In reply to What do you mean?

By "unavailable", I mean that a computer that has said network shares mapped to it can no longer access it. They get the following message: "An error occurred while reconnecting L: to \\servername\sharename

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

This connection has not been restored."

There are also a lot of things in the event viewer, unfortunately, I don't know which ones, if any, pertain to this issue.

Collapse -

All the red X's you should look into....

by ---TK--- In reply to They're no longer accessa ...

Also you might want to look into Memory leaks.

Collapse -


by julisana In reply to All the red X's you shoul ...

They look like they all have to do with services, but I don't know what would cause them in the first place.

Collapse -


by ---TK--- In reply to Services

Are the X errors all the same 2 or 3 or 4 repeating? or are all the errors different?

Collapse -


by julisana In reply to Question.....

There's a series of X's that each deal with different services (How they 'Terminated unexpectedly'. Some of them try and restart), and then a bunch that deal with printing. The printing one's I'm not concerned with.

There's an X that happened about 40 minutes prior to all the services quitting:

"An anonymous session connected from LOCALHOST has attempted to open an LSA policy handle on this machine. The attempt was rejected with STATUS_ACCESS_DENIED to prevent leaking security sensitive information to the anonymous caller.
The application that made this attempt needs to be fixed. Please contact the application vendor. As a temporary workaround, this security measure can be disabled by setting the \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\TurnOffAnonymousBlock DWORD value to 1.
This message will be logged at most once a day."

The services that left error messages:
Application Experience Lookup service (restart)
Windows Audio service
Background Intelligent Transfer Service (restart)
Computer Browser service
Cryptographic Services service
Logical Disk Manager service
COM+ Event System service
Help and Support service (restart)
Server service
Workstation service
Network Connections service
Network Location Awareness (NLA) service
Task Scheduler service (restart)
Secondary Logon service
System Event Notification service
Shell Hardware Detection service
Distributed Link Tracking Client service
Windows Management Instrumentation service (restart)
Automatic Updates service
Wireless configuration service

These all happened at the same time this morning.

Collapse -


by julisana In reply to Question.....

I took a look at the services window, and neither the Server nor the Workstation services restarted. I'm not sure why they didn't restart properly.

Any tips on how I can keep this issue from happening in the future?

Collapse -

its a rabbit hole....

by ---TK--- In reply to Odd...

look at their common dependencies. if their dependencies will not start then they can not start. but you can disable these two services "Help and Support service" and "Wireless configuration service". As long as you wireless network doesn't rely on your server... When you research the X's all you really need are the EventID #'s... I would also run a virus scan, seems like there is a whole mess of stuff going on....

Collapse -


by ---TK--- In reply to Odd...

Im shooting in the dark but check this out the registry part lead me to it....

Collapse -

Well that's your problem!!

by cmiller5400 In reply to Odd...

If the Server Service is not started, nobody can connect to your machine!!!

Related Discussions

Related Forums