Skip to main content

Posts

Showing posts from August, 2013

How to enable remote Desktop Remotely

Well ! this may be seem you an old post over the internet but I was just working on this, and I share it with you :). I am not going to write about cheating . So, for this " how to enable remote desktop remotely "; you must have some administrative access on the system or domain admins access on the network (great idea). Lets starts now; From your Windows Operating System (Client / Server), Hit Start Button then Run and type regedit. registry Windows will be open, Click on File , then select Connect Network Registry ;   Type the remote computer IP Address (best practice) or host name in the Enter the object name to select (as below image) and the click OK Press OK and you can manage now remote computer via registry :). Now, it's very simple; B rowse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server in the right panel, I have highlighted seelct   fDenyTSConnection ( REG_DWORD ...

Microsoft Visual SourceSafe File “location-project-userss-username\ss.ini” not found

One of Network user moved in remote location and he was required to dial in VPN to access Microsoft Visual SourceSafe database. Days after his work from remote site he complains that he is getting this error “Microsoft Visual SourceSafe File “ location\project\userss\username\ss.ini” not found ” I checked in VSS location and there were no ss.ini file and this is the file that contains information about user’s working folder path etc. Microsoft doesn’t give any solution on this issue but Google search give us two solutions; Solutions: Note: - Please backup before starting troubleshooting to your Production Microsoft Visual SourceSafe or any Database.   Go to your VSS location, where ss.ini is not found, hope there will be one or more .tmp files. greater in size .tmp file is your ss.ini file. What you just need to do is to rename it to ss. ini.   If you have backup of your VSS, just extract it to somewhere and copy required user’s ss.ini file to error in...

Cisco VPN Client Reason 442: "Failed to enable Virtual Adapter"

If you are Windows user and you often face an error message when you try to connect your Cisco VPN Client and it stats as; “Secure VPN Connection terminated locally by the Client. Reason 442: Failed to enable Virtual Adapter. Connection terminated on: Feb 6, 2013 19:56:04 Duration: 0 day(s), 00:00.00” In Windows XP, sometimes ' remove and reinstall ' was a great solution but in Windows 7 there is a technique that works because this problem is not associated with Cisco VPN client Software. If you face exactly same below message then below solution will surely work; Solution: Hit the start button and type " services.msc ' as shown: Locate and stop Cisco Systems, Inc. VPN Service; Stop and disable Internet Connection Sharing (ICS) Service ; Restart Cisco System, Inc. VPN Service. Launch the Cisco VPN Client again, and the problem is now gone! Solution 2 : Open regedit , and navigate to   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi...