ivan.ukr's questions

I have primary Mikrotik router connected to Internet provider and serving internal network 192.168.88.0/24. I also have second Mikrotik router which I want to plug into my internal network of the first router and server its own internal network. I can control both routers.

I have configured second one to serve its own internal network 192.168.77.0/24 using QuickSet, and allocated IP address for it on the first one. After this second router is visible in the list of DHCP clients on the first router with address that I've configured. Second router itself seems to have connection to Internet (it is able to find RouterOS update). However any clients connected to the second router do not have access to Internet. They successfully receive IP address from it, DNS also seems to work (i.e. for example nslookup google.com on the client PC gives some IP address in answer). However web browser can't open any site. tracert on Windows shows that packets reach router and stuck there, i.e. like

1 <1ms  <1ms  <1ms    192.168.77.1
2 *     *     *       

What am I doing wrong? What need to be tuned additionally to make it working?

I have a server with Windows Server 2008 R2 and a service process (our custom service) running on it under SYSTEM account. A service has presumably hanged and I wanted to stop it. I tried stopping via Management Console "Services" snap-in, but it didn't help, service process still running, despite in the Management Console it is already marked as not running. Is there a way to kill it from the command line? Note that service runs under the SYSTEM account. I have full administrative privileges on the server.

I have tried pskill from console with elevated privileges (just as pskill PID), but it didn't do the job: it has reported that process killed, but I still see it in the Task Manager.

Taskkill also doesn't help:

C:\>taskkill /f /im myservice.exe
ERROR: The process "myservice.exe" with PID 1268 could not be terminated.
Reason: There is no running instance of the task.

But the process still visible in the Task Manager.

Update: Powerhell Stop-Process -Name myservice -Force also didn't work.

Any ideas how to really kill the process (except rebooting the server)?

I'm trying to connect to Windows 2003 Server SP1 machine from Windows 2008 Server machine with Server Manager and getting following error:

[Window Title] Server Manager

[Main Instruction] Server Manager cannot connect to mtx-app-4.emea.int.genesyslab.com. Click Retry to try to connect again.

[Expanded Information] Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. The resource URI (http://schemas.microsoft.com/powershell/Microsoft.ServerManager) was not found in the WS-Management catalog. The catalog contains the metadata that describes resources, or logical endpoints. For more information, see the about_Remote_Troubleshooting Help topic.

[^] Hide details [Retry] [Cancel]

Please advice how to resolve

I had to reboot machine with w2k8 server by pressing "reset" during it was installing updates due to hung update. After this when I've rebooted and resumed update process it installs update but does not show usual messages like "Installing update X of Y" and name of update, and progress bar also does not show progress. How to fix this?