Shares from our Windows Server 2008 machine disappear daily, these are being used are our shared docs. I can remote desktop to it but not connect to the server via windows explorer.
arrived this morning all was fine, now it seems to have gone FUBAR agen. i have tried so far:
- removing from the domain
- deleting the shares
- rejoining then reconnecting
- have swapped the nw port (generally for the sake of it lol)
- tried restarting services left and right (only one that sounds right is 'server for NFS'
just removed the file services roll see how this goes
want to do a complete reinstall but cant get in til this sat.
only thing to solve it is a restart. but if stations have lost the mappings they need a restart too.
please please any ideas, clues, insights.....anything
have being trying since last week to resolve this no joy yet
bump please any thoughts, ideas, jokes lol (need cheering up lol)
Are the NIC drivers borked?
Try re-installing the NICs. I know you tried a different port but I suspect it will be the same make/model and hence using the same driver.
am gonna reinstall (during school time lol) have the old srver have swapped to that for time being. when i reinstall will use the drivers on disk or site not standard win drivers suppose will be a good idea.
another weird thing t'was doing, when setting up shares took ages to search for users/usertypes off the domain. sharing the files wasnt too slow (folders of 20gb gonna take a while to apply permissions) but searching on the old old server and other1s is done in seconds not mins.
By any change you have a service server.exe running on your box ?
yeah the 'server' service was running along with 'server nfs'. whats this have to do bio?
Originally Posted by bio
just finished a rebuild and copied 50gb of data bk time go in a sec and see if it is still standing in the morrow!
Well 2 weeks ago i spoke to a fellow engineer that ran into the same problem as yours... shares where disappearing on a w2k8 server box. It seems that a server.exe service was running on the box... as he investigated ...he pinned down the problem due to a faulty client that was creating havoc on the server. That client was infected with a trojan/virus. He also told me that he was running symantec AV that had not recognised that virus.. after cleanig the network (he used NOD32).. his problems went away..
I hope this helps somehow