Search Results

Search found 2 results on 1 pages for 'otiel'.

Page 1/1 | 1 

• How to start Windows Explorer as domain administrator [closed]

  - by Otiel

  Possible Duplicate: How do you run windows explorer as a different user? Is it possible to start a Windows Explorer with the rights of another domain user? I tried to do the following to start a Windows Explorer on my computer as my domain Administrator, but without success: Right click on C:\Windows\explorer.exe to select Run as different user, Enter the domain administrator credentials: Domain\Administrator ************ The windows explorer session only opens with my current user rights (Domain\me). The reason behind my question is that I want to change some folder rights on a domain shared disk and I need the Domain\Administrator user rights to do it. Usually, I do it by login as Domain\Administrator on the server hosting the shared disk but I would like to be able to do it from my PC, logged as my current login (Domain\me). EDIT As seen in the linked posts, it is not possible anymore on Windows Vista or 7. On Windows XP, the solution is to do: runas /user:domain\username "explorer /separate"

  Read the article

• Close TCP connection when owner process is already killed

  - by Otiel

  I have a Windows service that - when it starts - opens some WCF services to listen on the 8000 port. It happens that this service crashes sometimes. When it does, the TCP connection is not released, thus causing my service to throw an exception if I try to start it again: AddressAlreadyInUseException: There is already a listener on IP endpoint 0.0.0.0:8000 Some observations: When running CurrPorts or netstat -ano, I can see that the 8000 port is still in use (in LISTENING state) and is owned by the Process ID XXX that corresponded to my service process ID. But my service has already crashed, and does not appear in the Task Manager anymore. Thus I can't kill the process to free the port! Of course, running taskkill /PID XXX returns: ERROR: The process "XXX" not found. When running CurrPorts or netstat -b, I can see that the process name involved in creating the listening port is System, and not as MyService.exe (whereas it is MyService.exe when my service is running). I tried to use CurrPorts to close the connection, but I always get the following error message: Failed to close one or more TCP connections. Be aware that you must run this tool as admin in order to close TCP connections. (Useless to say, I do run CurrPorts as Administrator...) TCPView is not much help either: the process name associated to the 8000 port is <non-existent>, and doing "End process" or "Close connection" has no effect. I tried to see if there was not a child process associated with the PID XXX using Process Explorer, but no luck here. If I close my service properly (before it crashes), the TCP connection is correctly released. This is normal, as I close the WCF service hosts in the OnStop() event of my service. The only way I found to release the connection is to restart the server (which is not convenient in a production environment as you can guess). Waiting does not help, the TCP connection is never released. How can I close the connection without restarting the Windows server? PS: found some questions extremely similar to mine.

  Read the article

1