New answers tagged network-share
There's no difference. The first creates a new share (you can edit one) and automatically configures the share permissions to System and your current user. The second allows you to manage the share (permissions, remove, offline files, etc.).
I use bogus credentials to really disable access. net use * /d /y net use "\\10.0.0.5\c$" "badpassword" /user:"baduser" net use * /d /y that seems to overwrite the old credentials and forces explorer to attempt to use the new bad credentials.
Sounds like a DNS issue to me. To confirm, I'd add server name and IP to the hosts file on the computer with issues and see if that resolves the problem.
If you want to avoid the download/upload you have to look for online applications. Google docs is very good for office documents. Your main requirement (having the same url for a document everywhere) is solved. This also solves your cross-platform problem and access problem (you need a webbrowser). For large documents you could work with multiple smaller ...
Are file shares a vector for malware to propagate? Absolutely. Does the share being wide open vs. restricted to authenticated/authorized users make a difference? Not really. In my experience, most of your infection vectors will be from authenticated users and not rogue machines on your network. Should you have an AV solution in place to monitor the ...
Take the IP address of your old storage server and add it to the new one. As long as none of the shares on the old top level shares have the same name on the new server, you'll be ok. If they do, it gets more complex. This is how I'd do it on a NAS, at least. I presume it works the same way with Windows file servers.
For what its worth, I recently migrated a file-based database from a Netgear Raid 5 NAS (3 drive, consumer quality?) to a Win Server 2012 Raid 5 (5 drive) and immediately experienced some lag in application performance. So there's is lot more to it in protocols, particularly if Windows uses SMB, as I'm starting to learn quickly.
While MDMarra's suggestion was good and is typically something that should be set via GPO anyway to allow for network scripts, etc. to function properly during login, unfortunately it didn't fix it like I thought. Consider it a placebo effect for a few days, but the issue returned in force. But, I did find a Technet community post that did end up fixing ...
Top 50 recent answers are included