New answers tagged windows-server-2008
In my case this happened because my Internet connection had both IPv4 and IPv6 enabled, but I then connected to a VPN that supported only IPv4. So I guess Windows was still trying to connect to that host over IPv6 over the VPN, which failed. The fix was to disable IPv6 in the network adapter properties for my Internet connection.
I don't know if win2k8 has it.. (Win8 and Win2k12 has it for sure), but look for control panel app called "View Reliability History". This control panel applet, is supposed to display any apps which stopped working, and to my knowledge and experience, include apps which were explicitly killed by the user. Do note that this probably won't tell you how long ...
You should just have to turn off the DHCP server in Tomato and turn it on on your Windows Server. You don't have to "point" anything at it. The way DHCP works, is it sends a UDP packet to the broadcast address for the subnet, so as long as the server and clients are on the same subnet it should "just work."
Per my testing, beginning with Windows 7 (possibly Vista) the functionality you describe no longer exists. I've tried a variety of settings in Windows Explorer and have found no workarounds. It looks like Microsoft has removed this and isn't bringing it back. The same "reset" behavior of the selected items happens even on Server 2012. Unfortunately I ...
It depend on how it done. If it policy (I don't know about this way) or by local scheduler, local admin can change policy. If it remote shutdown command and it issued for immediate shutdown. Hard to do somthing, except remove domain admins from local admins group. If it remote shutdown with timeout. In this timeout other admin (local) can cancel shutdown ...
Normally you can prevent a restart or shutdown using the command shutdown /a within the time-out period Try running the above command in CMD with admin privileges and check
Simple solution we used at work for this issue: cheap USB audio dongles from eBay, less than £2.50 apiece. Stick one in the back of the server and it now has an audio device that it can redirect.
For purposes of centralized login and sharing resources (like document files & folders) you will want a server. If you just want to share files a simple NAS appliance might do but if you want centralized logins and management of users (probably you do, as in a school students will come and go every semester) you want what's called a Domain Server. ...
Top 50 recent answers are included