shares become unavailable..?

[remcovanuitert]

Sometimes, the shared folders on one of our servers (Win2k, SP4) become unaccessible and only a reboot seems to solve this!
Browsing to \\servername returns an error ("cannot be found&quot, they are also not accessible when you try to access these shares on the server itself (by going to \\servername). Going to \\servername\share does not work either.
This happens once every few weeks. I checked the event log, but nothing shows up in there.

Any idea what's causing this?

Thanks in advance,
Remco

PS This is not a 'I lost my network connection and now my mappings are gone'-problem. I'm trying to access the shares directly, not through mappings. All client PCs suffer from this, not just certain PCs.

 

[remcovanuitert]

PS2. It's not a network issue either. We have a dozen servers at our site, and this is the only one with this problem.

 

[FrauW]

Have you tried pinging the host server when you get the error 'Cannot be found'? Try this. If you can ping the server and get a reply even though your share is lost, it means that you do not have a persistent connection. If the drives are being mapped via a login script, verify that the 'Persistent: Yes' parameter has been set.

 

[remcovanuitert]

Like I said in my post; it is not a network issue. It is not a mappings issue either.

If we encounter the problem, we can still access everything else on the network, we can still logon to the server via terminal services or pcAnywhere, everything on the server still works, except for the shares. Like I said, we access the shares by going to \\servername\share directly.

Thanks anyway.

 

[intensecity]

Has anyone come up with a fix for this issue I seem to be having the same exact issue, any suggestions?

- MaC

 

[mawilson]

When it happens are the computer browser and server services still running?

 

[xmsre]

if you do a netstat -an, what do you see?

 

[intensecity]

Yes the server is still running and so are the services - the server can access all computers on the network - I just cant access the server - if I ping the server I get a reply if I try to connect by IP I can get in -

"NETSTAT -an" - Server Results

Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:88 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:464 0.0.0.0:0 LISTENING
TCP 0.0.0.0:548 0.0.0.0:0 LISTENING
TCP 0.0.0.0:593 0.0.0.0:0 LISTENING
TCP 0.0.0.0:636 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1029 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1032 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1058 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1060 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1065 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1066 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1067 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1068 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1100 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1104 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1115 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1117 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1119 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1121 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1124 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1171 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2512 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2513 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3372 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5688 0.0.0.0:0 LISTENING
TCP 127.0.0.1:389 127.0.0.1:1060 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1065 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1066 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1068 ESTABLISHED
TCP 127.0.0.1:1060 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1065 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1066 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1068 127.0.0.1:389 ESTABLISHED
TCP 192.168.0.10:139 0.0.0.0:0 LISTENING
TCP 192.168.0.10:389 192.168.0.10:1117 ESTABLISHED
TCP 192.168.0.10:389 192.168.0.10:1286 TIME_WAIT
TCP 192.168.0.10:389 192.168.0.10:1287 TIME_WAIT
TCP 192.168.0.10:389 192.168.0.10:1288 TIME_WAIT
TCP 192.168.0.10:445 192.168.0.103:1157 ESTABLISHED
TCP 192.168.0.10:445 192.168.0.125:4199 ESTABLISHED
TCP 192.168.0.10:1026 192.168.0.10:1119 ESTABLISHED
TCP 192.168.0.10:1026 192.168.0.11:1750 ESTABLISHED
TCP 192.168.0.10:1032 192.168.0.11:1026 ESTABLISHED
TCP 192.168.0.10:1117 192.168.0.10:389 ESTABLISHED
TCP 192.168.0.10:1119 192.168.0.10:1026 ESTABLISHED
TCP 192.168.0.10:1280 192.168.0.10:445 TIME_WAIT
TCP 192.168.0.10:1282 192.168.0.10:135 TIME_WAIT
TCP 192.168.0.10:1283 192.168.0.10:1026 TIME_WAIT
TCP 192.168.0.10:1284 192.168.0.10:135 TIME_WAIT
TCP 192.168.0.10:1285 192.168.0.10:1026 TIME_WAIT
TCP 192.168.0.10:1289 192.168.0.10:135 TIME_WAIT
TCP 192.168.0.10:1290 192.168.0.10:1026 TIME_WAIT
TCP 192.168.0.10:1291 192.168.0.10:135 TIME_WAIT
TCP 192.168.0.10:1292 192.168.0.10:1026 TIME_WAIT
TCP 192.168.0.10:1494 0.0.0.0:0 LISTENING
UDP 0.0.0.0:135 *:*
UDP 0.0.0.0:161 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:1028 *:*
UDP 0.0.0.0:1033 *:*
UDP 0.0.0.0:1035 *:*
UDP 0.0.0.0:1054 *:*
UDP 0.0.0.0:1059 *:*
UDP 0.0.0.0:1064 *:*
UDP 0.0.0.0:1116 *:*
UDP 0.0.0.0:1125 *:*
UDP 0.0.0.0:1135 *:*
UDP 0.0.0.0:1146 *:*
UDP 0.0.0.0:1147 *:*
UDP 0.0.0.0:1158 *:*
UDP 0.0.0.0:1232 *:*
UDP 0.0.0.0:1604 *:*
UDP 0.0.0.0:2967 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:38293 *:*
UDP 192.168.0.10:88 *:*
UDP 192.168.0.10:123 *:*
UDP 192.168.0.10:137 *:*
UDP 192.168.0.10:138 *:*
UDP 192.168.0.10:389 *:*
UDP 192.168.0.10:464 *:*
UDP 192.168.0.10:500 *:*

Please help this is really starting to get annoying...

 

[jcoleman]

Has anyone come up with an answer to this one yet? We are having the same problem and it is very annoying.
Thanks

 

[1101001100110101]

Check your ICP$ share make sure a hacker or somone isnt killing the share. A company I used to work for had the same type of problem it ending up being a script runing in the background would delete the IPC$ share when a admin would login to the server. Next time it freezes go to computer managment and see if the IPC$ is still available.

 

[xmsre]

What hardware is it? Is it a broadcom NIC?

 

[jcoleman]

IPC$ is still running, even when I can't get to the shares.

I'm running a Compaq ML350, Win2000, SP4 and not a broadcom NIC.

 

[geist4]

Hello,


Hmmm a tough problem - I had a similar issue. Do you have or have you checked:

Firewall, and so did you re-check the configuration
Event Log Error Id's - still none?
Network Connections - File and Printer Sharing is enabled
Group Policies - Are you using them?
What other jobs does this server have DC/DNS?
Dcdiag / Netdiag- have your run these and reviewed the status?
Are the DNS records for this machine correctly registered?

Using \\Servername\Sharename - is not necessarily direct - name resolution to IP address must occur -

When this problem occurs try: doing a command prompt - NSLOOKUP Servername on a different machine and then on the same machine. Compare those results with those displayed when you type IPCONFIG /all on the server having the problem. Do all the IP addresses correctly match?

Good Luck, (I will follow up with you)

Wills3