Rizwan Ranjha

I am working as Network Engineer & as QA Officer with two separate companies but sometime some issues occurs on both locations and you are unable to get the cause that why it happens on both different locations on same day but today I get an Error in Events and that was something like as under; ========================= EVENT ID 13568 Source NtFrs START ==================== The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.  Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"  Replica root path is   : "c:\windows\sysvol\domain"  Replica root volume is : "\\.\C:"  A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons.  [1] Volume "\\.\C:" has been formatted.  [2] The NTFS USN journal on volume "\\.\C:"...

Please make sure that you have at least one network interface that is currently active and has an IP address and start this application again. One of my network user call me today and show me below error and ask the solution. There were Cisco VPN client installed & Cisco AnyConnect installed on user system but it was not an issue. Read More ...

Well, I was just trying to install Apache 2.2.0 on CentOS 6.4  manually but when i tried to ./configure , it gives me an error stating something like as ; configure error no acceptable c compiler found in $PATH Solution was more than simple, it was just to do something like as; Solution : yum groupinstall "Development Tools" Hope this will also work for you for title error, please show up in errors

I just install CentOS 6.4 and use yum install update but got “Cannot retrieve repository metadata (repomd.xml) for repository: Please verify its path and try again” I have double check with nslookup , ping and general internet browsing and everything seems me fine but update didn't work. I also tried yum clean all etc. but what work for me is here; Solution :   Open a terminal (become Super user by entering 'su' and then the password) Type cd /var/run/ Than Type dir  to look for the ' yum.pid ' file. Type rm -f yum.pid  and press Enter Again Type dir to Confirm that the ' yum.pid ' file has been deleted. Now again try yum update Hope this will resolve your issue, I have done this on CentOS 6.4 but I have a great hope that it will also work for fedora, RedHat as well. please show yourself in comments;

I know, I am writing about the thing that is a lot over the internet but today in my Good Morning to my Desk, I tried to ping of host in my network and I just got this message and I faced this issue on Windows XP, Windows 7 and now on Windows 8 and on Servers Windows 2003 and Windows Server 2008/R2 as well and the solution also work for me on these Operating Systems. Well the message was; C:\Users\rizwan.ahmad>ping 192.168.10.10 'ping' is not recognized as an internal or external command, operable program or batch file. Solution 1 (Easy):    Start > RUN Type control sysdm.cpl,,3 or Open Control Panel » System » Advanced » Environment Variables Right Click on My computer Go to Properties Go to Advanced system settings (on Windows 7 / 8) Environment Variables Select 'PATH' from the list of system variables and edit set PATH to c:\windows\system32 ; Solution 2 (Advance) Open CMD and enter SET command and check the output, there you ...

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 ...

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...