• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 402
  • Last Modified:

the shared folder not accessible and error removed by restart

i have HP Blade server BL460C with windows server 2003 Enterprise edition, some of servers do the following:
The server is alive and reply to the ping reques (By name and IP address) and was working correctly and all shared folders work and suddenly, i can't access any shared folder on this server also if i accessing this shared folders from the server itself and this error message appears while accessing:
\\servername is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission.
The specified network name is no longer avilable.
-- i can login to this server remotly
-- this error disappear when i restart the server
could you tell me what the reason of this suddenly stop for share
Regards,
0
saadgroup
Asked:
saadgroup
2 Solutions
 
ChiefITCommented:
Sounds like NIC flooding is shutting down some of your services.

I have been working on a similar post that has problems with intermitant DNS.

Maybe some of this information will help you resolve some intermittant comms over your network. There is a discrepancy on this information. A part of this reads:
(The server requires Multicast mode to work with dual NICS)
(It should read Unicast with one NIC on Layer 2)

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23107415.html
0
 
Amit BhatnagarTechnology Consultant - SecurityCommented:
ChiefIT is correct when he says it seems like flooding. I have personally seen a dozen of similar when I was a system Admin. Normally caused when an application starts grabbing "ephemeral ports" and eventually eats all up.

Try this, When you face this situation simply restart the "Server Service" by going into Services colsole. This service is responsible for creating inbound File Sharing Connections on 445 (SMB). Also, when you face this problem, run Netstat -pan tcp command to see how many ports are in use. Try and see if there is some application\machine which is trying to make too many connections. You can also use TCPView from Sysinternals to see how many connections are being created by different applications\machine etc.

Restarting the server ofcourse releases all the ephemeral ports and thus, you are able to connect again. Hope this helps !!
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now