Thursday, April 3, 2014

ESET Pronny infection

I have been wanting to write a detailed post on this one, but due to unavailable resources, i'm providing the following link which is the guide to the virus removal.

http://kb.eset.com/esetkb/index?page=content&id=SOLN3175

http://www.welivesecurity.com/2012/12/07/autorun-worm-continues-to-turn/

Kindly comment for any suggestions or discussion on this very annoying infection, also if anyone has found an alternate removal methodology.

Thursday, March 7, 2013

Netscreen VPN Client on Windows 7

The Netscreen VPN Client would give an error when installed on Windows 7, and after the install is completed with errors, the icon is disabled. The Juniper website itself says that the Client is no longer supported for Windows OS versions after Windows XP. Found the following workaround on another blog.

1. Stop the Volume Shadow Copy service (VSS) (which prompt an error message when I tried to install the client)
2. Install Juniper Client and ignore the error messages about the virtual adapter
3. Restart the PC
4. If Microsoft IKE and IPSec services are running, stop them
5. Import your Security Policy
6. Startup the Service SafeNet IKE Service
7. Connect to your network

As per another blog: The only downside is that this doesn't resolve the issue with the safenet adapter not installing, so that means DNS will not function once connected to your VPN. You must access network resources using ip addresses. Also, you will need to start the Safenet IKE service after each reboot. I suggest that you should create a .bat file with the following cmd:

net start IreIKE

This is best for my needs since I only need my VPN access for remote desktop connections and not anything that relies on DNS. If you need DNS with your VPN activities I suggest installing a Win XP virtual machine to access your VPN.

Note:
I have not found anyone confirming if this works on Windows 7 64 bit, so i would say this applies to 32 bit machines only. Kindly update if anyone does have a working Netscreen client in 64 bit environment.

Monday, February 25, 2013

Destination Host Unreachable when pinging from Server to any Client

This particular problem of non ping from server to client and vice versa, forced us to use a workaround when configuring anything in the Domain Network. We couldn't join any new client to the Domain or give permissions accordingly, it also caused various other accessibility issues all related to problem of non ping. Below is the Solution to get Ping back.
On Server
Start-> Run-> Services.msc
Disable or stop the Ipsec Services.

Due to some reason this service goes in Block mode, disallowing ping and all other functions based on Ping. I do not know the need for this service, therefore disabling this does not affect anything else in my network.

Friday, December 21, 2012

Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

Fellow troubleshooters, please READ this in full before implementing a solution.

One of our clients had this error message displayed on boot "Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM". I immediately decided to repair Windows which took a good 1 hour and more. After the repair i had to validate windows before i could login, it wouldnt do that though i clicked yes on the prompt. I then booted into safe mode with command prompt and typed the command "rundll32.exe syssetup, SetupOobeBnk", with uppercase and lowercase as typed and without quotes (this command increases the validation time to 30 days allowing to login). The command ran and i restarted, to my surprise i reached at the same boot screen i did before 1 hr, saying "Windows could not........ SYSTEM". Having no other bright idea, i called my colleague who advised to do the following. THIS IS THE ACTUAL SOLUTION TO THE PROBLEM.

Boot to Mini Xp (this is from Hirens Boot cd, an amazing tool, a must have for every techy) and follow the steps
1. Rename the file c:\Windows\system32\config\system, to systemold.
2. Copy the file c:\Windows\repair\system and paste in the folder c:\Windows\system32\config.
Restart the computer and the problem is solved in less than 10 mins.

Well, not for me. Since i had done the repair (which wasnt required in the first place), i still needed to activate windows. I logged in, and tried to go in programs-> Activate windows. The window wouldnt open. I tried windows update, wouldn't open. Tried to open internet explorer, would close. I figured windows activation would be connected to internet explorer. Thankfully i had chrome installed. I downloaded and installed the latest internet explorer and activated windows normally. Now everything was fixed.
So the most important lesson here is, Always search a bit and consult a colleague before implementing a possible solution, Happy toubleshooting :)

Monday, May 7, 2012

Computer/Server Serial Number from command line

Explaining a customer to find the serial number of a machine, can be a cumbersome task. At times it might even result in failing to get one, and requiring the IT person to visit the site. Here's the simple command to retrieve the Serial number and model name of a machine ( pc and server )

Type in command prompt

wmic bios get serialnumber 
wmic csproduct get name

Handy !!

Thursday, March 22, 2012

HP Laserjet 1200 Windows 7 64 bit Drivers

This particular printer when installed and shared on Xp 32 and 64 bit computers, works perfectly fine. But when connected ( through USB cable ) to a Windows Xp machine and shared ( through network ) to Windows 7 64 bit/ Vista 64 bit, the printer wouldn't print, even after giving the right drivers downloaded from the HP website.
Following is the step by step process given on Hp forum to get it working , i have tried and tested it myself, almost a sure shot bet.

1. Disconnect the printer from the desktop computer on the network. Then, connect the printer directly to the Window 7 64 bit (or Vista 64 bit) machine using the USB cable. The machine loads the correct driver automatically.
2. Print a test page. (This is an important step.)
3. Disconnect the printer from Windows 7/ Vista 64 bit and reconnect it back to the Xp machine
4. Open the list of printers of the Windows 7/ Vista 64 bit computer , find the LaserJet printer. Right click and open "Printer properties" (not the "Properties" at the bottom of list).
5. Find the "ports" tab. Change from the USB port (DOT4_xxx) to the network connection. If you do not know how to change it to network connection, click "Add Port", then click "Local Port". Type "\\your_Xp_pc_name\your_shared_printer_name" (This is just an example.). Click OK to save it.
6. Print another test page.



Printer is now configured.

Wednesday, December 28, 2011

Windows Presentation Foundation Terminal Server Print W has encountered a problem and needs to close. We are sorry for the inconvenience.

When connecting Remote desktop from a Windows Xp machine on to Windows Server 2008, and trying to print on a redirected printer, the print comes out fine but the error mentioned in the subject pops up. Microsoft suggests to install .Net framework 3 with Sp1 and update the file Tswpfwrp.exe. The .Net fix didnot solve the problem for any computer in my organisation, updating the Tswpfwrp.exe file did. Heres the simple procedure.

1. Copy the file Tswpfwrp.exe from any Windows Vista or Windows 7 machine located in System32 folder
2. Paste the file in System32 folder of the windows Xp machine.

Connecting to remote desktop and printing should now work without error.